[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Title: Message Title Mark Waite closed an issue as Duplicate Jenkins / JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline resolved JENKINS-27491 as Duplicate kicking off of build via curl command not working in 1.16.1 version of plugin Dup of JENKINS-27332. Downgrade to 2.3.2 of the git plugin worked Change By: Peter Kline (23/Mar/15 1:49 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin 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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Mark Waite commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin 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. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin 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? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin now with credentials goodness Change By: Peter Kline (20/Mar/15 1:32 PM) Attachment: git2.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin I have attached a screenshot (git2.jpg) of the change in the job to use the credential of the main build user we use on all our slaves. Made a dummy change to the repo but still nothing is getting kicked off. the output from the polling log has no significant change so I can't tell if it made any difference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline edited a comment on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin now with credentials goodness see screenshot git2.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin I have a credential set up using a user that is the same one we use for all our slaves. Honestly I am not sure if its set up correctly as the git plugin page talks nothing about using credentials. You are correct in assuming that our older version did not have credentials support so this may be it but I am just not sure how to configure or debug this. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Mark Waite commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Since you mentioned that you were updating from a much earlier version, I wonder if the much earlier version was prior to credentials support. Have you added a credential to that repository so that when the remote polling occurs (usually on the master node), it is not relying on an existing ssh configuration on the master node? The 1.x versions of the git plugin did not support the credentials plugin within the user interface, but the 2.x versions of the git plugin include support for the credentials plugin so that you can add your private key to Jenkins for using during remote polling and checkout. If that fixes it, then the bug is that the polling log did not clearly state that the git ls-remote command failed (since it would have failed due to no authorization). If that fixes it, then an additional enhancement would be some optional additional debugging support to identify the failure mode more clearly in the polling log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Mark Waite edited a comment on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Since you mentioned that you were updating from a much earlier version, I wonder if the much earlier version was prior to credentials support. Have you added a credential to that repository so that when the remote polling occurs (usually on the master node), it is not relying on an existing ssh configuration on the master node? The 1.x versions of the git plugin did not support the credentials plugin within the user interface, but the 2.x versions of the git plugin include support for the credentials plugin so that you can add your private key to Jenkins for use during remote polling and checkout. If that fixes it, then the bug is that the polling log did not clearly state that the git ls-remote command failed (since it would have failed due to no authorization). If that fixes it, then an additional enhancement would be some optional additional debugging support to identify the failure mode more clearly in the polling log. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin I have attached a screenshot of our config. We aren't using multiple repos. The plugin info i have is: Git client plugin: 1.16.1 Git Parameter plugin: 0.4.0 Git plugin: 2.3.5 Git Server Plugin: 1.6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Here is the screenshot of our config Change By: Peter Kline (20/Mar/15 1:31 AM) Attachment: git.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Mark Waite commented on JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Does your job use multiple git repositories? When I have more than one git repository defined in my job, then the polling seems to run, but does not detect changes. I think that matches the buggy behavior you describe, but it isn't clear from your output if you're using a single repository or multiple repositories. Any other hints what might be different? What version of the git plugin are you running? You mentioned git client plugin 1.16.1, but didn't mention the version of the git plugin. You might review the online help for the various forms in which the branch name can be specified. There are many more options in the recent versions of the git plugin than were available in the earlier versions. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline
updated JENKINS-27491
kicking off of build via curl command not working in 1.16.1 version of plugin
Change By:
Peter Kline
(18/Mar/15 7:55 PM)
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):{code}Started on Mar 18, 2015
2
3
:
25
38
:
58
19
PMUsing strategy: Default[poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0)Done. Took 1
.1
sec
No changes
Changes found
{code}New Instance with git 1.8.0.6 and git client 1.16.1{code}Started on Mar 18, 2015 2:28:23 PMUsing 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=10Done. Took 1.6 secNo changes{code}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:{code}-bash-4.1$ /usr/local/bin/git -c core.askpass=true ls-remote -h git@thoroughbred:flt/root.git |grep release_teamfff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1{code}
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.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27491) kicking off of build via curl command not working in 1.16.1 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 1.16.1 version of plugin Change By: Peter Kline (18/Mar/15 7:52 PM) Summary: kicking off of build via curl command not working in 2 1 . 2 16.1 version of plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
