Details

    • Similar Issues:

      Description

      From Jenkins we are launching a z/OS agent for build. Earlier we were able to do a build with Jenkins v. 2.222.1. Now we are trying to setup a new environment with Jenkins v. 2.222.3, but when we try to do a build, we are unable to clone the repository to Mainframe, and we are continuously getting "Seen 0 remote branches" error

      Log is attached.

      We have this git-jenkins.sh file in this path:  /usr/lpp/IBM/dbb106/bin/git-jenkins.sh

      Still we are getting this error in Jenkins log:
      /usr/lpp/IBM/dbb106/bin/git-jenkins.sh 29: FSUM7351 not found

        Attachments

          Activity

          Hide
          markewaite Mark Waite added a comment -

          The Jenkins agent is correctly trying to call git rev-list and the git rev-list command is returning unexpected results.

           > /usr/lpp/IBM/dbb106/bin/git-jenkins.sh rev-list 09db73c29ecb79f9bb7ffdac2febcd1f31fc94ef # timeout=10
          FATAL: Invalid id: git: /usr/lpp/IBM/dbb106/bin/git-jenkins.sh 29: FSUM7351 not found
          

          The format of that error message looks like git-jenkins.sh might be a shell script that is failing on line 29 when trying to call a program named FSUM7351 that is not in the PATH. Compare the PATH on the working system and the non-working system in case an important element of the PATH is missing.

          As far as I can tell, this is most likely an environment error, not a bug with the git plugin.

          Show
          markewaite Mark Waite added a comment - The Jenkins agent is correctly trying to call git rev-list and the git rev-list command is returning unexpected results. > /usr/lpp/IBM/dbb106/bin/git-jenkins.sh rev-list 09db73c29ecb79f9bb7ffdac2febcd1f31fc94ef # timeout=10 FATAL: Invalid id: git: /usr/lpp/IBM/dbb106/bin/git-jenkins.sh 29: FSUM7351 not found The format of that error message looks like git-jenkins.sh might be a shell script that is failing on line 29 when trying to call a program named FSUM7351 that is not in the PATH. Compare the PATH on the working system and the non-working system in case an important element of the PATH is missing. As far as I can tell, this is most likely an environment error, not a bug with the git plugin.
          Hide
          markewaite Mark Waite added a comment -

          Issue is in the git-jenkins.sh script maintained by the user, not by the Jenkins git plugin or git client plugin.

          Please use the mailing list or chat channels for configuration help and other issues.

          Show
          markewaite Mark Waite added a comment - Issue is in the git-jenkins.sh script maintained by the user, not by the Jenkins git plugin or git client plugin. Please use the mailing list or chat channels for configuration help and other issues.

            People

            • Assignee:
              Unassigned
              Reporter:
              goks13 Gokila B
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: