Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45480

GIT Build with Parameters is not listing branches

    Details

    • Similar Issues:

      Description

      We have a job and it is configured as "Build with Parameters".
      We have chosen "GIT Parameter" when we try to list "Branches/tags" while click build option it is not listing instead showing error message.
      But when we try build job able to clone with SSH keys:

      Command "git ls-remote -h ssh://server.de.xyz.com:7999/xdk/xdk110.git" returned status code 128:
      stdout:
      stderr: error: cannot run ssh: No such file or directory
      fatal: unable to fork
      

      We were using:

      • Jenkins LTS version "2.46.2"
      • Git plugin -->3.3.1
      • Git client plugin --->2.4.6
      • Git Parameter Plug-In--->0.8.0

        Attachments

        1. chrome_2019-02-20_18-34-30.png
          chrome_2019-02-20_18-34-30.png
          123 kB
        2. chrome_2019-02-20_18-34-30.png
          chrome_2019-02-20_18-34-30.png
          308 kB
        3. chrome_2019-02-20_18-41-40.png
          chrome_2019-02-20_18-41-40.png
          37 kB
        4. config-no-flyweight.xml
          6 kB
        5. config-windows-flyweight.xml
          6 kB
        6. Credentional_configuration.png
          Credentional_configuration.png
          46 kB
        7. few_builds.png
          few_builds.png
          76 kB
        8. github_key_add.png
          github_key_add.png
          22 kB
        9. image-2017-11-20-08-59-44-472.png
          2.33 MB
        10. image-2019-03-06-09-41-20-264.png
          image-2019-03-06-09-41-20-264.png
          370 kB
        11. image-2019-03-06-11-03-41-468.png
          image-2019-03-06-11-03-41-468.png
          39 kB
        12. Job_Test_2B_out.png
          Job_Test_2B_out.png
          68 kB
        13. Job_Test_2B.png
          Job_Test_2B.png
          143 kB
        14. Job_test_B_output.png
          Job_test_B_output.png
          220 kB
        15. Job_Test_B.png
          Job_Test_B.png
          132 kB
        16. Windows_slave_configuration.png
          Windows_slave_configuration.png
          71 kB

          Issue Links

            Activity

            Hide
            delovan delo delo added a comment -

            Robson Hermes Are you sure it's durable ?

             

            With SSH, cloning the project was a workaround but only works for the very first build. Starting the 2nd build, it failed.

            Show
            delovan delo delo added a comment - Robson Hermes Are you sure it's durable ?   With SSH, cloning the project was a workaround but only works for the very first build. Starting the 2nd build, it failed.
            Hide
            robsonhermes Robson Hermes added a comment -

            Oh damn it. You are right, now I have failure starting from the 2nd attempt.

            Show
            robsonhermes Robson Hermes added a comment - Oh damn it. You are right, now I have failure starting from the 2nd attempt.
            Hide
            delovan delo delo added a comment -

            Robson Hermes, I suggest you do as Mark Waite suggested for keeping tmp files. I've done it and surprisingly I can't reproduce the bug anymore, even though I switch back to the original plugin.

            For info, after you build the plugin, just copy the plugin files over the original plugin (keep a backup) and restart jenkins.

            With theses files, you will be able to run them directly in bash and have more debug info.

            Show
            delovan delo delo added a comment - Robson Hermes , I suggest you do as Mark Waite suggested for keeping tmp files. I've done it and surprisingly I can't reproduce the bug anymore, even though I switch back to the original plugin. For info, after you build the plugin, just copy the plugin files over the original plugin (keep a backup) and restart jenkins. With theses files, you will be able to run them directly in bash and have more debug info.
            Show
            amoshason Amos Hason added a comment - Related:  https://issues.jenkins-ci.org/browse/JENKINS-56558
            Hide
            amoshason Amos Hason added a comment -

            In our case "/tmp" is not mounted with "noexec".

            I don't understand why it even tries to execute it on the master machine instead of the slave machine. It clearly should run on the slave machine.

            Show
            amoshason Amos Hason added a comment - In our case "/tmp" is not mounted with "noexec". I don't understand why it even tries to execute it on the master machine instead of the slave machine. It clearly should run on the slave machine.

              People

              • Assignee:
                klimas7 Boguslaw Klimas
                Reporter:
                spalani Senthilkumar Palanisamy
              • Votes:
                3 Vote for this issue
                Watchers:
                14 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: