[JIRA] [xcode] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
SCM/JIRA link daemon commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace Code changed in jenkins User: Victor Barros Path: src/main/java/au/com/rayh/XCodeBuilder.java src/test/java/au/com/rayh/XCodeBuilderTest.java http://jenkins-ci.org/commit/xcode-plugin/8b0e0525b9583fbfd90cebe56882a0bd0b5abf5b Log: fix for issue JENKINS-12800 https://issues.jenkins-ci.org/browse/JENKINS-12800 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-12800) Can't add xcodebuild parameters including whitespace
SCM/JIRA link daemon commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace Code changed in jenkins User: Jerome Lacoste Path: pom.xml src/main/java/au/com/rayh/XCodeBuilder.java src/test/java/au/com/rayh/XCodeBuilderTest.java http://jenkins-ci.org/commit/xcode-plugin/d08553a852c2feb61ec016bb0940a3571b613a9d Log: Merge pull request #22 from heyzooi/master fix for issue JENKINS-12800 Compare: https://github.com/jenkinsci/xcode-plugin/compare/17322cab642c...d08553a852c2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-17729) Parsing issues with XCode plugin
lacostej commented on JENKINS-17729 Parsing issues with XCode plugin It looks like a reordering of output. Are you able to provide me the output of the command run on the command line ? Could you also try to see if the stdout and sterr can be differentiated ? Or just give me a xcode project with testcases that I could run. I don't have any. Maybe there's one open source somewhere. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-17335) Xcode Project Directory does not expand correctly
lacostej commented on JENKINS-17335 Xcode Project Directory does not expand correctly Could you try with 1.3.3 ? Variable expansion was improved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-17457) get a non-existing directory problem when making an IPA after building a workspace.
lacostej commented on JENKINS-17457 get a non-existing directory problem when making an IPA after building a workspace. Could you try with 1.3.3 ? Variable expansion was improved. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-17184) Allow setting a custom timeout when unlocking the keychain
lacostej commented on JENKINS-17184 Allow setting a custom timeout when unlocking the keychain This doesn't sound to hard to add. Would you mind trying ? https://developer.apple.com/library/mac/documentation/Darwin/Reference/ManPages/man1/security.1.html https://github.com/jenkinsci/xcode-plugin/blob/master/src/main/java/au/com/rayh/XCodeBuilder.java#L363 Try to support both -u -l and -t arguments This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-16771) Xcode plugin doesn't read the Source Trees setting from the IDE
lacostej commented on JENKINS-16771 Xcode plugin doesnt read the Source Trees setting from the IDE Can you describe a bit more your configuration and what happens when you try building with the plugin ? Any log from both your command line and our plugin to compare ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testlink] (JENKINS-17608) Test Link plugin, show the test results in the category notes
Jeanjean LaGuigne commented on JENKINS-17608 Test Link plugin, show the test results in the category notes Hi Bruno, how are you ^^ ? Could we try to include this little improvement in the next release? Are you free this weekend? Cheers! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15941) Xcode PlugIn can't properly build an IPA when the Info.plist File build setting contains a variable
lacostej commented on JENKINS-15941 Xcode PlugIn cant properly build an IPA when the Info.plist File build setting contains a variable Could it be because the variables were not expanded properly ? This was improved in 1.3.3 released this morning. Please try again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-17184) Allow setting a custom timeout when unlocking the keychain
SCM/JIRA link daemon commented on JENKINS-17184 Allow setting a custom timeout when unlocking the keychain Code changed in jenkins User: Jerome Lacoste Path: src/main/java/au/com/rayh/XCodeBuilder.java http://jenkins-ci.org/commit/xcode-plugin/5b2a452d965abfe3660092cda378f0dc2b835d41 Log: JENKINS-15939, JENKINS-17184 display keychain timeout information This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15939) Unlock Keychain option does not work for long build when keychain has a timeout
lacostej resolved JENKINS-15939 as Duplicate Unlock Keychain option does not work for long build when keychain has a timeout This duplicates JENKINS-17184 in which I indicated some tips for implementing it. Please help I added in 5b2a452d965abfe3660092cda378f0dc2b835d41 a debug of the current timeout as part of the build output. I will also document the current settings on the page. Change By: lacostej (16/May/13 7:23 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15939) Unlock Keychain option does not work for long build when keychain has a timeout
SCM/JIRA link daemon commented on JENKINS-15939 Unlock Keychain option does not work for long build when keychain has a timeout Code changed in jenkins User: Jerome Lacoste Path: src/main/java/au/com/rayh/XCodeBuilder.java http://jenkins-ci.org/commit/xcode-plugin/5b2a452d965abfe3660092cda378f0dc2b835d41 Log: JENKINS-15939, JENKINS-17184 display keychain timeout information This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [downstream-ext] (JENKINS-10435) Join project not triggered correctly when passing SCM info downstream via downstream-ext plugin
Thomas Fields commented on JENKINS-10435 Join project not triggered correctly when passing SCM info downstream via downstream-ext plugin I wouldn't be adverse to contributing but my time is also very limited. I'm sure someone with a firmer grasp on how this all works would be in a better position to fix it though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-14375) Xcode plugin: Can't use environment variable in Custom xcodebuild arguments field
lacostej resolved JENKINS-14375 as Fixed Xcode plugin: Cant use environment variable in Custom xcodebuild arguments field The release 1.3.3 contains proper variable expansion. I resolve the issue, please reopen if this is still a problem. Change By: lacostej (16/May/13 7:33 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/groups/opt_out.
[JIRA] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Andreas Scheucher created JENKINS-17974 SVN plugin ignores --depth parameters Issue Type: Bug Affects Versions: current Assignee: jbq Components: svncompat13 Created: 16/May/13 7:37 AM Description: As we have a huge SVN repository, a selective svn checkout is done to minimize the checkout and update times during the build. First set all subfolders to be excluded: svn co http://reposerver/repos/project/trunk source --depth immediates svn update --set-depth exclude source\Folder1 svn update --set-depth exclude source\Folder2 svn update --set-depth exclude source\Folder3 Then the needed subfolders are included again: svn update --set-depth infinity source\Folder2 The expected behavior is to update only the included folder on an "svn up". The SVN plugin does not allow to update without --depth attribute. Because of this it is not possible to update depending on the workspace settings (which are mixed: immediates and infinity) but only on the possible settings in the SVN plugin (which are: infinity, empty, files, immediates) Environment: windows 7, vm ware virtual machine, jenkins running as service. Project: Jenkins Labels: scm subversion Priority: Major Reporter: Andreas Scheucher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [matrix-reloaded] (JENKINS-17964) NPE if one of the upstream builds is not found (our case 9294)
Jens Brejner updated JENKINS-17964 NPE if one of the upstream builds is not found (our case 9294) Pseudo linking into our tracker Change By: Jens Brejner (16/May/13 7:37 AM) Summary: NPEifoneoftheupstreambuildsisnotfound (ourcase9294) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-14246) Keychain cannot be unlocked if no user session is created
lacostej resolved JENKINS-14246 as Not A Defect Keychain cannot be unlocked if no user session is created It is my understanding that the new jenkins installer contains this setting. I don't see this as a xcode issue One can also probably work around this by installing the keys in e.g. the system keychains. But this isn't standard. I've added a note to the WIKI. Closing this Change By: lacostej (16/May/13 7:39 AM) Status: Open Resolved Assignee: lacostej 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/groups/opt_out.
[JIRA] [xcode] (JENKINS-13555) XCode Plugin: Code signing issue after first restart (but project builds successfully when triggered through terminal)
lacostej resolved JENKINS-13555 as Fixed XCode Plugin: Code signing issue after first restart (but project builds successfully when triggered through terminal) Duplicate with JENKINS-14246 This was mostly a documentation issue I think. I added information on the wiki regarding the SessionCreate argument for the daemon, which is now default for mac installs. Change By: lacostej (16/May/13 7:41 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/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17971) bzr switch does not work for anonymous http checkouts
Timotheus Pokorra resolved JENKINS-17971 as Cannot Reproduce bzr switch does not work for anonymous http checkouts sorry, I was using an old version of bzr, 2.4.1. I tried now with version bzr 2.5.1, and it works fine! Change By: Timotheus Pokorra (16/May/13 7:44 AM) Status: Open Resolved Assignee: MontyTaylor TimotheusPokorra Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svncompat13] (JENKINS-17974) SVN plugin ignores --depth parameters
Andreas Scheucher commented on JENKINS-17974 SVN plugin ignores --depth parameters The problem could be solved with an an additional option repository depth: none This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [bazaar] (JENKINS-17971) bzr switch does not work for anonymous http checkouts
Alexandre Garnier closed JENKINS-17971 as Cannot Reproduce bzr switch does not work for anonymous http checkouts Change By: Alexandre Garnier (16/May/13 7:59 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/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
gitt commented on JENKINS-16845 NullPointer in getPreviousBuild I get similar error with 1.509.1: I had several jobs created in Jenkins 1.501. The problem was that "Test Result Trend" chart was often not shown and in log file there were NullPointer/getPreviousBuild() exceptions. Then I upgraded to 1.509.1, deleted all old builds and "Test Result Trend" charts were shown again. But only for some time. After several new builds they disappeared and this is what i see in Jenkins log again: May 15, 2013 2:19:19 PM org.kohsuke.stapler.compression.CompressionFilter reportException WARNING: Untrapped servlet exception javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) ... Caused by: java.lang.NullPointerException at hudson.model.Run.getFullDisplayName(Run.java:711) at hudson.model.Run.toString(Run.java:706) at java.lang.String.valueOf(Unknown Source) at java.lang.StringBuilder.append(Unknown Source) at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:218) at hudson.tasks.test.AbstractTestResultAction.getPreviousResult(AbstractTestResultAction.java:163) at hudson.tasks.test.AbstractTestResultAction.buildDataSet(AbstractTestResultAction.java:246) at hudson.tasks.test.AbstractTestResultAction.doGraphMap(AbstractTestResultAction.java:217) at hudson.tasks.test.TestResultProjectAction.doTrendMap(TestResultProjectAction.java:108) at sun.reflect.GeneratedMethodAccessor2212.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) ... Or sometimes: May 16, 2013 10:06:30 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: tr.previousResult!=null in /jenkins/view/Tests-Functional/job/FT_Web/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor815.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTNENode.value(ASTNENode.java:55) at org.apache.commons.jexl.parser.ASTExpression.value(ASTExpression.java:54) at org.apache.commons.jexl.parser.ASTExpressionExpression.value(ASTExpressionExpression.java:56) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) ... Caused by: java.lang.NullPointerException at hudson.model.Run.getFullDisplayName(Run.java:711) at
[JIRA] [zentimestamp] (JENKINS-17975) SCM polling stops to work if the previously used build node no longer exists
aldaris created JENKINS-17975 SCM polling stops to work if the previously used build node no longer exists Issue Type: Bug Assignee: Gregory Boissinot Components: zentimestamp Created: 16/May/13 8:41 AM Description: When a build job is changed to use a new build node, and also the previously used node is removed from the Jenkins setup, then SCM polling starts to fail with: ERROR: Failed to record SCM polling for hudson.model.FreeStyleProject@587918[jobName] java.lang.NullPointerException at hudson.plugins.zentimestamp.ZenTimestampEnvironmentContributor.buildEnvironmentFor(ZenTimestampEnvironmentContributor.java:37) at hudson.model.Run.getEnvironment(Run.java:2045) at hudson.model.AbstractBuild.getEnvironment(AbstractBuild.java:931) at hudson.scm.SubversionSCM.compareRemoteRevisionWith(SubversionSCM.java:1230) at hudson.scm.SCM._compareRemoteRevisionWith(SCM.java:356) at hudson.scm.SCM.poll(SCM.java:373) at hudson.model.AbstractProject._poll(AbstractProject.java:1521) at hudson.model.AbstractProject.poll(AbstractProject.java:1446) at hudson.triggers.SCMTrigger$Runner.runPolling(SCMTrigger.java:439) at hudson.triggers.SCMTrigger$Runner.run(SCMTrigger.java:468) at hudson.util.SequentialExecutionQueue$QueueEntry.run(SequentialExecutionQueue.java:118) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) This is because AbstractBuild#getBuiltOn may return null, but this case is not handled in hudson.plugins.zentimestamp.ZenTimestampEnvironmentContributor#buildEnvironmentFor. See http://javadoc.jenkins-ci.org/hudson/model/AbstractBuild.html#getBuiltOn() for reference. Project: Jenkins Priority: Major Reporter: aldaris This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [testflight] (JENKINS-17592) Testflight uploader plugin doesn't allow to upload multiple files
Mikolaj Leszczynski commented on JENKINS-17592 Testflight uploader plugin doesnt allow to upload multiple files I wasn't aware of that, thank you. I didn't notice that on the plugin webpage, but I see that it's there, sorry . It would be nice if this came with the Jenkins in-page help. It would still be great to be able to provide a wildcard or specify a list of files just for convenience. The android build process spits out multiple intermediate .apk files which you probably don't want to upload, so you have to use another build step to remove them just before running Testflight. Also you might simply not want to release all of the apks. Thanks for all the great work guys, your plugin makes life so much easier for our team! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17976) Jenkins executors dies
Jan Fagerström
created JENKINS-17976
Jenkins executors dies
Issue Type:
Bug
Affects Versions:
current
Assignee:
Marc Sanfacon
Components:
core, fingerprint
Created:
16/May/13 8:59 AM
Description:
The problem is that all executors on all nodes die with this stack trace:
java.lang.NullPointerException
at hudson.tasks.Fingerprinter$FingerprintAction.onLoad(Fingerprinter.java:346)
at hudson.model.Run.onLoad(Run.java:319)
at hudson.model.RunMap.retrieve(RunMap.java:226)
at hudson.model.RunMap.retrieve(RunMap.java:59)
at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:667)
at jenkins.model.lazy.AbstractLazyLoadRunMap.load(AbstractLazyLoadRunMap.java:629)
at jenkins.model.lazy.AbstractLazyLoadRunMap.search(AbstractLazyLoadRunMap.java:368)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:220)
at hudson.model.AbstractBuild.getPreviousBuild(AbstractBuild.java:103)
at hudson.model.Job.getLastBuildsOverThreshold(Job.java:887)
at hudson.model.Job.getEstimatedDuration(Job.java:894)
at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:320)
at hudson.model.queue.MappingWorksheet.init(MappingWorksheet.java:303)
at hudson.model.Queue.maintain(Queue.java:1035)
at hudson.model.Queue.pop(Queue.java:863)
at hudson.model.Executor.grabJob(Executor.java:285)
at hudson.model.Executor.run(Executor.java:206)
A simple restart of the executor is not working, restart of Jenkins do not help either. Instead the whole Tomcat server needs to be restarted.
In the FingerprintAction where the NPE originates you can see these lines:
345:public void onLoad() {
346:if (build.getParent() == null) {
347:logger.warning("JENKINS-16845: broken FingerprintAction record");
348:build = null;
349:return;
250:}
When looking in the Tomcat logs:
grep JENKINS-16845 /path/to/catalina.out
WARNING: JENKINS-16845: broken FingerprintAction record
WARNING: JENKINS-16845: broken FingerprintAction record
. . .
So a possible reason is that onLoad has been called twice.
I do not know if it has any relevance to this bug, but just before all executors died we had started a build of a particular job. The build could never start because there were no available executors. After Tomcat had been restarted we saw the job that had lost all Build History. The history was still there on the disc, but could not be seen on the job page. It is unclear if the history was gone before the restart. We had learned that a trick to get back the history is to rename the job and then rename again to the original name. After that we tried to build again and this time it worked.
Environment:
OS: Linux unknown, amd64/64 (2 cores)
Java: Java(TM) SE Runtime Environment, 1.7.0_03-b04
JVM: Java HotSpot(TM) 64-Bit Server VM, 22.1-b02, mixed mode
Server: Tomcat
Jenkins: 1.512
Project:
Jenkins
Priority:
Major
Reporter:
Jan Fagerström
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
[JIRA] [core] (JENKINS-17977) Reload configuration from disk no longer works after upgrade to Jenkins 1.512.
johmart created JENKINS-17977 Reload configuration from disk no longer works after upgrade to Jenkins 1.512. Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 16/May/13 9:27 AM Description: When I access the link "Reload Configuration from Disk" in the "Manage Jenkins" area. I get a popup asking for confirmation since the upgrade to Jenkins 1.512 (previous was 1.478). When I click ok, I get the following error message: HTTP Status 403 - No valid crumb was included in the request type Status report message No valid crumb was included in the request description Access to the specified resource (No valid crumb was included in the request) has been forbidden. JBoss Web/7.0.13.Final Environment: Ubuntu 12.04 LTS, OpenSuse 10.3 Project: Jenkins Labels: jenkins configuration Priority: Major Reporter: johmart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [configurationslicing] (JENKINS-17978) Jabber Notification support
Evgeny Goldin created JENKINS-17978 Jabber Notification support Issue Type: New Feature Assignee: mdonohue Components: configurationslicing Created: 16/May/13 9:49 AM Description: Being able to slice in "Jabber Notification" to jobs would be very nice. Project: Jenkins Priority: Major Reporter: Evgeny Goldin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
SCM/JIRA link daemon commented on JENKINS-13243 Do not replace slashes in URLs with backslashes on Windows Code changed in jenkins User: Marco Ambu Path: src/main/java/hudson/plugins/xshell/XShellBuilder.java http://jenkins-ci.org/commit/xshell-plugin/3ac09e1cf3ce8de0e0c9eedfd076998dc754c961 Log: Merge pull request #7 from achengs/master Don't replace slashes in git URLs. Fixes JENKINS-13243 Compare: https://github.com/jenkinsci/xshell-plugin/compare/3c8ade876689...3ac09e1cf3ce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xshell] (JENKINS-13243) Do not replace slashes in URLs with backslashes on Windows
SCM/JIRA link daemon commented on JENKINS-13243 Do not replace slashes in URLs with backslashes on Windows Code changed in jenkins User: Andrew Cheng Path: src/main/java/hudson/plugins/xshell/XShellBuilder.java http://jenkins-ci.org/commit/xshell-plugin/8b564d19c457e85c88763d270edc803772286c75 Log: add git to URL matcher for JENKINS-13243 otherwise git://github.com/user/repo.git becomes git:\github.com\user\repo.git see https://issues.jenkins-ci.org/browse/JENKINS-13243?focusedCommentId=178712page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-178712 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-15966) Build flow breaks when triggering next job
Marijn van der Zee commented on JENKINS-15966 Build flow breaks when triggering next job I had the same error, in my case it was a because the job that the build flow wanted to trigger had a pending build already. Removing the pending build (e.g. from the build history sidebar) resolved the error. It would be nice if the exception message was a bit more descriptive though. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
LuFrija commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Kenny, Bret, Did you do any modification to the pom files of the fork of jenkinsci-svnkit or to the svnPlugin? In fact I'm using the svnkit code patched by Kenny: https://github.com/theotherwhitemeat/svnkit-1 ...and the SVNPlugin 1.46: https://github.com/jenkinsci/subversion-plugin/tree/subversion-1.45 The first one was successfully built, but then I get tons of test errors while building the second one. Any idea? I know I could simply use the build of Kenny (btw, thx! ) but I wanted to try to build it on my own. Thanks for any help! p.s. Kenny, I had the very same problem mentioned by you here: http://jenkins.361315.n4.nabble.com/Compiling-SVNKit-for-subversion-plugin-td4663822.html ...and I ended up changing the exec task in the pom file of svnKit from this: exec command="./gradlew clean assemble" / ...to this: exec command="./gradlew clean build -x test -x signMaven"/ Did you do the same? I then copied the jar file located in the gradle/build folder into my local maven repo, I hope this was not an incredible stupid idea... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
LuFrija edited a comment on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Kenny, Bret, Did you do any modification to the pom files of the fork of jenkinsci-svnkit or to the svnPlugin? In fact I'm using the svnkit code patched by Kenny: https://github.com/theotherwhitemeat/svnkit-1 ...and the SVNPlugin 1.45: https://github.com/jenkinsci/subversion-plugin/tree/subversion-1.45 The first one was successfully built, but then I get tons of test errors while building the second one. Any idea? I know I could simply use the build of Kenny (btw, thx! ) but I wanted to try to build it on my own. Thanks for any help! p.s. Kenny, I had the very same problem mentioned by you here: http://jenkins.361315.n4.nabble.com/Compiling-SVNKit-for-subversion-plugin-td4663822.html ...and I ended up changing the exec task in the pom file of svnKit from this: exec command="./gradlew clean assemble" / ...to this: exec command="./gradlew clean build -x test -x signMaven"/ Did you do the same? I then copied the jar file located in the gradle/build folder into my local maven repo, I hope this was not an incredible stupid idea... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17979) checkout from/via Eclipse Projectsets (PSF)
cforce updated JENKINS-17979 checkout from/via Eclipse Projectsets (PSF) Change By: cforce (16/May/13 12:46 PM) Summary: checkou checkout from /via Eclipse Projectset Projectsets (PSF) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-17979) checkou from Eclipse Projectset (PSF)
cforce created JENKINS-17979 checkou from Eclipse Projectset (PSF) Issue Type: New Feature Assignee: Unassigned Components: subversion Created: 16/May/13 12:46 PM Description: Being able to configure the scm repositories and projects to poll and checkout via Eclipse Project set files. The adavanatge is less need to mainatin the jenkins job itself because there only the builds project repo has to get checked out to get acess to the scm config (psf file) This feature is already available for cvs but is missing for svn Project: Jenkins Priority: Major Reporter: cforce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svn-tag] (JENKINS-12934) Subversion Tag plugin tries to copy from invalid source path
Cook Gallaher commented on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Hi guys, same issue with path duplicating, did anybody solve it? Regards, Cook This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [svn-tag] (JENKINS-12934) Subversion Tag plugin tries to copy from invalid source path
Cook Gallaher commented on JENKINS-12934 Subversion Tag plugin tries to copy from invalid source path Hello, try to update Subversion Plug-in. After update to 1.45 version it works nice for us. Regards, Cook This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-15941) Xcode PlugIn can't properly build an IPA when the Info.plist File build setting contains a variable
Francis Labrie commented on JENKINS-15941 Xcode PlugIn cant properly build an IPA when the Info.plist File build setting contains a variable Will this new release appear in updates in Jenkins PlugIns Manager? I can't build and install it myself. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-collector] (JENKINS-17980) Error 404 when clikcing on Static Analysis Trend graph
Joshua Slominski created JENKINS-17980 Error 404 when clikcing on Static Analysis Trend graph Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: analysis-collector, analysis-core Created: 16/May/13 1:57 PM Description: When clicking on the Static Analysis trend graph, an error 404 is thrown. The web address that is linked to is: http://SERVER_NAME:PORT/job/JOB_NAME/SERVER_NAME/job/JOB_NAME/JOB_NUMBER/analysisResult/NORMAL if I edit the address to: http://SERVER_NAME:PORT/job/JOB_NAME/JOB_NUMBER/analysisResult/NORMAL/? I get the proper page Environment: Red Hat Linux Fix Versions: current Project: Jenkins Priority: Major Reporter: Joshua Slominski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Vasudeva Bhat commented on JENKINS-17872 build-pipeline-plugin seems to have lost its ability to show sub-projects We are seeing this problem since upgrading to Jenkins LTS 1.509 Was working ok with the previous LTS build, 1.480 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-16845) NullPointer in getPreviousBuild
Jesse Glick commented on JENKINS-16845 NullPointer in getPreviousBuild @gitt I am not convinced your exception is related to this 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/groups/opt_out.
[JIRA] [xcode] (JENKINS-15941) Xcode PlugIn can't properly build an IPA when the Info.plist File build setting contains a variable
lacostej commented on JENKINS-15941 Xcode PlugIn cant properly build an IPA when the Info.plist File build setting contains a variable The release will appear in the update manager within 24h I guess. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-flow] (JENKINS-17981) When ignoring failure in job run in parallel with others, jobs after parallel block will not run
Graham Saulnier
created JENKINS-17981
When ignoring failure in job run in parallel with others, jobs after parallel block will not run
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
build-flow
Created:
16/May/13 2:30 PM
Description:
I have something like this:
build(jobA)
parallel
(
{build(jobB)}
ignore(FAILURE) { build(jobC) }
{ build(jobD) }
)
build(jobE)
if jobC fails, jobA, jobB and jobD will run and succeed, however, jobE never gets run. The entire build reports failure but is unable to give a reason.
Project:
Jenkins
Priority:
Major
Reporter:
Graham Saulnier
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [build-pipeline] (JENKINS-17872) build-pipeline-plugin seems to have lost its ability to show sub-projects
Marco Miller commented on JENKINS-17872 build-pipeline-plugin seems to have lost its ability to show sub-projects I pushed a fix for this issue to that plugin's master (May 3-10), so it should show up in plugin's next release: https://github.com/jenkinsci/build-pipeline-plugin/commits/master This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [confluence-publisher] (JENKINS-17982) Option to publish without notifying watchers
Martin Wiklundh created JENKINS-17982 Option to publish without notifying watchers Issue Type: New Feature Affects Versions: current Assignee: Joe Hansche Components: confluence-publisher Created: 16/May/13 3:06 PM Description: If possible it would be good to have the option to publish without notifying the watchers of the page. Project: Jenkins Priority: Minor Reporter: Martin Wiklundh This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Brent Atkinson commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content I had similar issues, building on windows. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
Alex Earl resolved JENKINS-17969 as Cannot Reproduce Jelly Script not working Change By: Alex Earl (16/May/13 3:57 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17838) full build log not in content of email
Alex Earl resolved JENKINS-17838 as Cannot Reproduce full build log not in content of email Change By: Alex Earl (16/May/13 3:57 PM) Status: Open Resolved Resolution: CannotReproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Joseph Lawson commented on JENKINS-5853 Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key I too ran into this problema (JENKINS-17683) and submitted a pull request (https://github.com/jenkinsci/ec2-plugin/pull/45) which was accepted so this should be resolved at the next release. If you are feeling adventurous just get the plugin from github, compile and this should be working. -Joe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Joseph Lawson edited a comment on JENKINS-5853 Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key I too ran into this problema (JENKINS-17683) and submitted a pull request (https://github.com/jenkinsci/ec2-plugin/pull/45) which was accepted so this should be resolved at the next release. If you are feeling adventurous just get the plugin from github, compile and this should be working. Edit: Never mind I misread this. The patch I submitted allows you to upload the public key of any private key you have generated to EC2 and use that as the launch key. -Joe This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
A AA updated JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Change By: A AA (16/May/13 4:35 PM) Attachment: no_ssh_config.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/groups/opt_out.
[JIRA] [ec2] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Joseph Lawson commented on JENKINS-5853 Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key Seems to me the way to do this is to take the private key given and then upon startup feed it via the user-data to the authorized_keys file of the ec2-user. ie: #! echo ssh-rsa AAAB3N...QcGskx keyname ~ec2-user/.ssh/authorized_keys echo ssh-rsa BBRdt5...LguTtp another-key ~ec2-user/.ssh/authorized_keys From: http://stackoverflow.com/a/13202445 Regardless, the plugin still needs an keypair to launch the instance so I feel like this is a won't implement feature and your workaround is as described. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-5853) Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key
Joseph Lawson edited a comment on JENKINS-5853 Allow Amazon EC2 Plugin to use ssh keys other than the EC2 private key Seems to me the way to do this is to take the private key given and then upon startup feed it via the user-data to the authorized_keys file of the ec2-user. ie: #! echo ssh-rsa AAAB3N...QcGskx keyname ~ec2-user/.ssh/authorized_keys echo ssh-rsa BBRdt5...LguTtp another-key ~ec2-user/.ssh/authorized_keys From: http://stackoverflow.com/a/13202445 Regardless, the plugin still needs an keypair to launch the instance so I feel like this is a won't implement feature and your workaround is as described. Edit (again . So yes EC2 doesn't need a keypair to launch an instance, just your access keys. Thinking about it even more, I'm going to change my opinion here. The plugin could instead, if it doesn't find the keypair match on EC2 to automatically submit the public key to the authorized_keys for the user specified. That could implement this feature. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-cifs] (JENKINS-17885) Publish over SSH lost main configuration data after jenkins server reboot
wearbif updated JENKINS-17885 Publish over SSH lost main configuration data after jenkins server reboot Change By: wearbif (16/May/13 4:42 PM) Description: Afterjenkinsserverreboot,configurationislostonmainoptionsmenu.Buildjobssavepublish-over-sshconfiguaionscorrectly. Ascreenshotshowsaconfiguratingwindowafterreboot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15389) Fingerprinting private key for discovery is flawed
Joseph Lawson commented on JENKINS-15389 Fingerprinting private key for discovery is flawed This was fixed with: https://issues.jenkins-ci.org/browse/JENKINS-17683 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15389) Fingerprinting private key for discovery is flawed
Joseph Lawson edited a comment on JENKINS-15389 Fingerprinting private key for discovery is flawed This was fixed with: https://issues.jenkins-ci.org/browse/JENKINS-17683 the plugin now checks both the private keyfingerprint (off of a sha checksum) and the public key fingerprint (off of an md5 checksum) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-15389) Fingerprinting private key for discovery is flawed
Francis Upton resolved JENKINS-15389 as Duplicate Fingerprinting private key for discovery is flawed https://issues.jenkins-ci.org/browse/JENKINS-17683 Change By: Francis Upton (16/May/13 4:54 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-17816) SDK lookup from PATH looks for adb in {sdk}/tools folder (it has been moved).
Mike Dougherty
commented on JENKINS-17816
SDK lookup from PATH looks for adb in {sdk}/tools folder (it has been moved).
I'm also experiencing this after our Android SDK was updated. The component is now unable to detect the installed SDK, causing it to attempt automatic install, which fails as it is unable to accept the license correctly.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
SCM/JIRA link daemon commented on JENKINS-17086 Use IAM Role when creating instance Code changed in jenkins User: ww-mgr Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java http://jenkins-ci.org/commit/ec2-plugin/7d8a169e64c7d7c744518ba1297774e2903b7804 Log: JENKINS-17086 Undo some whitespace changes This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
SCM/JIRA link daemon commented on JENKINS-17086 Use IAM Role when creating instance Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-iamInstanceProfile.html src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java src/test/java/hudson/plugins/ec2/TemplateLabelsTest.java http://jenkins-ci.org/commit/ec2-plugin/4102f1cf7898dae96f3785d3a196276e5627ffae Log: Merge pull request #52 from ww-mgr/ec2-iamrole JENKINS-17086 Add iamRole option to slave configuration Compare: https://github.com/jenkinsci/ec2-plugin/compare/3ee74a45270e...4102f1cf7898 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
SCM/JIRA link daemon commented on JENKINS-17086 Use IAM Role when creating instance Code changed in jenkins User: ww-mgr Path: src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/main/resources/hudson/plugins/ec2/SlaveTemplate/config.jelly src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-iamInstanceProfile.html src/main/resources/hudson/plugins/ec2/SlaveTemplate/help-iamRole.html src/test/java/hudson/plugins/ec2/SlaveTemplateTest.java http://jenkins-ci.org/commit/ec2-plugin/b5f2eb7beec88bb7d008ffeb0b1768404aba3b8f Log: JENKINS-17086 Add iamInstanceProfile option to slave configuration This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17086) Use IAM Role when creating instance
Francis Upton resolved JENKINS-17086 as Fixed Use IAM Role when creating instance Change By: Francis Upton (16/May/13 5:37 PM) 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/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
David Brossard closed JENKINS-17969 as Cannot Reproduce Jelly Script not working Change By: David Brossard (16/May/13 5:59 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/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17902) NullPointerException and pull request doesn't exist when triggering build via GitHub hooks
Ben Dolman commented on JENKINS-17902 NullPointerException and pull request doesnt exist when triggering build via GitHub hooks I have a similar problem, but a different error it seems. Whenever I add a new commit to an existing PR, I get this: May 16, 2013 11:58:20 AM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload INFO: Received POST for https://github.com/user/repo May 16, 2013 11:58:22 AM org.jenkinsci.plugins.ghprb.GhprbProjectAction doIndex INFO: Got payload event: pull_request May 16, 2013 11:58:22 AM org.jenkinsci.plugins.ghprb.GhprbPullRequest check INFO: Pull request builder: pr #30 was updated on user/repo at 5/16/13 11:51 AM May 16, 2013 11:58:22 AM winstone.Logger logInternal SEVERE: Error while serving http://jenkins.mycompany.com/job/job-name%20(GitHub)/ghprbhook/ java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:156) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NullPointerException at org.kohsuke.github.GHIssue.getApiRoute(GHIssue.java:204) at org.kohsuke.github.GHIssue.access$000(GHIssue.java:41) at
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
David Brossard commented on JENKINS-17969 Jelly Script not working Dang it. It was curly quotes around "html". Sorry for wasting your time Alex This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [email-ext] (JENKINS-17969) Jelly Script not working
Alex Earl commented on JENKINS-17969 Jelly Script not working No time wasted. I'm glad it was a simple fix for you. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ghprb] (JENKINS-17902) NullPointerException and pull request doesn't exist when triggering build via GitHub hooks
Ben Dolman edited a comment on JENKINS-17902 NullPointerException and pull request doesnt exist when triggering build via GitHub hooks I have a similar problem, but a different error it seems. Whenever I add a new commit to an existing PR, I get the following error. If I close the PR then immediately reopen it, then it does rebuild it. May 16, 2013 11:58:20 AM com.cloudbees.jenkins.GitHubWebHook processGitHubPayload INFO: Received POST for https://github.com/user/repo May 16, 2013 11:58:22 AM org.jenkinsci.plugins.ghprb.GhprbProjectAction doIndex INFO: Got payload event: pull_request May 16, 2013 11:58:22 AM org.jenkinsci.plugins.ghprb.GhprbPullRequest check INFO: Pull request builder: pr #30 was updated on user/repo at 5/16/13 11:51 AM May 16, 2013 11:58:22 AM winstone.Logger logInternal SEVERE: Error while serving http://jenkins.mycompany.com/job/job-name%20(GitHub)/ghprbhook/ java.lang.reflect.InvocationTargetException at sun.reflect.GeneratedMethodAccessor198.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$2.dispatch(MetaClass.java:156) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680) Caused by: java.lang.NullPointerException at
[JIRA] [subversion] (JENKINS-14551) an update which contains added files merged from a branch results in those files having doubled content
Kenny Ayers commented on JENKINS-14551 an update which contains added files merged from a branch results in those files having doubled content Hey LuFrija, If my memory is correct, I had to do the same thing - modify the build command for SVNKit, then copy the resultant jar file into my local maven repo, then build subversion-plugin against that. This seems like a hacky workflow, but it's the best I could stitch together given there are no instructions on how to build this properly, and the mailing list didn't respond to my question on how to build the correct way. Are you good to go now? -Kenny This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [android-emulator] (JENKINS-17816) SDK lookup from PATH looks for adb in {sdk}/tools folder (it has been moved).
Mike Dougherty
edited a comment on JENKINS-17816
SDK lookup from PATH looks for adb in {sdk}/tools folder (it has been moved).
I'm also experiencing this after our Android SDK was updated. The component is now unable to detect the installed SDK, causing it to attempt automatic install, which fails as it is unable to accept the license correctly (and even if it succeeded, I assume the tools would not be detected correctly).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-collector] (JENKINS-17980) Error 404 when clikcing on Static Analysis Trend graph
Ulli Hafner commented on JENKINS-17980 Error 404 when clikcing on Static Analysis Trend graph Can you please be more specific? Which trend graph? Which plug-in? Which plug-in version? Which part of the trend graph did you click? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [analysis-collector] (JENKINS-17980) Error 404 when clikcing on Static Analysis Trend graph
Joshua Slominski commented on JENKINS-17980 Error 404 when clikcing on Static Analysis Trend graph I am using the Priority distribution of all warnings graph. Its collecting data from findbugs and PMD. I am using 1.49 of Static Analysis Utilities, and 1.35 static Analysis Collector This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ivytrigger] (JENKINS-17831) Update to latest xTrigger
Gregory Boissinot commented on JENKINS-17831 Update to latest xTrigger You can try version 0.27. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [zentimestamp] (JENKINS-17975) SCM polling stops to work if the previously used build node no longer exists
SCM/JIRA link daemon commented on JENKINS-17975 SCM polling stops to work if the previously used build node no longer exists Code changed in jenkins User: Gregory Boissinot Path: src/main/java/hudson/plugins/zentimestamp/ZenTimestampEnvironmentContributor.java http://jenkins-ci.org/commit/zentimestamp-plugin/6568c274b3758e8fea581602eb7b363ffd0d61ed Log: Fix JENKINS-17975 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [collabnet] (JENKINS-17152) Large file upload fails using collabnet plugin
SCM/JIRA link daemon commented on JENKINS-17152 Large file upload fails using collabnet plugin Code changed in jenkins User: sheta Path: src/main/java/com/collabnet/ce/webservices/CollabNetApp.java http://jenkins-ci.org/commit/collabnet-plugin/8b70a7a107dfdd1c1c131a8904d4ff2960bd0e9e Log: JENKINS-17152Large file upload fails with timeout Making use of TF soap api call to upload large file in chunks If file is bigger than 124MB then dividing file into chunks of 0.74MB each and uploading at a time This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [collabnet] (JENKINS-17152) Large file upload fails using collabnet plugin
SCM/JIRA link daemon commented on JENKINS-17152 Large file upload fails using collabnet plugin Code changed in jenkins User: jmcnally Path: src/main/java/com/collabnet/ce/webservices/CollabNetApp.java http://jenkins-ci.org/commit/collabnet-plugin/3b8b2a846dd5b637aed55c42120d210c8d07d10e Log: Merge pull request #3 from dharmsheta/master JENKINS-17152 Large file upload fails using collabnet plugin Compare: https://github.com/jenkinsci/collabnet-plugin/compare/27bddec19e5e...3b8b2a846dd5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [zentimestamp] (JENKINS-17975) SCM polling stops to work if the previously used build node no longer exists
Gregory Boissinot resolved JENKINS-17975 as Fixed SCM polling stops to work if the previously used build node no longer exists Change By: Gregory Boissinot (16/May/13 8:36 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-17983) Cannot create a custom logger matching any namespace
Jesse Glick created JENKINS-17983 Cannot create a custom logger matching any namespace Issue Type: Bug Assignee: Jesse Glick Components: core Created: 16/May/13 8:40 PM Description: ?xml version='1.0' encoding='UTF-8'? log nameexplicit fine/name targets target nameorg/name level500/level /target target namecom/name level500/level /target target namenet/name level500/level /target target namehudson/name level500/level /target target namejenkins/name level500/level /target /targets /log works to capture all log messages at FINE, so long as you get all the top-level domains, but is clumsy. ?xml version='1.0' encoding='UTF-8'? log nameall fine/name targets target name/name level500/level /target /targets /log ought to work but currently does not. Project: Jenkins Labels: logging Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17984) Changing Idle termination time on a cloud instance killed the running job
David Walend created JENKINS-17984 Changing Idle termination time on a cloud instance killed the running job Issue Type: Bug Affects Versions: current Assignee: Francis Upton Components: ec2 Created: 16/May/13 9:02 PM Description: If I change "Idle termination time" on a running ec2 instance slave then Jenkins stops the job. It'd be much less bug-like if the job just kept running. (I set the timeout to "0" because the run will take days and I want to be able to log into the slave machine if something goes wrong to see what we can salvage.) Environment: Jenkins is running on a micro, using cc28xlarges as slaves. Ubuntu 12.04 OS, Tomcat 7. Project: Jenkins Labels: plugin slave job Priority: Major Reporter: David Walend This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17983) Cannot create a custom logger matching any namespace
SCM/JIRA link daemon resolved JENKINS-17983 as Fixed Cannot create a custom logger matching any namespace Change By: SCM/JIRA link daemon (16/May/13 9:24 PM) 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/groups/opt_out.
[JIRA] [core] (JENKINS-17983) Cannot create a custom logger matching any namespace
SCM/JIRA link daemon commented on JENKINS-17983 Cannot create a custom logger matching any namespace Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/java/hudson/logging/LogRecorder.java core/src/test/java/hudson/logging/LogRecorderTest.java http://jenkins-ci.org/commit/jenkins/84d1abdcd42ab64198a29a40bdec268eac384b22 Log: FIXED JENKINS-17983 Empty LogRecorder.Target.name was not working. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17985) REST API summary should enumerate known web methods
Jesse Glick created JENKINS-17985 REST API summary should enumerate known web methods Issue Type: Improvement Assignee: Jesse Glick Components: core Created: 16/May/13 9:34 PM Description: Any @WebMethod or method with a matching doSomething signature should be listed along with any @QueryParameter arguments. Project: Jenkins Labels: rest Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [cloudtest] (JENKINS-17986) CloudTest plug-in does not work on Windows
msolnit created JENKINS-17986 CloudTest plug-in does not work on Windows Issue Type: Bug Affects Versions: current Assignee: msolnit Components: cloudtest Created: 16/May/13 9:40 PM Description: See http://cloudlink.soasta.com/t5/forums/replypage/board-id/FW-TestExecutionAndManagement/message-id/63. The plug-in tries to launch "scommand/bin/scommand", but needs to use the ".bat" extension on Windows. Project: Jenkins Priority: Major Reporter: msolnit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [publish-over-ftp] (JENKINS-17987) Publish Over FTP: path with spaces transfers 0 files.
javydreamercsw created JENKINS-17987 Publish Over FTP: path with spaces transfers 0 files. Issue Type: Bug Affects Versions: current Assignee: bap Components: publish-over-ftp Created: 16/May/13 9:58 PM Description: I've used this plugin without issues before. I believe it is because the path to the files now have an space and is ran on a Linux machine. That's the only difference I can see. Project: Jenkins Priority: Major Reporter: javydreamercsw This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17988) Broken image links when using CloudBees Folders plugin
Jesse Glick created JENKINS-17988 Broken image links when using CloudBees Folders plugin Issue Type: Bug Assignee: Jesse Glick Components: dashboard-view Created: 16/May/13 10:23 PM Description: If you add a Jobs Grid portlet to a dashboard view and include some folders, the primary icon is broken. The reason is that the view was using job.buildStatusUrl, which is not defined for a folder. It could be, but anyway you were unnecessarily constructing icon URLs, when StatusIcon (and BuildHealth) already provide approved methods for getting the full image URL. Fixing this also gets support for custom folder icons for free. Project: Jenkins Labels: folders Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [dashboard-view] (JENKINS-17988) Broken image links when using CloudBees Folders plugin
Jesse Glick updated JENKINS-17988 Broken image links when using CloudBees Folders plugin Change By: Jesse Glick (16/May/13 10:26 PM) URL: https://github.com/jenkinsci/dashboard-view-plugin/pull/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/groups/opt_out.
[JIRA] [mailer] (JENKINS-16332) Leading and trailing underscores are added to commiters email address, unable to send build notification
wee thomas commented on JENKINS-16332 Leading and trailing underscores are added to commiters email address, unable to send build notification I should also indicate that my manual access of Jenkins is anonymous. While I've created accounts for all users in SCM, I don't actually login to Jenkins when making changes, manually triggering builds, etc. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-17956) Jenkins always replace the last letter of job with dot in the node view
Ken Adams commented on JENKINS-17956 Jenkins always replace the last letter of job with dot in the node view Any ideas ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [collabnet] (JENKINS-17152) Large file upload fails using collabnet plugin
John McNally resolved JENKINS-17152 as Fixed Large file upload fails using collabnet plugin Pull request closed and released as version 1.1.8 Change By: John McNally (17/May/13 3:15 AM) Status: InProgress Resolved Fix Version/s: current 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/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-17907) Build Failed due to ERROR: Asynchronous execution failure
anil kumar commented on JENKINS-17907 Build Failed due to ERROR: Asynchronous execution failure Now it's working fine. i have cleanup the maven repo and run the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jenkins-tracker] (JENKINS-17907) Build Failed due to ERROR: Asynchronous execution failure
anil kumar closed JENKINS-17907 as Fixed Build Failed due to ERROR: Asynchronous execution failure Change By: anil kumar (17/May/13 4:33 AM) 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/groups/opt_out.
[JIRA] [git] (JENKINS-17989) Git Plugin should expose a Git repository URL as an environment variable
Roman Revyakin created JENKINS-17989 Git Plugin should expose a Git repository URL as an environment variable Issue Type: Bug Assignee: Nicolas De Loof Components: git Created: 17/May/13 4:48 AM Description: It would be handy to have the Git Plugin expose the Git URL as an environment variable for processing by shell scripts, not only the Git branch. Otherwise we have to use Metadata plugin and basically duplicate the information in it for that purposes. Project: Jenkins Priority: Major Reporter: Roman Revyakin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Jenkins - Changin the URL issue
HI, I am using the Jenkins ver. 1.509.1. When i try to change the url, it gets success. But it is working for both old url and the new url. In the new url , when i try to login with admin credentials, it shows, *Oops! This link appears to be broken.* But the same credential working in the old jenkins url. Let me know what changes needs to be done to resolve the login issue. Thanks in advance. Regards, Karthik -- View this message in context: http://jenkins.361315.n4.nabble.com/Jenkins-Changin-the-URL-issue-tp4666484.html Sent from the Jenkins issues mailing list archive at Nabble.com. -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [xcode] (JENKINS-12151) Control the signing certificate for both the build and the packaging step
lacostej resolved JENKINS-12151 as Fixed Control the signing certificate for both the build and the packaging step I believe this was fixed by the aforementioned commit. 1.3.3 was released yesterday and should contain the fix. Change By: lacostej (17/May/13 5:51 AM) Status: Open 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/groups/opt_out.
