[JIRA] [cli] (JENKINS-24385) Jenkins CLI hangs with InvocationTargetException
Marcel Richter created JENKINS-24385 Jenkins CLI hangs with InvocationTargetException Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins.err.log Components: cli Created: 22/Aug/14 6:00 AM Description: CLI commands hangs with no console output but following Exception in Jenkins.err.log: java -jar jenkins-cli.jar -s http://ciserver:8080/ help _ Environment: Jenkins ver. 1.565.1 Java build 1.7.0_55-b13 Project: Jenkins Labels: cli Priority: Major Reporter: Marcel Richter 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-24385) Jenkins CLI hangs with InvocationTargetException
Marcel Richter
updated JENKINS-24385
Jenkins CLI hangs with InvocationTargetException
Change By:
Marcel Richter
(22/Aug/14 6:09 AM)
Description:
CLIcommandshangswithnoconsoleoutputbutfollowingExceptioninJenkins.err.log:java-jarjenkins-cli.jar-shttp://ciserver:8080/help_
{noformat}Aug22,20146:47:11AMhudson.TcpSlaveAgentListener$ConnectionHandlerrunINFO:Acceptedconnection#3from/192.168.1.200:58954ExceptioninthreadTCPslaveagentconnectionhandler#3with/192.168.1.200:58954java.lang.Error:java.lang.reflect.InvocationTargetExceptionathudson.cli.CliProtocol2$Handler2.run(CliProtocol2.java:76)athudson.cli.CliProtocol2.handle(CliProtocol2.java:32)athudson.TcpSlaveAgentListener$ConnectionHandler.run(TcpSlaveAgentListener.java:157)Causedby:java.lang.reflect.InvocationTargetExceptionatsun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethod)atsun.reflect.NativeMethodAccessorImpl.invoke(UnknownSource)atsun.reflect.DelegatingMethodAccessorImpl.invoke(UnknownSource)atjava.lang.reflect.Method.invoke(UnknownSource)athudson.cli.CliProtocol2$Handler2.run(CliProtocol2.java:63)...2moreCausedby:java.lang.NullPointerExceptionatorg.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:126)...7more{noformat}
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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Mark McNeely created JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. Issue Type: New Feature Affects Versions: current Assignee: lacostej Components: unity3d-plugin Created: 22/Aug/14 6:53 AM Description: Unity Test Tools package will produce an exit code of 2 (partial fail) or 3 (all fail) if there are integration test failures. Currently, the plugin treats 2 and 3 as errors and I am hoping they can be setup mark the build as unstable instead or to have it as an option. The documentation regarding the exit codes of 0, 2, and 3 are available on the 19th page of UnitTestToolsDocsUnitTestTools-en.pdf. Environment: Unity 4.5 and Unity Test Tools 1.4 Project: Jenkins Priority: Minor Reporter: Mark McNeely 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
Mark McNeely updated JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. Change By: Mark McNeely (22/Aug/14 6:54 AM) Description: UnityTestToolspackagewillproduceanexitcodeof2(partialfail)or3(allfail)ifthereareintegrationtestfailures.Currently,theplugintreats2and3aserrorsandIamhopingtheycanbesetup to markthebuildasunstable instead ortohaveitasanoption.Thedocumentationregardingtheexitcodesof0,2,and3areavailableonthe19thpageofUnitTestToolsDocsUnitTestTools-en.pdf. 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] [core] (JENKINS-24361) NullPointerException when trying to log in
Christian Lövsund commented on JENKINS-24361 NullPointerException when trying to log in I have the same issue. Ubuntu 14.04 Jenkins 1.576 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] [ansicolor] (JENKINS-24387) Support parsing output of $(tput sgr0)
Nikolaj Schumacher created JENKINS-24387 Support parsing output of $(tput sgr0) Issue Type: Bug Assignee: Unassigned Components: ansicolor Created: 22/Aug/14 7:47 AM Description: tput is a utility frequently used to set the terminal colors (if TERM is set to xterm). echo "$(tput setaf 3)highlight $(tput sgr0)normal" ansicolor works as expected here, too, however, when using $(tput sgr0) to reset the font properties, ansicolor leaves a "(B " visible. So the output when using ansicolor looks like: highlight normal(B I assume that's a part of the control sequence that ansicolor doesn't yet know about. Project: Jenkins Priority: Minor Reporter: Nikolaj Schumacher 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] [computer-queue] (JENKINS-24267) Use Queue.getApproximateItemsQuickly() not to lock the queue
Oliver Gondža updated JENKINS-24267 Use Queue.getApproximateItemsQuickly() not to lock the queue Change By: Oliver Gondža (22/Aug/14 8:00 AM) Assignee: OliverGondža StevenChristou 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] [computer-queue] (JENKINS-24267) Use Queue.getApproximateItemsQuickly() not to lock the queue
Oliver Gondža resolved JENKINS-24267 as Fixed Use Queue.getApproximateItemsQuickly() not to lock the queue Fixed in 1.4 Change By: Oliver Gondža (22/Aug/14 8:00 AM) Status: Open Resolved Resolution: Fixed 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] [unity3d-plugin] (JENKINS-24386) Unity Test Tools package returns 2 or 3 for failed integration testing.
lacostej commented on JENKINS-24386 Unity Test Tools package returns 2 or 3 for failed integration testing. Hei Mark, this should be very easy to add. Could you do any of these things ? create a minimal sample with unity test tools that can be executed from the command line. Attach it as zip here. perfect if we can fail all or partially (maybe use 2 different methods) if you feel like, send a pull request integration tests go under src/test/resources/org/jenkinsci/plugins/unity3d/IntegrationTests/ and ./src/test/java/org/jenkinsci/plugins/unity3d/IntegrationTests.java 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] [accelerated-build-now] (JENKINS-22349) Jenkins can't sync files from MKS server on master node
Ivan Yan closed JENKINS-22349 as Fixed Jenkins cant sync files from MKS server on master node FIXED Change By: Ivan Yan (22/Aug/14 8:07 AM) Status: Resolved Closed 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bernd Ott edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 No support for 1.8 affect us because we deploy with jenkis using svn checkouts. it's a pain that working directory must say at 1.7. HURRY, to give us 1.8, please. Alternative: drop svn kit and use a svn cli client instead. 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bernd Ott commented on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 No support for 1.8 affect us because we deploy with jenkis using svn checkouts. it's a pain that working directory must say at 1.7. HURRY, to give us 1.8, please. 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] [subversion] (JENKINS-18935) Make Subversion plugin support Subversion 1.8
Bernd Ott edited a comment on JENKINS-18935 Make Subversion plugin support Subversion 1.8 +1 No support for 1.8 affect us because we deploy with jenkis using svn checkouts. it's a pain that working directory must say at 1.7. HURRY, to give us 1.8, please. Alternative: drop svn kit and use a external svn cli client instead. 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Still valid for v1.576. This is very useful for admins that use a periodic fetch on Jenkins job status. For example if I develop Software I wouldn't like to be bombarded with notifications every 5 minutes, so the RSS aggregator (Akregator from KDE in my case) is configured to fetch every hour or so. After enabling authentication this is no longer possible. Also it seems that Akregator's web browser is not able to login. It reports a bug in the login page script: Error: http://jenkins:8080/login?from=%2F: TypeError: Attempt to use a non-function object or a value as a function. Anonymous is denied all access (even read) so the only page you get is the login when you access it. I've tried through basic authentication in the form of the url but it fails (as it's so popularly documented on the web) and even with the API key I couldn't make much progress with regards to the RSS reader. Too bad Jenkins is so powerful but yet so useless after you automate your infrastructure and you are poorly informed (or not at all) on whats going on; whats the point at this moment? Navigating from time to time to the page is not that nice when you only have a few minutes to take only a quick look. 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe commented on JENKINS-6610 RSS Feeds Ought to Accept Credentials Still valid for v1.576. This is very useful for admins that use a periodic fetch on Jenkins job status. For example if I develop Software I wouldn't like to be bombarded with notifications every 5 minutes, so the RSS aggregator (Akregator from KDE in my case) is configured to fetch every hour or so. After enabling authentication this is no longer possible. Also it seems that Akregator's web browser is not able to login. It reports a bug in the login page script: Error: http://jenkins:8080/login?from=%2F: TypeError: Attempt to use a non-function object or a value as a function. Anonymous is denied all access (even read) so the only page you get is the login when you access it. I've tried through basic authentication in the form of the url but it fails (as it's so popularly documented on the web) and even with the API key I couldn't make much progress with regards to the RSS reader. Too bad Jenkins is so powerful but yet so useless after you automate your infrastructure and you are poorly informed (or not at all) on whats going on; whats the point at this moment? Navigating from time to time to the page is not that nice when you only have a few minutes to take only a quick look. 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Still valid for v1.576. This is very useful for admins that use a periodic fetch on Jenkins job status. For example if I develop Software I wouldn't like to be bombarded with notifications every 5 minutes, so the RSS aggregator (Akregator from KDE in my case) is configured to fetch every hour or so. After enabling authentication this is no longer possible. Also it seems that Akregator's web browser is not able to login. It reports a bug in the login page script: Error: http://jenkins:8080/login?from=%2F: TypeError: Attempt to use a non-function object or a value as a function. Anonymous is denied all access (even read) so the only page you get is the login when you access it. I've tried through basic authentication in the form of the url but it fails (as it's so popularly documented on the web) and even with the API key I couldn't make much progress with regards to the RSS reader. Too bad Jenkins is so powerful but yet so useless after you automate your infrastructure and you are poorly informed (or not at all) on whats going on; whats the point at this moment? Navigating from time to time to the page is not that nice when you only have a few minutes to take only a quick look. By the way williamleara what RSS reader are you using and on what O.S.? 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe updated JENKINS-6610 RSS Feeds Ought to Accept Credentials Change By: Alexandru Gheorghe (22/Aug/14 8:20 AM) Labels: usability 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Still valid for v1.576. This is very useful for admins that use a periodic fetch on Jenkins job status. For example if I develop Software I wouldn't like to be bombarded with notifications every 5 minutes, so the RSS aggregator (Akregator from KDE in my case) is configured to fetch every hour or so. After enabling authentication this is no longer possible. Also it seems that Akregator's web browser is not able to login. It reports a bug in the login page script: Error: http://jenkins:8080/login?from=%2F: TypeError: Attempt to use a non-function object or a value as a function. Anonymous is denied all access (even read) so the only page you get is the login when you access it. I've tried through basic authentication in the form of the url but it fails (as it's so popularly documented on the web) and even with the API key I couldn't make much progress with regards to the RSS reader. Too bad Jenkins is so powerful but yet so useless after you automate your infrastructure and you are poorly informed (or not at all) on whats going on; whats the point at this moment? Navigating from time to time to the page is not that nice when you only have a few minutes to take only a quick look. My settings: Jenkins hosted on Ubuntu 12.04.4 LTS Security policy: Matrix per project (with Advanced Project plugin) Users managed from Jenkins own database No anonymous access is allowed Several users configured (some are admins with full privileges, others are limited to their projects/views) By the way williamleara what RSS reader are you using and on what O.S.? 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe updated JENKINS-6610 RSS Feeds Ought to Accept Credentials Attached some screenshots (GNU/Linux Debian 7 with Akregator Version 1.6.6 Using KDE Development Platform 4.8.4 (4.8.4)): 1-akregator_jenkins-Cannot_Fetch_Feed.png can't fetch the feed due to login 2-login_try-akregator_jenkins.png trying to login via Akregator's browser 3-login_failed-akregator_jenkins.png login failed and the supposed bug 4-akregator_jenkins.png a sneak peek on how the announcements look; notice that the title is short and a link is provided, this is very useful when you just want to quickly know what is going on and if needed, go to the url (time is important) Change By: Alexandru Gheorghe (22/Aug/14 8:34 AM) Attachment: 1-akregator_jenkins-Cannot_Fetch_Feed.png Attachment: 2-login_try-akregator_jenkins.png Attachment: 3-login_failed-akregator_jenkins.png Attachment: 4-akregator_jenkins.png 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Attached some screenshots (GNU/Linux Debian 7 with Akregator Version 1.6.6 Using KDE Development Platform 4.8.4 (4.8.4)): color: Color value is not a valid CSS2 color 1-akregator_jenkins-Cannot_Fetch_Feed.png can't fetch the feed due to login color: Color value is not a valid CSS2 color 2-login_try-akregator_jenkins.png trying to login via Akregator's browser color: Color value is not a valid CSS2 color 3-login_failed-akregator_jenkins.png login failed and the supposed bug color: Color value is not a valid CSS2 color 4-akregator_jenkins.png a sneak peek on how the announcements look; notice that the title is short and a link is provided, this is very useful when you just want to quickly know what is going on and if needed, go to the url (time is important) 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Attached some screenshots (GNU/Linux Debian 7 with Akregator Version 1.6.6 Using KDE Development Platform 4.8.4 (4.8.4)): 1-akregator_jenkins-Cannot_Fetch_Feed.png can't fetch the feed due to login 2-login_try-akregator_jenkins.png trying to login via Akregator's browser 3-login_failed-akregator_jenkins.png login failed and the supposed bug 4-akregator_jenkins.png a sneak peek on how the announcements look; notice that the title is short and a link is provided, this is very useful when you just want to quickly know what is going on and if needed, go to the url (time is important) 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] [core] (JENKINS-6610) RSS Feeds Ought to Accept Credentials
Alexandru Gheorghe edited a comment on JENKINS-6610 RSS Feeds Ought to Accept Credentials Attached some screenshots (GNU/Linux Debian 7 with Akregator Version 1.6.6 Using KDE Development Platform 4.8.4 (4.8.4)): 1-akregator_jenkins-Cannot_Fetch_Feed.png can't fetch the feed due to login 2-login_try-akregator_jenkins.png trying to login via Akregator's browser 3-login_failed-akregator_jenkins.png login failed and the supposed bug 4-akregator_jenkins.png a sneak peek on how the announcements look; notice that the title is short and a link is provided, this is very useful when you just want to quickly know what is going on and if needed, go to the url (time is important) 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] [core] (JENKINS-10109) Error 404 with Exception: Stacktrace: (none) when trying to access a job as guest (not logged in)
bhagavan padala assigned JENKINS-10109 to bhagavan padala Error 404 with Exception: Stacktrace: (none) when trying to access a job as guest (not logged in) Change By: bhagavan padala (22/Aug/14 9:00 AM) Assignee: bhagavanpadala 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] [nodejs] (JENKINS-20636) RVM and NodeJS plugins are incompatible
Vanja Radovanović commented on JENKINS-20636 RVM and NodeJS plugins are incompatible I've had the same experience with rbenv plugin. Started by user Vanja Radovanović [EnvInject] - Loading node environment variables. Building remotely on ci-clave (available linux) in workspace /opt/jenkins/workspace/test-project Wiping out workspace first. Cloning the remote Git repository Cleaning workspace $ bash -c "[ -d \$HOME/.rbenv ]" $ bash -c "[ -d \$HOME/.rbenv/plugins/ruby-build ]" Just ignoring local Ruby version. $ bash -c "mkdir \$HOME/.rbenv.lock" $ bash -c "mkdir \$HOME/.rbenv.lock" $ bash -c "mkdir \$HOME/.rbenv.lock" . $ bash -c "mkdir \$HOME/.rbenv.lock" ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-us...@googlegroups.com org.jruby.exceptions.RaiseException: (LockError) could not acquire lock in 1000 seconds. at RUBY.release_lock(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:31) at RUBY.synchronize(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:14) at RUBY.setup!(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv.rb:24) at RUBY.setup(C:/.jenkins/plugins/rbenv/WEB-INF/classes/models/rbenv_wrapper.rb:61) at RUBY.setUp(C:/.jenkins/plugins/rbenv/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/model/environment_proxy.rb:8) project=hudson.maven.MavenModuleSet@9230959[test-project-module] project.getModules()=[hudson.maven.MavenModule@2d785573[test-project/org.test:test-project-module][test-project-module/org.test:test-project-module][relativePath:]] project.getRootModule()=hudson.maven.MavenModule@2d785573[test-project/org.test:test-project-module][test-project-module/org.test:test-project-module][relativePath:] FATAL: (LockError) could not release lock in 1000 secs. org.jruby.exceptions.RaiseException: (LockError) could not release lock in 1000 secs. at RUBY.release_lock(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:44) at RUBY.synchronize(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv/semaphore.rb:17) at RUBY.setup!(C:/.jenkins/plugins/rbenv/WEB-INF/classes/lib/rbenv.rb:24) at RUBY.setup(C:/.jenkins/plugins/rbenv/WEB-INF/classes/models/rbenv_wrapper.rb:61) at RUBY.setUp(C:/.jenkins/plugins/rbenv/WEB-INF/classes/vendor/gems/gems/jenkins-plugin-runtime-0.2.3/lib/jenkins/model/environment_proxy.rb:8) I've tried with an updated version of NodeJS plugin that uses jenkins parent 1.575 and maven-hpi-plugin 1.106 but without any luck. From what I see, rbenv plugin can execute native bash commands normally (e.g. directory location testing) but the PATH is not set for it so commands like mkdir, git, env and others just fail. When I turn off the NodeJS plugin from the job configuration, everything works as expected. We use Jenkins 1.575. The master is a windows machine and the slave is CentOS one. 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin when i access the xml api then i get: Stack trace java.io.IOException: Failed to write jobs at org.kohsuke.stapler.export.Property.writeTo(Property.java:120) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:187) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:182) at org.kohsuke.stapler.export.Model.writeTo(Model.java:154) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doXml(Api.java:98) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:120) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:210) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:86) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at
[JIRA] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin After looking through the stack trace i saw that there might have been some issues with the jobs that were there. They were jobs imported from another instance and might have been lacking some configurations. I deleted them and the page works. Now a non-admin can create and configure a job correctly. Thanks for pointing me in the right direction! 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin Ill continue digging to see which/what config actually caused the exception 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] [docker-build-step] (JENKINS-24388) Add registry authentication
Adam McMaster created JENKINS-24388 Add registry authentication Issue Type: Improvement Assignee: vjuranek Components: docker-build-step Created: 22/Aug/14 11:02 AM Description: The Docker Hub allows private images which can only be pulled by authenticated users. It would be nice to be able to pull these from Jenkins. docker-java already supports authentication (see https://github.com/docker-java/docker-java#configuration), so hopefully this wouldn't be hard to implement. Project: Jenkins Priority: Minor Reporter: Adam McMaster 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] [core] (JENKINS-14993) JDK auto-installer for OSX
lacostej updated JENKINS-14993 JDK auto-installer for OSX Here's a script that can be used to intall the JDK from the command line. It uses sudo and at some points it requests the user password. Combined with the credentials plugin, it could be used to install the JDK on Mac OS X. WDYT ? Change By: lacostej (22/Aug/14 11:30 AM) Attachment: install_jdk.sh 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] (JENKINS-24368) Authentication failed for https://usern...@bitbucket.org/project/repository.git
Mark Waite updated JENKINS-24368 Authentication failed for https://usern...@bitbucket.org/project/repository.git Change By: Mark Waite (22/Aug/14 11:42 AM) Component/s: git 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] [core] (JENKINS-23471) Channel reader thread consumes all CPUs
Olaf Lenz commented on JENKINS-23471 Channel reader thread consumes all CPUs I also see this happening sometimes. Each of the threads causes a load of +1, so this can easily lead to the jenkins server causing a load of 20. It does not seem to be connected to anything happening on the node, like a job getting started, but it does seem to coincide with some action happening at the GUI. BTW, I am running the Jenkins LTS, i.e. Jenkins 1.565.1. If I can help to find the bug, let me know. My experiences with Java debugging are small. 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] [xcode] (JENKINS-13887) Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build
lacostej commented on JENKINS-13887 Ability to change the Bundle identifier (CFBundleIdentifier) for an xcode build Esteban's code was merged in and will be available in the next release. 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] [xcode] (JENKINS-12510) Custom xcodebuild arguments values are not persisted
lacostej resolved JENKINS-12510 as Fixed Custom xcodebuild arguments values are not persisted Marked as solved again as we cannot reproduce. Change By: lacostej (22/Aug/14 12:04 PM) Status: Reopened Resolved Assignee: ArnaudHéritier lacostej Resolution: Fixed 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] [xcode] (JENKINS-12510) Custom xcodebuild arguments values are not persisted
lacostej commented on JENKINS-12510 Custom xcodebuild arguments values are not persisted I tested locally with a recent jenkins (Jenkins ver. 1.565.1) and a new project with xcode builder. The field appears in the config when saved. xcodebuildArgumentsSELECTED_LOCALE=en/xcodebuildArguments xcodeSchema/xcodeSchema xcodeWorkspaceFile/xcodeWorkspaceFile I am using ce1992dc36a1322de363fb16eafa3e5f23af9779 (1.4.3-alpha) version of the plugin and I don't see changes that could affect this. I am going to close this issue. If you face the issue again, let us know and we will investigate this further. 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin seems the plugin is throwing an NPE here https://github.com/jenkinsci/github-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/GithubRequireOrganizationMembershipACL.java#L260 Do you have any idea why this variable may be null (githubRepositoryName) 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] [external-resource-dispatcher] (JENKINS-24389) Access to Metadata of dispached resource
Henrik Herwig created JENKINS-24389 Access to Metadata of dispached resource Issue Type: New Feature Assignee: rsandell Components: external-resource-dispatcher, metadata-plugin Created: 22/Aug/14 12:53 PM Description: It would be nice to have access to the metadata of the dispated recource to get device specific information for a generic job. Project: Jenkins Priority: Major Reporter: Henrik Herwig 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] [core] (JENKINS-23471) Channel reader thread consumes all CPUs
Olaf Lenz commented on JENKINS-23471 Channel reader thread consumes all CPUs A further observation, which may give an idea: I just saw this happening when starting jenkins. In the jenkins log, I noticed that it tried to start the slave on a node twice. And that was apparently the thread that causes the high load. From the log: Aug 21, 2014 5:07:27 PM hudson.slaves.SimpleScheduledRetentionStrategy check INFO: Trying to launch computer cip20 as schedule says it should be on-line at this point in time ... [clip] ... Effective SlaveRestarter on master: null Aug 21, 2014 5:07:29 PM hudson.WebAppMain$3 run INFO: Jenkins is fully up and running [08/21/14 17:07:30] SSH Launch of cip12 on cip12 failed in 3,013 ms ... [clip] ... INFO: Trying to launch computer cip20 as schedule says it should be on-line at this point in time Aug 21, 2014 5:08:17 PM hudson.node_monitors.AbstractNodeMonitorDescriptor$Record init 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] [core] (JENKINS-24384) Not able to get update for jenkins in Ubuntu
Daniel Beck updated JENKINS-24384 Not able to get update for jenkins in Ubuntu Change By: Daniel Beck (22/Aug/14 1:17 PM) Component/s: core Component/s: jenkins-tracker 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] [core] (JENKINS-24384) Not able to get update for jenkins in Ubuntu
Daniel Beck resolved JENKINS-24384 as Not A Defect Not able to get update for jenkins in Ubuntu Not clear whether this is a defect with Jenkins (e.g. its repos). For requests for assistance, please ask the jenkinsci-users mailing list, or in #jenkins on Freenode. Change By: Daniel Beck (22/Aug/14 1:17 PM) Status: Open Resolved Resolution: NotADefect 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] [core] (JENKINS-10109) Error 404 with Exception: Stacktrace: (none) when trying to access a job as guest (not logged in)
Daniel Beck commented on JENKINS-10109 Error 404 with Exception: Stacktrace: (none) when trying to access a job as guest (not logged in) Is this still unresolved? The following is how it's supposed to work (assuming matrix permissions strategy or similar) If anonymous does not have the Overall/Read permission, it always presents a login for. If anonymous has this permission, it depends on whether he has Item/Discover. If so, a login form should be presented, otherwise it should be an error page to hide the existence of the resource. 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] [confluence-publisher] (JENKINS-15472) Option to create a new page
SCM/JIRA link daemon commented on JENKINS-15472 Option to create a new page Code changed in jenkins User: Trevor Hill Path: src/main/java/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher.java src/main/resources/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher/config.jelly src/main/resources/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher/help-parentId.html http://jenkins-ci.org/commit/confluence-publisher-plugin/204a8d61e9bef49bfee586260d87219597263984 Log: FIXED JENKINS-15472 Added parentId property Added a new job-configuration field for parent page ID#. Plugin verifies that page ID exists and returns an error message if not. 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] [confluence-publisher] (JENKINS-15472) Option to create a new page
SCM/JIRA link daemon resolved JENKINS-15472 as Fixed Option to create a new page Change By: SCM/JIRA link daemon (22/Aug/14 2:04 PM) Status: Reopened Resolved Resolution: Fixed 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] [confluence-publisher] (JENKINS-15472) Option to create a new page
SCM/JIRA link daemon commented on JENKINS-15472 Option to create a new page Code changed in jenkins User: Joe Path: src/main/java/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher.java src/main/resources/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher/config.jelly src/main/resources/com/myyearbook/hudson/plugins/confluence/ConfluencePublisher/help-parentId.html http://jenkins-ci.org/commit/confluence-publisher-plugin/feb61cb2d6b17db746eba410d6478c361956e9f7 Log: Merge pull request #7 from trevor-hill/master FIXED JENKINS-15472 Added parentId property Compare: https://github.com/jenkinsci/confluence-publisher-plugin/compare/d7e9c4f4a48d...feb61cb2d6b1 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] [nodejs] (JENKINS-24381) NodeJS Plugin installs while other jobs are running, breaking builds
Travis Cosgrave commented on JENKINS-24381 NodeJS Plugin installs while other jobs are running, breaking builds I guess I didn't write this issue properly. I believe it is a bug. I'll edit the description to better reflect a bug. 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] [nodejs] (JENKINS-24381) NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Travis Cosgrave
updated JENKINS-24381
NodeJS Plugin runs auto-install while other dependant jobs are running, breaking builds
Change By:
Travis Cosgrave
(22/Aug/14 2:16 PM)
Summary:
NodeJSPlugin
installs
runsauto-install
whileother
dependant
jobsarerunning,breakingbuilds
Description:
Ihave
With
multiplejobsconfiguredtousethesameNodeJSInstaller
.Asaresult
,
sometimesone
say
job
isrunning
AandjobB,
the
installertoupdatethecachewhileanotheronestarts.Itseemsasifallofnodeisremovedmakingcommandsunavailable.Itlookslikeitseventhappenedduringabuildresulting
auto-installoptionresults
in
jobBfailingwhenjobAtriggers
a
filenotfounderror
NodeJSinstall
.
Isthereaway
ThisisespeciallyanissuewhenmultiplejobsrelyingonthesameNodeJSinstallaretriggered
to
share
runatthesametimeviasourcecontrol,andallofthejobstrytouse
a
nodejsinstallerwithmultiplebuilds
package
that
mayrunconcurrently?
hasbeenremovedbyfirsttheauto-installprocess.
ThisistheerrorIreceivedduringthemiddleofmyjob,after
already
using
thispackageawholebunchoftimebefore
the
error
referencedmoduleduringtherunningjob
.{code}Error:ENOENT,nosuchfileordirectory/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/atObject.fs.readdirSync(fs.js:654:18)atloadCommandFiles(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:166:27)atloadClientCommands(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:158:5)atmodule.exports.load(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/core/api.js:381:5)atnewNightwatch(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:41:18)atObject.exports.client(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/index.js:432:10)atrunModule(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:142:27)atrunTestModule(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:481:7)atnull._onTimeout(/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/runner/run.js:484:13)atTimer.listOnTimeout[asontimeout](timers.js:110:15)ENOENT,nosuchfileordirectory/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/0.10.25_nightwatch_karma_grunt/lib/node_modules/nightwatch/lib/selenium/commands/+true{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] [p4] (JENKINS-24342) Plugin invalidates ticket when testing connection and using P4TICKETS
Paul Allen closed JENKINS-24342 as Fixed Plugin invalidates ticket when testing connection and using P4TICKETS Patched in 1.0.13 Change By: Paul Allen (22/Aug/14 2:19 PM) Status: Open Closed Resolution: Fixed 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] [p4] (JENKINS-24189) Need more info on Perforce credential connection error
Paul Allen commented on JENKINS-24189 Need more info on Perforce credential connection error I have added more error logging and a second stage where the connection URI path is checked before establishing a Perforce connection. 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] [p4] (JENKINS-24189) Need more info on Perforce credential connection error
Paul Allen closed JENKINS-24189 as Fixed Need more info on Perforce credential connection error Patched in 1.0.13 Change By: Paul Allen (22/Aug/14 2:20 PM) Status: Open Closed Resolution: Fixed 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] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Paul Allen commented on JENKINS-24202 Pin Build at Label Does not Sync at the CL of the Label Please can you check this with 1.0.13; I'm hoping it is fixed with all the other label updates. 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] [p4] (JENKINS-24187) Perforce Credential 'Trust' field needs explantion ( ie implement the '?')
Paul Allen closed JENKINS-24187 as Fixed Perforce Credential Trust field needs explantion ( ie implement the ?) I have added error reporting with the Server's Trust fingerprint. Perhaps I should add a help bubble, but is this really necessary? Change By: Paul Allen (22/Aug/14 2:24 PM) Status: Open Closed Resolution: Fixed 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] [p4] (JENKINS-24202) Pin Build at Label Does not Sync at the CL of the Label
Ryan Hummer commented on JENKINS-24202 Pin Build at Label Does not Sync at the CL of the Label Will do. Thanks! 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-24385) Jenkins CLI hangs with InvocationTargetException
Daniel Beck commented on JENKINS-24385 Jenkins CLI hangs with InvocationTargetException Is Jenkins running (rather than initializing/restarting/... at the time you run that command? 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Daniel Beck commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin The URL provided from somewhere isn't a valid Git URL: https://github.com/jenkinsci/github-oauth-plugin/blob/master/src/main/java/org/jenkinsci/plugins/GitHubRepositoryName.java#L89 Probably missing configuration somewhere. Still, seems unnecessarily brittle and should probably be fixed in the 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.
[JIRA] [p4] (JENKINS-24390) P4TICKETS credential should honor default values
dan tran created JENKINS-24390 P4TICKETS credential should honor default values Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: p4 Created: 22/Aug/14 3:05 PM Description: Looks like P4Jenkins requires user to explicitly enter the location of the ticket files. Is it intended? Project: Jenkins Priority: Major Reporter: dan tran 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley commented on JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin Yep you're correct. My issue is resolved. Turned out the job that was copied over had an environment variable for the repository which was null in the new Jenkins instance. I would assume the plugin would hide the job if it couldn't determine if you had access to view it or something. so I agree, this edge case should be handled better 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley
commented on JENKINS-24383
Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin
To be precise this involved the Workspace sharing plugin. There is an environment variable that is set when the job runs ${SHAREDSPACE_SCM_URL}. which give you access to the git url.
GitHub oauth plugin checks each job when authenticating the view for the git repo url. Because the job is not running the variable is null.
Completely avoiding this variable resolved my issue
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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley updated JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin Change By: Layton Whiteley (22/Aug/14 3:31 PM) Component/s: shared-workspace 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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Layton Whiteley
edited a comment on JENKINS-24383
Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin
To be precise this involved the Workspace sharing plugin (id:'shared-workspace'). There is an environment variable that is set when the job runs ${SHAREDSPACE_SCM_URL}. which give you access to the git url.
GitHub oauth plugin checks each job when authenticating the view for the git repo url. Because the job is not running the variable is null.
Completely avoiding this variable resolved my issue
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] [github-oauth] (JENKINS-24383) Exception when viewing pages after 'Use Github repository permissions' is enabled for github-oauth plugin
Daniel Beck updated JENKINS-24383 Exception when viewing pages after Use Github repository permissions is enabled for github-oauth plugin Change By: Daniel Beck (22/Aug/14 3:33 PM) Component/s: security 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] [confluence-publisher] (JENKINS-15472) Option to create a new page
Joe Hansche closed JENKINS-15472 as Fixed Option to create a new page Change By: Joe Hansche (22/Aug/14 3:41 PM) Status: Resolved Closed 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] [core] (JENKINS-9430) zip of workspace folders does garble filenames with german characters.
Daniel Beck commented on JENKINS-9430 zip of workspace folders does garble filenames with german characters. Johannes Schmieder: To clarify, it depends on the JVM version, and it works correctly with 1.7, but doesn't with 1.6? Also, if you could test 1.574 or newer would be great, as that contained a related change (JENKINS-20663). 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] [hipchat] (JENKINS-24391) HipChat plugin stopped working after 1.7 upgrade
Gennady Feldman created JENKINS-24391 HipChat plugin stopped working after 1.7 upgrade Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: hipchat Created: 22/Aug/14 4:12 PM Description: No hipchat notifications received. Also see this in the logs: Error posting to HipChat java.net.UnknownHostException: null at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:178) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:579) at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:618) at sun.security.ssl.SSLSocketImpl.init(SSLSocketImpl.java:407) at sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88) at hudson.util.NoClientBindSSLProtocolSocketFactory.createSocket(NoClientBindSSLProtocolSocketFactory.java:135) at hudson.util.NoClientBindSSLProtocolSocketFactory.createSocket(NoClientBindSSLProtocolSocketFactory.java:117) at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:707) at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDirector.java:387) at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirector.java:171) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:397) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:323) at jenkins.plugins.hipchat.StandardHipChatService.publish(StandardHipChatService.java:48) at jenkins.plugins.hipchat.ActiveNotifier.notifyStart(ActiveNotifier.java:53) at jenkins.plugins.hipchat.ActiveNotifier.started(ActiveNotifier.java:46) at jenkins.plugins.hipchat.HipChatNotifier$HipChatJobProperty.prebuild(HipChatNotifier.java:203) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:806) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:801) at hudson.model.AbstractBuild$AbstractBuildExecution.preBuild(AbstractBuild.java:797) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532) at hudson.model.Run.execute(Run.java:1740) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:233) I tried going into global config and hitting save. Makes no difference, rolling back to 1.6 for now. Project: Jenkins Priority: Critical Reporter: Gennady Feldman 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-21086) jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown
Daniel Beck commented on JENKINS-21086 jenkins-cli requires Overall/Read permission for anonymous to perform a safe-shutdown I expect this to be fixed in Jenkins 1.577 with the fix for JENKINS-23988. Please download that and test once it's available. 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] [maven2] (JENKINS-4861) Post-build deployment of Maven artifacts does not work with scpexe-type repository
Raúl Wegmann updated JENKINS-4861 Post-build deployment of Maven artifacts does not work with scpexe-type repository We are seeing this problem again when using any Jenkins version greater than 1.559 so that we have been stuck for the last few months with that version. Apparently some CLI escaping issues have been fixed in the plexus-utils library since version 3.0.10, which is the one included in the maven-plugin, and I believe that this bug may have been fixed since 3.0.16 (https://jira.codehaus.org/browse/PLXUTILS-161). Please consider including the changes of the following pull request that fixes this error by bumping the plexus-utils version to the most recent one (3.0.17): https://github.com/jenkinsci/maven-plugin/pull/28 Change By: Raúl Wegmann (22/Aug/14 4:30 PM) Priority: Major 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] [cli] (JENKINS-23988) @CLIMethods do not support authentication via SecurityRealm's CLIAuthenticator
Daniel Beck assigned JENKINS-23988 to Daniel Beck @CLIMethods do not support authentication via SecurityRealms CLIAuthenticator Change By: Daniel Beck (22/Aug/14 4:33 PM) Assignee: DanielBeck 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] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Ferzan Rizvi created JENKINS-24392 Manual Build Trigger invoke job on different folder level Issue Type: Bug Assignee: Unassigned Attachments: CD-View-Plugin-Stacktrace.txt Components: delivery-pipeline Created: 22/Aug/14 5:31 PM Description: Job View Folder Structure: RootFolder/ CD View SubFolder/ JobA-Initial JobB-Manual JobA-Initial - (Manual Trigger) - JobB-Manual If the delivery pipeline view is created at a different folder level than where the manually triggered job is located, it throws a null pointer exception. I've tried multiple combinations of specifying the absolute path, relative path from the view but, it will not take. The relative path from the view would probably work to manually trigger the job from the view but it does not display the job in pipeline view because when it reads the trigger chain specified in the jobs, the job folder location will be incorrect. Environment: Cloudbees Jenkins Project: Jenkins Priority: Major Reporter: Ferzan Rizvi 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] [github] (JENKINS-19775) Github plugin - Set build status on github commit - No result
Ben Bracha commented on JENKINS-19775 Github plugin - Set build status on github commit - No result Hey, I tried this option with git plugin and cannot see any build status on my git-hub project. My project is on private repository, but I don't think this should change. Should I add something to the project README in order this to work? 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] [cluster-stats] (JENKINS-23712) Exceptions in multi-conf jobs and concurrents executions
Shannon Kerr assigned JENKINS-23712 to toomasr Exceptions in multi-conf jobs and concurrents executions I think this person maintains this plugin. Change By: Shannon Kerr (22/Aug/14 6:05 PM) Assignee: toomasr 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] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
SCM/JIRA link daemon
commented on JENKINS-23963
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/resources/hudson/model/Computer/sidepanel.jelly
core/src/main/resources/hudson/slaves/SlaveComputer/sidepanel2.jelly
http://jenkins-ci.org/commit/jenkins/c45d6be237de4b588c59395b6bcd9a8dc63a7383
Log:
FIXED JENKINS-23963 Use absolute sidepanel links for computers
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] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
SCM/JIRA link daemon
resolved JENKINS-23963 as Fixed
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Change By:
SCM/JIRA link daemon
(22/Aug/14 6:07 PM)
Status:
InProgress
Resolved
Resolution:
Fixed
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] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
SCM/JIRA link daemon
commented on JENKINS-23963
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Code changed in jenkins
User: Daniel Beck
Path:
core/src/main/resources/hudson/model/Computer/sidepanel.jelly
core/src/main/resources/hudson/slaves/SlaveComputer/sidepanel2.jelly
http://jenkins-ci.org/commit/jenkins/e2d9fdc9894bed799893f85f2e884c3567805730
Log:
Merge pull request #1378 from daniel-beck/JENKINS-23963
FIXED JENKINS-23963 Use absolute sidepanel links for computers
Compare: https://github.com/jenkinsci/jenkins/compare/1b9cc8aa1f5e...e2d9fdc9894b
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] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
dogfood
commented on JENKINS-23963
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
Integrated in jenkins_main_trunk #3644
FIXED JENKINS-23963 Use absolute sidepanel links for computers (Revision c45d6be237de4b588c59395b6bcd9a8dc63a7383)
Result = SUCCESS
daniel-beck : c45d6be237de4b588c59395b6bcd9a8dc63a7383
Files :
core/src/main/resources/hudson/slaves/SlaveComputer/sidepanel2.jelly
core/src/main/resources/hudson/model/Computer/sidepanel.jelly
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] [docker-build-step] (JENKINS-24071) Docker build step tries to build on master and not slave
Hack Kampbjørn reopened JENKINS-24071 Docker build step tries to build on master and not slave After updating to version 1.9 it now fails with a java.io.NotSerializableException 16:02:43 FATAL: Unable to serialize org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DockerCmdCallable@3235025a 16:02:43 java.io.IOException: Unable to serialize org.jenkinsci.plugins.dockerbuildstep.DockerBuilder$DockerCmdCallable@3235025a 16:02:43 at hudson.remoting.UserRequest.serialize(UserRequest.java:166) 16:02:43 at hudson.remoting.UserRequest.init(UserRequest.java:62) 16:02:43 at hudson.remoting.Channel.call(Channel.java:738) 16:02:43 at org.jenkinsci.plugins.dockerbuildstep.DockerBuilder.perform(DockerBuilder.java:67) 16:02:43 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) 16:02:43 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:772) 16:02:43 at hudson.model.Build$BuildExecution.build(Build.java:199) 16:02:43 at hudson.model.Build$BuildExecution.doRun(Build.java:160) 16:02:43 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:535) 16:02:43 at hudson.model.Run.execute(Run.java:1732) 16:02:43 at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) 16:02:43 at hudson.model.ResourceController.execute(ResourceController.java:88) 16:02:43 at hudson.model.Executor.run(Executor.java:234) 16:02:43 Caused by: java.io.NotSerializableException: hudson.model.FreeStyleBuild 16:02:43 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1164) 16:02:43 at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1518) 16:02:43 at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1483) 16:02:43 at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1400) 16:02:43 at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1158) 16:02:43 at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) 16:02:43 at hudson.remoting.UserRequest._serialize(UserRequest.java:155) 16:02:43 at hudson.remoting.UserRequest.serialize(UserRequest.java:164) 16:02:43 ... 12 more Change By: Hack Kampbjørn (22/Aug/14 7:10 PM) Resolution: Fixed Status: Resolved Reopened 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] [ldap] (JENKINS-24393) Cannot login w/ LDAP
Fory Horio created JENKINS-24393 Cannot login w/ LDAP Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: ldap Created: 22/Aug/14 7:30 PM Description: Just upgraded to the latest. Now, I cannot login using LDAP auth. Not sure how I can solve this. Is there a way to login (back door)? Environment: Jenkins ver. 1.576 on Ubuntu 12.04.5 LTS Project: Jenkins Priority: Blocker Reporter: Fory Horio 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] [core] (JENKINS-23963) Computer's sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
evernat
commented on JENKINS-23963
Computers sidepanel.jelly should use ${rootURL}/${it.url} instead of relative URLs
thanks
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] [ldap] (JENKINS-24393) Cannot login w/ LDAP
Fory Horio updated JENKINS-24393 Cannot login w/ LDAP Change By: Fory Horio (22/Aug/14 7:55 PM) Attachment: jenkins.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] [delivery-pipeline] (JENKINS-24392) Manual Build Trigger invoke job on different folder level
Daniel Beck commented on JENKINS-24392 Manual Build Trigger invoke job on different folder level The formatting of your description needs some 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/d/optout.
[JIRA] [ldap] (JENKINS-24393) Cannot login w/ LDAP
Daniel Beck resolved JENKINS-24393 as Duplicate Cannot login w/ LDAP Change By: Daniel Beck (22/Aug/14 7:57 PM) Status: Open Resolved Assignee: KohsukeKawaguchi 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Michael Rose
reopened JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
I just tried to executed a matrix build with a mixture of user defined axis and node label axis. The parent build properly sync'd and triggered the configuration builds, but all of the configuration build failed in the following way:
Started by upstream project "test-new-p4plugin" build number 12
originally caused by:
Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on b261806 (linux x86_64-Linux-2.618) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/222/foo/xxx/label/linux
ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/bar=222,foo=xxx,label=linux/...' is not under '//JenkinsJob_test-new-p4plugin-bar-222-foo-xxx-label-linux/...'.
ERROR: Unable to setup workspace: com.perforce.p4java.exception.RequestException: Error in client specification.
Mapping '//JenkinsJob_test-new-p4plugin/bar=222,foo=xxx,label=linux/...' is not under '//JenkinsJob_test-new-p4plugin-bar-222-foo-xxx-label-linux/...'.
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE
I am using the Manual (custom view) with workspace name set to JenkinsJob_${JOB_NAME} and view set to //test_mrose/... //JenkinsJob_${JOB_NAME}/...
P4 plugin version: 1.0.12
Jenkins version: 1.575
Change By:
Michael Rose
(22/Aug/14 8:07 PM)
Resolution:
Fixed
Status:
Closed
Reopened
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] [gerrit-trigger] (JENKINS-24394) Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base
James Rawlings created JENKINS-24394 Gerrit trigger plugin doesnt update Gerrit with review comments using the latest Gerrit code base Issue Type: Bug Affects Versions: current Assignee: rsandell Components: gerrit-trigger Created: 22/Aug/14 8:21 PM Description: If you are having issues sending any review comments to Gerrit, after investigation I found using the command line feature of Gerrit that you need to remove the verified flag from the default 'Gerrit Verified Commands'. I'm building Gerrit from source at the date of this post and suspect it will affect the current release candidate Gerrit 2.10-rc0 Steps in Jenkins.. Manage Jenkins Gerrit Trigger select your gerrit server Advanced edit all lines that include the --verified flag, for example.. gerrit review CHANGE,PATCHSET --message 'Build Started BUILDURL STARTED_STATS' --verified VERIFIED --code-review CODE_REVIEW to gerrit review CHANGE,PATCHSET --message 'Build Started BUILDURL STARTED_STATS' --code-review CODE_REVIEW Project: Jenkins Priority: Major Reporter: James Rawlings 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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Michael Rose
commented on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Here is another strange issue. The parent sync'd successfully, but the other configurations did this:
Started by upstream project "test-new-p4plugin" build number 13
originally caused by:
Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on nile (linux) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/111/foo/xxx/label/linux
Connected to server: perforce2.csdt.sjm.com:1777
Connected to client: JenkinsJob_myspace
SCM Task: cleanup workspace: JenkinsJob_myspace
SCM Task: reverting all pending and shelved revisions.
... list = revert
... rm list | ABANDONED
SCM Task: removing all non-versioned files.
... list = reconcile -n -a
... rm list
SCM Task: restoring all missing and changed revisions.
... list = reconcile -n -ed
... sync -f list
P4: Unable to find label: linux
ERROR: Unable to update workspace: hudson.AbortException: P4: Unable to find label: linux
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE
This time I used a static workspace name, but updated the matrix configuration to build sequentially so there wouldn't be any client clobbering.
Client Name: JenkinsJob_myspace
Client View: //test_mrose/... //JenkinsJob_myspace/...
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] [p4] (JENKINS-24028) using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Michael Rose
edited a comment on JENKINS-24028
using ${JOB_NAME} in Workspace Name Format fails in Matrix jobs
Here is another strange issue. The parent sync'd successfully, but the other configurations did this:
Started by upstream project "test-new-p4plugin" build number 13
originally caused by:
Started by user Rose, Michael
EnvInject - Loading node environment variables.
Building remotely on nile (linux) in workspace /var/tmp/jenkins/workspace/test-new-p4plugin/bar/111/foo/xxx/label/linux
Connected to server: perforce2.csdt.sjm.com:1777
Connected to client: JenkinsJob_myspace
SCM Task: cleanup workspace: JenkinsJob_myspace
SCM Task: reverting all pending and shelved revisions.
... list = revert
... rm list | ABANDONED
SCM Task: removing all non-versioned files.
... list = reconcile -n -a
... rm list
SCM Task: restoring all missing and changed revisions.
... list = reconcile -n -ed
... sync -f list
P4: Unable to find label: linux
ERROR: Unable to update workspace: hudson.AbortException: P4: Unable to find label: linux
Started calculate disk usage of build
Finished Calculation of disk usage of build in 0 seconds
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
Finished: FAILURE
This time I used a static workspace name, but updated the matrix configuration to build sequentially so there wouldn't be any client clobbering.
Client Name: JenkinsJob_myspace
Client View: //test_mrose/... //JenkinsJob_myspace/...
The same issue occurs when using streams.
Character Set: none
Stream Codeline: //test_streams/main
Workspace Name Format: jenkins-${NODE_NAME}-${JOB_NAME}
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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
thetaphi created JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 Issue Type: Bug Assignee: Alex Earl Components: email-ext Created: 22/Aug/14 9:17 PM Description: I updated to the RC build of Jenkins: Jenkins ver. 1.577-SNAPSHOT (rc-08/21/2014 13:41 GMT-jenkins) The problem with the email-ext plugin here is the following fatal error on sending e-mail after failed build: Build step 'Invoke Ant' marked build as failure [description-setter] Description set: Java: 64bit/jdk1.7.0_67 -XX:-UseCompressedOops -XX:+UseParallelGC Archiving artifacts Recording test results Email was triggered for: Failure - Any Sending email for trigger: Failure - Any ERROR: Publisher hudson.plugins.emailext.ExtendedEmailPublisher aborted due to exception java.lang.NoSuchMethodError: hudson.model.AbstractBuild.getTestResultAction()Lhudson/tasks/test/AbstractTestResultAction; at hudson.plugins.emailext.plugins.content.FailedTestsContent.evaluate(FailedTestsContent.java:47) at org.jenkinsci.plugins.tokenmacro.DataBoundTokenMacro.evaluate(DataBoundTokenMacro.java:189) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:182) at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:233) at hudson.plugins.emailext.plugins.ContentBuilder.transformText(ContentBuilder.java:71) at hudson.plugins.emailext.ExtendedEmailPublisher.getContent(ExtendedEmailPublisher.java:597) at hudson.plugins.emailext.ExtendedEmailPublisher.createMail(ExtendedEmailPublisher.java:476) at hudson.plugins.emailext.ExtendedEmailPublisher.sendMail(ExtendedEmailPublisher.java:290) at hudson.plugins.emailext.ExtendedEmailPublisher._perform(ExtendedEmailPublisher.java:281) at hudson.plugins.emailext.ExtendedEmailPublisher.perform(ExtendedEmailPublisher.java:233) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1786) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered Finished: FAILURE This is caused by a signature change of the return type of this method in this commit to Jenkins core: https://github.com/jenkinsci/jenkins/commit/16197ea502bc2f370f70b65242b9ccb2f0583372 I am not sure how to fix this, reflection might be an option. Another option is to build a new version of this plugin. Project: Jenkins Priority: Major Reporter: thetaphi 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen commented on JENKINS-22820 Changes are not commited when using a recent git client After some research, I figured out how to downgrade git to the version in Ubuntu 13.10. I created "/etc/apt/sources.list.d/sausy.list" with these contents: I need access to the 13.10 repositories so that I can downgrade git deb http://us.archive.ubuntu.com/ubuntu/ saucy main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ saucy main restricted I ran aptitude and did an update (the equivalent of apt-get update). After that, I was able to find the older version of git and install it. I used dependency resolver in aptitude to downgrade the dependencies. If you are using apt-get, you can avoid this by uninstalling git first. I still have the problem described here: https://issues.jenkins-ci.org/browse/JENKINS-22666 I tried downgrading the scm-sync-plugin to 0.0.7.3, but it did not fix the problem 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
David Cullen edited a comment on JENKINS-22820 Changes are not commited when using a recent git client After some research, I figured out how to downgrade git to the version in Ubuntu 13.10. I created "/etc/apt/sources.list.d/sausy.list" with these contents: # I need access to the 13.10 repositories so that I can downgrade git deb http://us.archive.ubuntu.com/ubuntu/ saucy main restricted deb-src http://us.archive.ubuntu.com/ubuntu/ saucy main restricted I ran aptitude and did an update (the equivalent of apt-get update). After that, I was able to find the older version of git and install it. I used dependency resolver in aptitude to downgrade the dependencies. If you are using apt-get, you can avoid this by uninstalling git first. I still have the problem described here: https://issues.jenkins-ci.org/browse/JENKINS-22666 I tried downgrading the scm-sync-plugin to 0.0.7.3, but it did not fix the problem 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] [template-project] (JENKINS-24396) Support for the Cloudbees folder plugin
Morne Joubert created JENKINS-24396 Support for the Cloudbees folder plugin Issue Type: New Feature Assignee: huybrechts Components: template-project Created: 22/Aug/14 9:43 PM Description: I can use builders from projects if they are not inside a folder (using Cloudbees folder plugin) As soon as the other project is in a folder it doesn't work. Is it suppose to work or is this a known issue ? Project: Jenkins Priority: Major Reporter: Morne Joubert 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Alex Earl commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 Email-ext is built and tested against the LTS. Until something after 1.577 becomes an LTS, this won't be fixed. 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
thetaphi commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 This now breaks Apache Lucene/Solr builds that need this newer Jenkins. Too bad... Can we build the plugin from source? To me it looks like maybe we can create a branch and build ourselves. 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] [hockeyapp] (JENKINS-24177) Use release notes since last successful build as changelog
Brenton B commented on JENKINS-24177 Use release notes since last successful build as changelog Possible combination with https://wiki.jenkins-ci.org/display/JENKINS/Changes+Since+Last+Success+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.
[JIRA] [hockeyapp] (JENKINS-23119) Should hockeyapp file upload originate from slave or master? Discussion.
Brenton B commented on JENKINS-23119 Should hockeyapp file upload originate from slave or master? Discussion. Why not option for both?? Default to have it go from Slave (since it's doing the building and if it builds, it should upload), but allow for override to go from server for case where firewall rules cause hurdles. 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] [github] (JENKINS-23641) Builds are failing due to GitHubCommitNotifier exception
Tony Ghita commented on JENKINS-23641 Builds are failing due to GitHubCommitNotifier exception I'm also having this issue. Was there a fix for 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] [core] (JENKINS-6153) allow description for slave labels
Daniel Beck assigned JENKINS-6153 to Daniel Beck allow description for slave labels Change By: Daniel Beck (22/Aug/14 10:32 PM) Assignee: DanielBeck 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Alex Earl commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 You can build it from source all you want, it just won't be supported at all. 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Steve Rowe commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 According to the Jenkins event calendar, the next LTS (which AFAICT will likely be = v1.577) is scheduled for release on October 15. 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
thetaphi commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 I can for now stay on Jenkins 1.576 (with an Apache mod_substitute rewrite on the reverse proxy for a bug in this version). If you have a branch for upgrades for the next LTS version, let us know. We can keep this issue open, because it has to be fixed in any case. 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] [email-ext] (JENKINS-24395) Fatal error with coming Jenkins ver. 1.577
Alex Earl commented on JENKINS-24395 Fatal error with coming Jenkins ver. 1.577 Nope, no branch for LTS updates right now. 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] [scm-sync-configuration] (JENKINS-22820) Changes are not commited when using a recent git client
rogerhu commented on JENKINS-22820 Changes are not commited when using a recent git client I had to bump all org.apache.maven.scm related packages to 1.9.1. https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/21 The fix works for me. 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] [core] (JENKINS-6153) allow description for slave labels
Daniel Beck started work on JENKINS-6153 allow description for slave labels Change By: Daniel Beck (22/Aug/14 11:26 PM) Status: Open InProgress 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.
