[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
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 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
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 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 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 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
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 2.2 version of plugin
Peter Kline created JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Issue Type: Bug Assignee: Nicolas De Loof Components: git-client-plugin Created: 18/Mar/15 6:40 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.5 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 2:25:58 PM Using strategy: Default [poll] Last Built Revision: Revision 27dca5ecda6278ef52534e2237c8875c6bcb46ff (remotes/origin/rel-5.3.7.0) Done. Took 1.1 sec No changes 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 fff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1 Project: Jenkins Priority: Minor Reporter: Peter Kline 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 2.2 version of plugin
Peter Kline updated JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Change By: Peter Kline (18/Mar/15 6:41 PM) Priority: Minor Critical 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 2.2 version of plugin
Peter Kline commented on JENKINS-27491 kicking off of build via curl command not working in 2.2 version of plugin Just as a note, the branch specifier for both the old and new instance is: remotes/origin/release_team1 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 2.2 version of plugin
Peter Kline
updated JENKINS-27491
kicking off of build via curl command not working in 2.2 version of plugin
Change By:
Peter Kline
(18/Mar/15 7:52 PM)
Description:
WearemigratingouroldJenkinsinstancetoanewmachinesowearemovingfromJenkins1.538to1.605.OurJenkinspluginismovingfrom1.5tothelatestrelease.Wehavebeenusingagithooktorunthecurlcommandtofireoffapollingtaskforyearsnowwithoutproblem.Thisnolongerworks.Inourolderversion1.
5
3.0
weseethepollingoutputofthejoblookinglike(notthesamejobsodonttakeitasitdoesntworkintheoldoneeither):{code}StartedonMar18,20152:25:58PMUsingstrategy:Default[poll]LastBuiltRevision:Revision27dca5ecda6278ef52534e2237c8875c6bcb46ff(remotes/origin/rel-5.3.7.0)Done.Took1.1secNochanges{code}NewInstancewithgit1.8.0.6andgitclient1.16.1{code}StartedonMar18,20152:28:23PMUsingstrategy:Default[poll]LastBuiltRevision:Revision742f5171deb7fcb7a80d00174003f5ffb9b1e396(refs/remotes/origin/release_team1)/usr/local/bin/git--version#timeout=10/usr/local/bin/git-ccore.askpass=truels-remote-hgit@thoroughbred:flt/root.git#timeout=10Done.Took1.6secNochanges{code}Nowinthesecondinstancetherewerechangesandthejobwasimportedfromouroldinstance.Wearenotsurewhythejobisneverfiredoff.Theoutputrefs/remotes...isdifferentbetweentheoldjobandthenewoneandnotsureifthatmightbetheissueornot.Wehavetriedtweakingthebranchspecifiertovariousthingsbutnothingseemstowork.IfIrunthels-remotebyhandtheoutputshowsthesha1changed:{code}-bash-4.1$/usr/local/bin/git-ccore.askpass=truels-remote-hgit@thoroughbred:flt/root.git|greprelease_teamfff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1{code}
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: kickingoffofbuildviacurlcommandnotworkingin 2 1 . 2 16.1 versionofplugin 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:
WearemigratingouroldJenkinsinstancetoanewmachinesowearemovingfromJenkins1.538to1.605.OurJenkinspluginismovingfrom1.5tothelatestrelease.Wehavebeenusingagithooktorunthecurlcommandtofireoffapollingtaskforyearsnowwithoutproblem.Thisnolongerworks.Inourolderversion1.3.0weseethepollingoutputofthejoblookinglike(notthesamejobsodonttakeitasitdoesntworkintheoldoneeither):{code}StartedonMar18,2015
2
3
:
25
38
:
58
19
PMUsingstrategy:Default[poll]LastBuiltRevision:Revision27dca5ecda6278ef52534e2237c8875c6bcb46ff(remotes/origin/rel-5.3.7.0)Done.Took1
.1
sec
Nochanges
Changesfound
{code}NewInstancewithgit1.8.0.6andgitclient1.16.1{code}StartedonMar18,20152:28:23PMUsingstrategy:Default[poll]LastBuiltRevision:Revision742f5171deb7fcb7a80d00174003f5ffb9b1e396(refs/remotes/origin/release_team1)/usr/local/bin/git--version#timeout=10/usr/local/bin/git-ccore.askpass=truels-remote-hgit@thoroughbred:flt/root.git#timeout=10Done.Took1.6secNochanges{code}Nowinthesecondinstancetherewerechangesandthejobwasimportedfromouroldinstance.Wearenotsurewhythejobisneverfiredoff.Theoutputrefs/remotes...isdifferentbetweentheoldjobandthenewoneandnotsureifthatmightbetheissueornot.Wehavetriedtweakingthebranchspecifiertovariousthingsbutnothingseemstowork.IfIrunthels-remotebyhandtheoutputshowsthesha1changed:{code}-bash-4.1$/usr/local/bin/git-ccore.askpass=truels-remote-hgit@thoroughbred:flt/root.git|greprelease_teamfff407f54ce3c97de851d9ba5cda1ce98ae3d931refs/heads/release_team1{code}
Wehavetrieddoingthepollingontheslavesbutwedontkeepourworkspacesaroundafterwebuildsothisdoesntworkifwedontalreadyhaveaworkspacewaitingforthenextpoll.
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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Peter Kline commented on JENKINS-23232 SEVERE: I/O error in channel Chunked connection By setting -Dhudson.diyChunking=false in /etc/sysconfig/jenkins and restarting I am now able to run remote build calls. Not sure if this fixes the remote slave issue but it certainly solves my issue when running the jenkins-cli.jar problems with Chunking 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] [cli] (JENKINS-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline commented on JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 By setting -Dhudson.diyChunking=false in /etc/sysconfig/jenkins and restarting I am now able to run remote build calls. Leaving ticket open as while this solves my problem not sure if this is a long term viable fix 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] [cli] (JENKINS-23232) SEVERE: I/O error in channel Chunked connection
Peter Kline edited a comment on JENKINS-23232 SEVERE: I/O error in channel Chunked connection Possibly related JENKINS-23223 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] [cli] (JENKINS-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline commented on JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 this is with the latest cli.jar 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] [cli] (JENKINS-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline commented on JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 We see this with calls list list-jobs. For the command "version" we see pages of jibberish but it does display the version somewhere in the mess. We haven't tried authenticating via cert. We use ldap as our method of authentication. We have upgraded our version to 1.566 with all latest plugins and no luck. 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] [cli] (JENKINS-23223) Jenkins CLI to start a build no longer working in 1.564
Peter Kline created JENKINS-23223 Jenkins CLI to start a build no longer working in 1.564 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: cli, core Created: 28/May/14 5:20 PM Description: Prior to upgrade 1.4X we were able to start builds remotely using the cli. Now when we try and do this we get the following output -bash-3.2$ java -jar /tools/jenkins/jenkins-cli.jar -s http://engtools:8080 build test-my-build -p email_name=emai...@domain.com,emai...@domian.com -p workspace_dir=/net/machine/path -p full_imagename=4.2.2.0 -p includes=test1 -p --username jenkins --password jenkins May 28, 2014 12:37:26 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel Chunked connection to http://engtools:8080/cli java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.init(Unknown Source) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Exception in thread "main" hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:41) at hudson.remoting.RequestAbortedException.wrapForRethrow(RequestAbortedException.java:34) at hudson.remoting.Request.call(Request.java:174) at hudson.remoting.Channel.call(Channel.java:739) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:168) at hudson.remoting.$Proxy1.waitForProperty(Unknown Source) at hudson.remoting.Channel.waitForRemoteProperty(Channel.java:1122) at hudson.cli.CLI.init(CLI.java:145) at hudson.cli.CLIConnectionFactory.connect(CLIConnectionFactory.java:72) at hudson.cli.CLI._main(CLI.java:459) at hudson.cli.CLI.main(CLI.java:382) Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at hudson.remoting.Request.abort(Request.java:299) at hudson.remoting.Channel.terminate(Channel.java:802) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.StreamCorruptedException: invalid stream header: 0A0A0A0A at java.io.ObjectInputStream.readStreamHeader(Unknown Source) at java.io.ObjectInputStream.init(Unknown Source) at hudson.remoting.ObjectInputStreamEx.init(ObjectInputStreamEx.java:40) at hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Environment: Jenkins 1.564 Running on Centos 5.8 Project: Jenkins Priority: Critical Reporter: Peter Kline 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
[JIRA] [git] (JENKINS-18212) Branches get triggered for polling when we don't want them to
Peter Kline commented on JENKINS-18212 Branches get triggered for polling when we dont want them to I don't see how that will help. When any push comes from any other job it will start a poll on all jobs that are set to poll. This in turn will cause the branch to see if there are any changes and start the build. Also, the use case may be that someone (not an admin) pushes and we don't want their build to start because we are queuing something so we kill the build immediately, again, as soon as any other branch pushes, the build gets kicked off. 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/groups/opt_out.
[JIRA] [git] (JENKINS-18212) Branches get triggered for polling when we don't want them to
Peter Kline commented on JENKINS-18212 Branches get triggered for polling when we dont want them to I guess my second scenario is more of what I am looking for, sorry for making it unclear. I want the ability to cancel a currently running build on branch2. I don't want a new build to start until a new push on branch2 regardless if they are an admin or not. What happens is when someone pushes on branch1, it will tell branch2 (and all other branches defined to poll) to start a poll. I was hoping that the branches=branch2 in the curl command would tell the git plugin to only cause Jenkins to poll that branch. 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/groups/opt_out.
[JIRA] [git] (JENKINS-18212) Branches get triggered for polling when we don't want them to
Peter Kline updated JENKINS-18212 Branches get triggered for polling when we dont want them to Change By: Peter Kline (12/Nov/13 2:23 PM) Issue Type: Bug Improvement 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/groups/opt_out.
[JIRA] [git] (JENKINS-18212) Branches get triggered for polling when we don't want them to
Peter Kline commented on JENKINS-18212 Branches get triggered for polling when we dont want them to Yes a new enhancement is fine. I thought it was more of a bug since I believed mistakenly that the branch option was intended to do what I wanted (documentation was weak in its function). 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/groups/opt_out.
[JIRA] [ssh] (JENKINS-18379) allow for variable interpolation in site name
Peter Kline
created JENKINS-18379
allow for variable interpolation in site name
Issue Type:
Improvement
Affects Versions:
current
Assignee:
Unassigned
Components:
ssh
Created:
17/Jun/13 7:55 PM
Description:
We have a need to pass in a variable from a slave node to connect to a certain IP address to execute the script.
For example, our master runs a job on slave1.
Slave1 has an environment variable configured of: builder_ip=10.1.1.181
As seen below the echo command is the ${builder_ip}. I need the ssh site name to interpolate that variable as well.
Started by user anonymous
EnvInject - Loading node environment variables.
Building remotely on vmdkDriver1 in workspace /tmp/workspace/concurrency_test
concurrency_test $ /bin/sh -xe /tmp/hudson4711012832981264076.sh
+ echo 10.1.1.181
10.1.1.181
executing script:
hostname
ifconfig eth0
SSH Exception:java.net.UnknownHostException: ${builder_ip}
com.jcraft.jsch.JSchException: java.net.UnknownHostException: ${builder_ip}
at com.jcraft.jsch.Util.createSocket(Util.java:341)
at com.jcraft.jsch.Session.connect(Session.java:182)
at com.jcraft.jsch.Session.connect(Session.java:150)
at org.jvnet.hudson.plugins.SSHSite.createSession(SSHSite.java:118)
at org.jvnet.hudson.plugins.SSHSite.executeCommand(SSHSite.java:128)
at org.jvnet.hudson.plugins.SSHBuilder.perform(SSHBuilder.java:60)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804)
at hudson.model.Build$BuildExecution.build(Build.java:199)
at hudson.model.Build$BuildExecution.doRun(Build.java:160)
at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:586)
at hudson.model.Run.execute(Run.java:1576)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:241)
Caused by: java.net.UnknownHostException: ${builder_ip}
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:175)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:384)
at java.net.Socket.connect(Socket.java:546)
at java.net.Socket.connect(Socket.java:495)
at java.net.Socket.init(Socket.java:392)
at java.net.Socket.init(Socket.java:206)
at com.jcraft.jsch.Util.createSocket(Util.java:335)
... 14 more
Build step 'Execute shell script on remote host using ssh' marked build as failure
Finished: FAILURE
Environment:
Jenkins 1.518
SSH Plugin 2.3
Project:
Jenkins
Priority:
Major
Reporter:
Peter Kline
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/groups/opt_out.
[JIRA] [git] (JENKINS-18212) Branches get triggered for polling when we don't want them to
Peter Kline created JENKINS-18212 Branches get triggered for polling when we dont want them to Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 05/Jun/13 1:06 PM Description: So what I am hoping to do is to prevent polling from happening on any branch besides the one that was changed. I thought by having the "branches=branch2" for example would trigger the plugin to only schedule a polling of that branch. The reason for this functionality is that we need certain users to be able to commit without triggering a build such as admin work/upper level scripts which don't impact our product. Even if I abort a build the next time someone pushes, the force polling will build that branch even though the push wasn't for that specific branch. Below you can see the output of what command we push, I would expect branch2 to kick off a poll but no other branch to do that. remote: branch=branch2, user=peter_kline, repo=flt/root remote: Running command: curl http://jenkins:8080/git/notifyCommit?url=""> remote: Scheduled polling of branch1 remote: Scheduled polling of branch2 remote: Scheduled polling of branch3 remote: Scheduled polling of branch4 remote: Scheduled polling of branch5 remote: Scheduled polling of branch6 remote: Scheduled polling of branch7 remote: Scheduled polling of branch8 remote: Scheduled polling of branch9 remote: Scheduled polling of branch10 remote: Scheduled polling of branch11 remote: Scheduled polling of branch12 remote: Scheduled polling of branch13 remote: Scheduled polling of branch14 To git@gitserver:flt/root.git 9607b14..1daed8c branch2 - branch2 Environment: Jenkins Server: 1.5.10 Git plugin: 1.3.0 Fix Versions: current Project: Jenkins Priority: Critical Reporter: Peter Kline 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/groups/opt_out.
[JIRA] (JENKINS-14336) Too many open files upon HTTP listener init or shutdown
Peter Kline commented on JENKINS-14336 Too many open files upon HTTP listener init or shutdown Same here for us, Jenkins 1.500 on Centos 5.8 Java 1.6.38 Only solution is for us to restart Jenkins. 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/groups/opt_out.
[JIRA] (JENKINS-14211) missing parameter file does not prevent downstream job from running even though it says it will
Peter Kline created JENKINS-14211 missing parameter file does not prevent downstream job from running even though it says it will Issue Type: Bug Affects Versions: current Assignee: huybrechts Components: parameterized-trigger Created: 25/Jun/12 7:06 PM Description: We have a file imagename.txt with a simple key of: imagename=foo.tar The file imagename.txt does not exist as see in the log output below but it still runs anyway. 14:08:56 [parameterizedtrigger] Could not trigger downstream project, as properties fileimagename.txt did not exist. 14:08:56 Triggering a new build of foojob_nightly #1205 Also, not sure why it displays fileimagename.txt over imagename.txt Environment: Jenkins 1.463 and latest plugin Fix Versions: current Project: Jenkins Priority: Critical Reporter: Peter Kline 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
[JIRA] (JENKINS-10550) Please add next-executions plugin to jira component list
[ https://issues.jenkins-ci.org/browse/JENKINS-10550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Peter Kline closed JENKINS-10550. - Assignee: Peter Kline Please add next-executions plugin to jira component list Key: JENKINS-10550 URL: https://issues.jenkins-ci.org/browse/JENKINS-10550 Project: Jenkins Issue Type: Improvement Components: jira Reporter: Peter Kline Assignee: Peter Kline The Next Executions plugin is not listed in the component list: https://wiki.jenkins-ci.org/display/JENKINS/Next+Executions -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9596) SCM polling with GIT creates Spurious Builds with No Changes
[ https://issues.jenkins-ci.org/browse/JENKINS-9596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159691#comment-159691 ] Peter Kline commented on JENKINS-9596: -- This is no longer an issue for us after using the method by Kohsuke: http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ SCM polling with GIT creates Spurious Builds with No Changes -- Key: JENKINS-9596 URL: https://issues.jenkins-ci.org/browse/JENKINS-9596 Project: Jenkins Issue Type: Bug Components: git Affects Versions: current Reporter: Charles Scalfani Assignee: abayer Priority: Minor Attachments: config.xml I see many builds when pushes to non-master branches (I'm only pulling from the master branch). The build is triggered by SCM change but the master branch has the same ID. Here is a discussion on StackOverflow where others are encountering the same problem (http://stackoverflow.com/questions/5784329/how-can-i-make-jenkins-ci-with-git-trigger-on-pushes-to-master). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
