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

kicking off of build via curl command not working in 1.16.1 version of plugin

    Details

    • Similar Issues:

      Description

      We are migrating our old Jenkins instance to a new machine so we are moving from Jenkins 1.538 to 1.605. Our Jenkins plugin is moving from 1.5 to the latest release. We have been using a git hook to run the curl command to fire off a polling task for years now without problem. This no longer works.

      In our older version 1.3.0 we see the polling output of the job looking like (not the same job so don't take it as it doesn't work in the old one either):

      Started on Mar 18, 2015 3:38:19 PM
      Using strategy: Default
      [poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0)
      Done. Took 1 sec
      Changes found
      

      New Instance with git 1.8.0.6 and git client 1.16.1

      Started on Mar 18, 2015 2:28:23 PM
      Using strategy: Default
      [poll] Last Built Revision: Revision 742f5171deb7fcb7a80d00174003f5ffb9b1e396 (refs/remotes/origin/release_team1)
       > /usr/local/bin/git --version # timeout=10
       > /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git # timeout=10
      Done. Took 1.6 sec
      No changes
      

      Now in the second instance there were changes and the job was imported from our old instance. We are not sure why the job is never fired off. The output "refs/remotes..." is different between the old job and the new one and not sure if that might be the issue or not.

      We have tried tweaking the branch specifier to various things but nothing seems to work.

      If I run the ls-remote by hand the output shows the sha1 changed:

      -bash-4.1$ /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git |grep release_team
      fff407f54ce3c97de851d9ba5cda1ce98ae3d931        refs/heads/release_team1
      

      We have tried doing the polling on the slaves but we don't keep our workspaces around after we build so this doesn't work if we don't already have a workspace waiting for the next poll.

        Attachments

        1. git.jpg
          git.jpg
          53 kB
        2. git2.jpg
          git2.jpg
          36 kB

          Issue Links

            Activity

            Hide
            peter_kline Peter Kline added a comment - - edited

            now with credentials goodness see screenshot git2.jpg

            Show
            peter_kline Peter Kline added a comment - - edited now with credentials goodness see screenshot git2.jpg
            Hide
            peter_kline Peter Kline added a comment -

            Another datapoint. I have tried using a user with a simple username/password for the credentials and also a username/with SSH key. Other than the polling output telling me that its using GIT_SSH, nothing else is changing in the log and no changes are detected.

            I know this works if we use polling on the slaves. Is there a way to make that happen without a workspace on the slave?

            Show
            peter_kline Peter Kline added a comment - Another datapoint. I have tried using a user with a simple username/password for the credentials and also a username/with SSH key. Other than the polling output telling me that its using GIT_SSH, nothing else is changing in the log and no changes are detected. I know this works if we use polling on the slaves. Is there a way to make that happen without a workspace on the slave?
            Hide
            markewaite Mark Waite added a comment -

            I wonder if this is another manifestation of JENKINS-27332 ? You could test that by downgrading your git plugin from 2.3.5 to 2.3.4. There are some other hints in that report of alternatives you may be able to try for the branch specification.

            Show
            markewaite Mark Waite added a comment - I wonder if this is another manifestation of JENKINS-27332 ? You could test that by downgrading your git plugin from 2.3.5 to 2.3.4. There are some other hints in that report of alternatives you may be able to try for the branch specification.
            Hide
            peter_kline Peter Kline added a comment -

            We changed the branch specifier to various things with no luck. Not sure if its the same as the bug you mention but after downgrading to 2.3.2 (was the automatic selection in the plugin manager)

            The output now changed to include a second poll line and it now works:

             
            Started on Mar 23, 2015 8:39:04 AM
            Using strategy: Default
            [poll] Last Built Revision: Revision 50f93f0d454e1361d54224c2510b8bbe10c031d6 (refs/remotes/origin/release_team1)
             > /usr/bin/git --version # timeout=10
             > /usr/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git refs/heads/release_team1 # timeout=10
            [poll] Latest remote head revision is: 7a55640ade424c9f730b21d06e483f1ed2626975
            Done. Took 1.5 sec
            Changes found
            
            Show
            peter_kline Peter Kline added a comment - We changed the branch specifier to various things with no luck. Not sure if its the same as the bug you mention but after downgrading to 2.3.2 (was the automatic selection in the plugin manager) The output now changed to include a second poll line and it now works: Started on Mar 23, 2015 8:39:04 AM Using strategy: Default [poll] Last Built Revision: Revision 50f93f0d454e1361d54224c2510b8bbe10c031d6 (refs/remotes/origin/release_team1) > /usr/bin/git --version # timeout=10 > /usr/bin/git -c core.askpass= true ls-remote -h git@thoroughbred:flt/root.git refs/heads/release_team1 # timeout=10 [poll] Latest remote head revision is: 7a55640ade424c9f730b21d06e483f1ed2626975 Done. Took 1.5 sec Changes found
            Hide
            peter_kline Peter Kline added a comment -

            Dup of JENKINS-27332. Downgrade to 2.3.2 of the git plugin worked

            Show
            peter_kline Peter Kline added a comment - Dup of JENKINS-27332 . Downgrade to 2.3.2 of the git plugin worked

              People

              • Assignee:
                ndeloof Nicolas De Loof
                Reporter:
                peter_kline Peter Kline
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: