[JIRA] [artifactdeployer] (JENKINS-17436) Artifacts are deployed locally on slaves
Jon Sten created JENKINS-17436 Artifacts are deployed locally on slaves Issue Type: Bug Assignee: Gregory Boissinot Components: artifactdeployer Created: 02/Apr/13 7:08 AM Description: In our system we have one master and one performance slave. The master server run most jobs The slave run all time critical jobs that require a dedicated system. Once a build is done, artifacts is copied to a storage disk on the master server once a build is done. This is done to reduce the size of the Jenkins installation on the primary disk. The Artifactdeployer plugin does a great job, and we get the expected behaviour from all the builds that are executed on the master server. However we get an unexpected behaviour for builds that are executed on the slave server. The artifacts are deployed relative the slave's system. So if we specify 'D:/artifacts/', then artifacts are copied to the slave's D: disk and not the D: disk on the master. We think this is incorrect behaviour since it is now always known on what slave a build will be executed and best practice would be to always deploy artifacts from the masters perspective. Environment: Master: Jenkins @1.506 Artifactdeployer @ 0.26 Windows 7 Slave: Windows 7 Project: Jenkins Priority: Major Reporter: Jon Sten 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-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/test/java/hudson/plugins/promoted_builds/ConfigurationRoundtripTest.java src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/builds/2012-10-08_10-29-01/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/builds/2012-10-08_10-30-11/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/config.xml http://jenkins-ci.org/commit/promoted-builds-plugin/145a38922ef87bb0bea5edb372d7e11e07bdb6eb Log: FIXED JENKINS-17341 NPE after JENKINS-3265 fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
SCM/JIRA link daemon commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/test/java/hudson/plugins/promoted_builds/ConfigurationRoundtripTest.java src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/builds/2012-10-08_10-29-01/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/builds/2012-10-08_10-30-11/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/config.xml http://jenkins-ci.org/commit/promoted-builds-plugin/145a38922ef87bb0bea5edb372d7e11e07bdb6eb Log: FIXED JENKINS-17341 NPE after JENKINS-3265 fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-3265) Reload Configuration from Disk (or POSTing config.xml) loses info on running builds
SCM/JIRA link daemon commented on JENKINS-3265 Reload Configuration from Disk (or POSTing config.xml) loses info on running builds Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/test/java/hudson/plugins/promoted_builds/ConfigurationRoundtripTest.java src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/builds/2012-10-08_10-29-01/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/builds/2012-10-08_10-30-11/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/config.xml http://jenkins-ci.org/commit/promoted-builds-plugin/8147deb58e583ba696cd7feb451b1afabcb15a3d Log: Merge pull request #24 from jglick/NPE-JENKINS-17341 FIXED JENKINS-17341 NPE after JENKINS-3265 fix. Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/8f07c80a678d...8147deb58e58 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] [promoted-builds] (JENKINS-17341) Promoted builds throw NullPointerException after upgrade to 1.507
SCM/JIRA link daemon commented on JENKINS-17341 Promoted builds throw NullPointerException after upgrade to 1.507 Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java src/test/java/hudson/plugins/promoted_builds/ConfigurationRoundtripTest.java src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/builds/2012-10-08_10-29-01/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/config.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/builds/2012-10-08_10-30-11/build.xml src/test/resources/hudson/plugins/promoted_builds/ConfigurationRoundtripTest/testLoad/jobs/j/promotions/OK/config.xml http://jenkins-ci.org/commit/promoted-builds-plugin/8147deb58e583ba696cd7feb451b1afabcb15a3d Log: Merge pull request #24 from jglick/NPE-JENKINS-17341 FIXED JENKINS-17341 NPE after JENKINS-3265 fix. Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/8f07c80a678d...8147deb58e58 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-15156) Builds disappear from build history after completion
SCM/JIRA link daemon commented on JENKINS-15156 Builds disappear from build history after completion Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/promoted_builds/JobPropertyImpl.java http://jenkins-ci.org/commit/promoted-builds-plugin/add555747e7d94e27e019db47523e74c0a94c1b0 Log: JENKINS-15156 PromotionProcessTest failed with parent set to 1.507 because in lazy-loading versions of Jenkins the build list for a project must be explicitly created. 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] [sauce-ondemand] (JENKINS-17303) Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin
SCM/JIRA link daemon commented on JENKINS-17303 Null Pointer Exception for hasSauceOnDemandResults in jobs that arent using that plugin Code changed in jenkins User: Ross Rowe Path: src/main/java/hudson/plugins/sauce_ondemand/SauceOnDemandProjectAction.java http://jenkins-ci.org/commit/sauce-ondemand-plugin/f0959fa0fc637ca90b363de0af4215cd9ddf5cbc Log: JENKINS-17303 Resolve NPE when navigating to non-Sauce projects 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-13546) buildWithParameters: return a JSON string when client request it through content-type header
Bertrand Roussel commented on JENKINS-13546 buildWithParameters: return a JSON string when client request it through content-type header @Sune: It seems the "queueItem" should contain informations about the scheduled item, could you please provide more details about when this is null ? Is that random (for a same type of build, even if the build has been scheduled, sometimes the queueItem is null, sometimes it isn't), or is that more for some type of 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] [android-emulator] (JENKINS-17435) FATAL: channel is already closed on Android Emulator launch
Christopher Orr commented on JENKINS-17435 FATAL: channel is already closed on Android Emulator launch Looking at the bottom of the stack trace, it looks like Jenkins was shut down during the build. At the very bottom, you see Winstone shutting down, which shuts down the slaves, which interrupted the build. Does that sound correct? Or are you seeing this behaviour regularly? 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] [cli] (JENKINS-11870) Could not select Node parameter if running through CLI
domi resolved JENKINS-11870 as Cannot Reproduce Could not select Node parameter if running through CLI closing b'cause of missing feedback Change By: domi (02/Apr/13 8:59 AM) 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
kutzi assigned JENKINS-7970 to kutzi If all JUnit tests are skipped, the build fails Change By: kutzi (02/Apr/13 9:18 AM) Assignee: kutzi 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] [plugin] (JENKINS-17298) github-sqs-plugin, when desired, should access SQS with minimum amount of privileges
Aaron Walker started work on JENKINS-17298 github-sqs-plugin, when desired, should access SQS with minimum amount of privileges Change By: Aaron Walker (02/Apr/13 9:51 AM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-13546) buildWithParameters: return a JSON string when client request it through content-type header
Sune Keller commented on JENKINS-13546 buildWithParameters: return a JSON string when client request it through content-type header @Bertrand: It is random, but notably so in the context of a job allowing concurrent builds, and when multiple builds are scheduled within a short amount of time. In my case I have a job A which, when built, uses the Remote API to start builds of job B. The build of job A, let's name it A-1, wants to print links in its console output to the B builds B-1, B-..., B-N it has scheduled. 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] [any-buildstep] (JENKINS-17437) Add buil/post-build step doesn't show selected component after drop-down selection
Peter Miklosko created JENKINS-17437 Add buil/post-build step doesnt show selected component after drop-down selection Issue Type: Bug Assignee: bap Components: any-buildstep Created: 02/Apr/13 10:16 AM Description: When adding new job or managing configuration of existing job, on Add build or post-build step drop-down will appear. However selected option doesn't make chosen component visible. This appear to be issue only on Chrome browser, does work fine under Safari and Firefox Environment: Mac OS 10.8.3, Chrome 26.0.1410.43 Project: Jenkins Priority: Minor Reporter: Peter Miklosko 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] [artifactory] (JENKINS-17407) IllegalArgumentException: promotion when trying to configure chain of downstream promotions
Hannes Kogler updated JENKINS-17407 IllegalArgumentException: promotion when trying to configure chain of downstream promotions Change By: Hannes Kogler (02/Apr/13 10:48 AM) Environment: Jenkins1.506/PromotedBuildsPlugin2.9/ParameterizedTriggerplugin2.17/XTriggerPlug-in0.53/insteadofusingTriggerparameterizedbuildsonotherprojectsIuseTrigger/callbuildsonotherprojects ArtifactoryJenkinsPlugin2.1.4 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] [artifactory] (JENKINS-17407) IllegalArgumentException: promotion when trying to configure chain of downstream promotions
Hannes Kogler updated JENKINS-17407 IllegalArgumentException: promotion when trying to configure chain of downstream promotions Change By: Hannes Kogler (02/Apr/13 10:47 AM) Component/s: artifactory 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] [artifactory] (JENKINS-17407) IllegalArgumentException: promotion when trying to configure chain of downstream promotions
Hannes Kogler commented on JENKINS-17407 IllegalArgumentException: promotion when trying to configure chain of downstream promotions Hi Peter! Thx for the fast support! yes we use the Artifactory plugin and indeed thats the cause for the problem, as my tests have shown now. everytime when I use the Artifactory plugin for Jenkins.. eg. setting the option Resolve artifacts from Artifactory (at the Build Environment section) or Deploy artifacts to Artifactorys (as a Post-build Action) the third job in my configured "promotion chain" fails due to the upper exception. Obviously the Artifactory plugin (and its parameter handling?) disturbs the promoted builds plugin or the way it reads/sends parameters from/to other jobs?! 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] [tap] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Alex Newnham commented on JENKINS-17215 TAP plugin can prevent Jenkins startup Hi Bruno - sorry for the delay getting back to you. Can you advise paths to the fields you'd like me to delete from build.xml? Is there a case perhaps for the TAP plugin to perform some sanity checking before build.xml is parsed? I manually removed a Jenkins plan that was listing old 1.8 Plugin results but our problem remains. Currently, whenever Jenkins is restarted we lose our history of previous builds and we see the attached stack trace (stack3.txt). 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] [tap] (JENKINS-17215) TAP plugin can prevent Jenkins startup
Alex Newnham updated JENKINS-17215 TAP plugin can prevent Jenkins startup Change By: Alex Newnham (02/Apr/13 10:56 AM) Attachment: stack3.txt 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-13546) buildWithParameters: return a JSON string when client request it through content-type header
Bertrand Roussel edited a comment on JENKINS-13546 buildWithParameters: return a JSON string when client request it through content-type header @Sune: I see what you mean, I've made few experiments and now I have a better idea of what the "queueItem" actually returns. As for the randomness, as soon as the queued item is being processed, it pops out of the queue, so (maybe) if the process as started before the project gets serialized to be served as a JSON Object, then the queue Item is null. It might not be the exact scenario, but in any case the "queueItem" is indeed not reliable, and the queued item object (WaitingItem) returned when scheduling does not offer much support either (enclosed infos, such as timestamp, etc ... are not kept when creating a build object). I might be wrong, but it seems it would be hard to return informations such as "Ok, I scheduled this task, number is 33 and you will find the build at http://my-jenkins/job/MyJob/33/". This is what I wanted at first but it seems it would be difficult due to the process, which appears to be: Request Processing: Let's queue that WaitingItem # This is where the request result is built Job Processing: Let's take that WaitingItem and process it # This is where a "Build" is created Maybe it would be ok to attribute a GUID to the queued item, and keep that GUID in the build item. At some point it could provide an 'Jenkins instance'-wide id for a build item, which seems more reliable than a Job Name + Build Number relation. I will try to provide a proof of concept by the end of the day. 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-17369) SVNKit 1.6.7 has authentication bugs
Pim Do commented on JENKINS-17369 SVNKit 1.6.7 has authentication bugs Yes please, any idea when this change will become available to Jenkins users? In the meanwhile I downgraded to 1.39 and am still unable to let jenkins checkout a project. After removing the $HOME/.subversion cache and the entries in the hudson configuration file and restarting tomcat. When I enter the credentials through the job configuration page in jenkins it still fails without proper logging information to identify the problem. So, I'm still stuck and management is already breathing down my neck. Please advise!!! 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
kutzi commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Agree, it's absolutely reasonable to expect the build to only fail if there are really no test results - i.e. also no skipped tests. 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
SCM/JIRA link daemon resolved JENKINS-7970 as Fixed If all JUnit tests are skipped, the build fails Change By: SCM/JIRA link daemon (02/Apr/13 12:20 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
SCM/JIRA link daemon commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Code changed in jenkins User: Christoph Kutzinski Path: changelog.html core/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java core/src/main/java/hudson/tasks/junit/TestResult.java http://jenkins-ci.org/commit/jenkins/9bc7e21dc0bd679e7b6506f264079630493237d4 Log: FIXED JENKINS-7970 JUnit result archiver should only fail builds if there are really no results - i.e. also no skipped tests. 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-13323) Renaming a node does not update associated projects
evernat commented on JENKINS-13323 Renaming a node does not update associated projects Is this issue a duplicate of JENKINS-4232 ? 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] [m2release] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
SCM/JIRA link daemon commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 Code changed in jenkins User: glandais Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java http://jenkins-ci.org/commit/m2release-plugin/3ac6000a844d0a1247024306b82cd123b0328c34 Log: Update M2ReleaseAction.java JENKINS-13465 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] [m2release] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
SCM/JIRA link daemon commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 Code changed in jenkins User: jtnord Path: src/main/java/org/jvnet/hudson/plugins/m2release/M2ReleaseAction.java http://jenkins-ci.org/commit/m2release-plugin/2e22caafe9cb4c52e98043ab913aa902d09a2ec7 Log: Merge pull request #9 from glandais/master Proposed fix for JENKINS-13465 Compare: https://github.com/jenkinsci/m2release-plugin/compare/3f825e999357...2e22caafe9cb 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] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
dogfood commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Integrated in jenkins_main_trunk #2427 FIXED JENKINS-7970 JUnit result archiver should only fail builds if there are really no results - i.e. also no skipped tests. (Revision 9bc7e21dc0bd679e7b6506f264079630493237d4) Result = SUCCESS Christoph Kutzinski : 9bc7e21dc0bd679e7b6506f264079630493237d4 Files : changelog.html core/src/main/java/hudson/tasks/junit/JUnitResultArchiver.java core/src/main/java/hudson/tasks/junit/TestResult.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [junit] (JENKINS-7970) If all JUnit tests are skipped, the build fails
Todd Edwards commented on JENKINS-7970 If all JUnit tests are skipped, the build fails Thank you so much! 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] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Tomek Kaczanowski commented on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade same issue here (Jenins 1.506, Gradle 1.5, Ubuntu Linux 12.04) any chances on fixing this bug? BTW. not sure what does 1.22 refer to in the ticket title 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] [gradle] (JENKINS-17386) Gradle.properties ignored after 1.22 upgrade
Tomek Kaczanowski edited a comment on JENKINS-17386 Gradle.properties ignored after 1.22 upgrade same issue here (Jenins 1.506, Gradle 1.5, Ubuntu Linux 12.04) any chances on fixing this bug? BTW. "fixed" it with the following snippet run before gradle tasks: cp /home/jenkins/.gradle/gradle.properties gradle.properties.global cat gradle.properties.global gradle.properties rm gradle.properties.global 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] [maven] (JENKINS-11766) promoted-builds plugin can't deploy to Maven repo
Oliver Fabry commented on JENKINS-11766 promoted-builds plugin cant deploy to Maven repo Are there any news about 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] [core] (JENKINS-10524) winstone.ClientSocketException: Failed to write to client
Jesse Glick commented on JENKINS-10524 winstone.ClientSocketException: Failed to write to client Also java.net.SocketException: Broken pipe from Tomcat. 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] [clearcase-ucm] (JENKINS-16704) Wrong file delimiters - our case 8584
SCM/JIRA link daemon commented on JENKINS-16704 Wrong file delimiters - our case 8584 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/486f7d8d287fb9ca4fb533da422fb76a5fd2186f Log: JENKINS-16704 Updated dependency 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] [clearcase-ucm] (JENKINS-16704) Wrong file delimiters - our case 8584
SCM/JIRA link daemon commented on JENKINS-16704 Wrong file delimiters - our case 8584 Code changed in jenkins User: Christian Wolfgang Path: src/main/java/net/praqma/hudson/remoting/RemoteDeliver.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/afe4a8821770eadb025014a931d9762516c1261b Log: JENKINS-16704 Fixing force deliver mistake 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] [clearcase-ucm] (JENKINS-16804) Better exception handling in core, case 8644
SCM/JIRA link daemon commented on JENKINS-16804 Better exception handling in core, case 8644 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/00aff677f7bcffbe903aefc1da814e43951fadb2 Log: fixed JENKINS-16804 Updated deps 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06_2.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/00aadca2e8a74aaadf954c692a4750364c445833 Log: JENKINS-17067 Updated story 6 test 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/hudson/remoting/RemoteDeliver.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/b01029f2191dbb75d431f0ea3caa62eabf6b5504 Log: JENKINS-17067 Using source stream 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: pom.xml src/main/java/net/praqma/hudson/scm/CCUCMScm.java src/test/java/net/praqma/hudson/test/CCUCMRule.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/e0ec5410b9ed07eb388ad691113505ce11894f59 Log: JENKINS-17067 Perfecting test cases 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/7fd7416da403ee834f53424766e6941f4149b923 Log: JENKINS-17067 Added test on remote 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/b256542a3d10bdbdfb0f2965d48b7ec04f6630c8 Log: JENKINS-17067 Added test on slave This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: src/test/java/net/praqma/hudson/test/integration/enslaved/Story06WithSlaves.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06Base.java src/test/java/net/praqma/hudson/test/integration/userstories/Story06_2.java http://jenkins-ci.org/commit/clearcase-ucm-plugin/d9e5211a80d6a9163ce5d50276c9508afee3ee95 Log: JENKINS-17067 Split up tests 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] [clearcase-ucm] (JENKINS-17067) Finding the correct delivering Stream to cancel, case 8775
SCM/JIRA link daemon commented on JENKINS-17067 Finding the correct delivering Stream to cancel, case 8775 Code changed in jenkins User: Christian Wolfgang Path: pom.xml http://jenkins-ci.org/commit/clearcase-ucm-plugin/859a9e7b8670d5e05785a2ed06751f85e40d00b4 Log: JENKINS-17067 New profile 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] [vsphere-cloud] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
cforce edited a comment on JENKINS-16960 Status Code: 500/ NullPointerException when running command in slave script console Any sles command (e.g. zypper ) which works on my putty ssh console , when i input this in browser command window https://jenkins.mynet/jenkins/computer/testunix.entwicklung.priv/script i get the above nullpointer exception. The node is a vSphere Cloud Virtual Machine which shows "Virtual Machine found successfully" when i push "Test VM Connection" button in slave cfg screen. Btw. i can access the textunix server from jenkins server by putty console also. 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] [vsphere-cloud] (JENKINS-16960) Status Code: 500/ NullPointerException when running command in slave script console
cforce commented on JENKINS-16960 Status Code: 500/ NullPointerException when running command in slave script console Any sles command which works on my putty ssh console , when i input this in browser command window https://jenkins.mynet/jenkins/computer/testunix.entwicklung.priv/script i get the above nullpointer exception. The node is a vSphere Cloud Virtual Machine which shows "Virtual Machine found successfully" when i push "Test VM Connection" button in slave cfg screen. Btw. i can access the textunix server from jenkins server by putty console also. 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-failure-analyzer] (JENKINS-15948) Analyzer Icons aren't displayed if Jenkins isn't installed at root context.
Evgeny Kryukov commented on JENKINS-15948 Analyzer Icons arent displayed if Jenkins isnt installed at root context. Jenkins installed as war in tomcat. Image URL - http://myhost:8080/jenkins/jenkins/plugin/build-failure-analyzer/images/16x16/information.png is broken, double "jenkins" in path. 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] [sauce-ondemand] (JENKINS-17303) Null Pointer Exception for hasSauceOnDemandResults in jobs that aren't using that plugin
Jared Griffith commented on JENKINS-17303 Null Pointer Exception for hasSauceOnDemandResults in jobs that arent using that plugin Yeah, upgrading to the latest plug in corrects the problem. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-8647) Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException
Mark Waite closed JENKINS-8647 as Fixed Hudson 1.395 logs many messages about RecordReaper IllegalArgumentException Confirmed fixes long ago. Change By: Mark Waite (02/Apr/13 3:43 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] [mstest] (JENKINS-4632) MSTest plugin does not parse Visual Studio 2010 results
Mark Waite closed JENKINS-4632 as Fixed MSTest plugin does not parse Visual Studio 2010 results Confirmed fixed long ago. Change By: Mark Waite (02/Apr/13 3:43 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] [git] (JENKINS-16911) An invalid git reference repository path now causes clone to fail, previously did not fail
Mark Waite closed JENKINS-16911 as Fixed An invalid git reference repository path now causes clone to fail, previously did not fail Confirmed fixed Change By: Mark Waite (02/Apr/13 3:42 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] [git] (JENKINS-16914) Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo
Mark Waite closed JENKINS-16914 as Fixed Specifying multiple git repositories to git plugin causes git fetch to fail on all repos after first repo Confirmed fixed Change By: Mark Waite (02/Apr/13 3:43 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] [git] (JENKINS-16940) Git publisher fails with Invalid id: origin/master when trying to publish changes
Mark Waite closed JENKINS-16940 as Fixed Git publisher fails with Invalid id: origin/master when trying to publish changes Confirmed fixed. Change By: Mark Waite (02/Apr/13 3:44 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] [git] (JENKINS-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Mark Waite commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Does git-client plugin 1.0.5 resolve this issue with its switch from JGit implementation back to the Git command line client implementation? 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-4418) do shallow clone by default
Kelly Heller commented on JENKINS-4418 do shallow clone by default Thank you for reopening. I, too, would very much like to use '--depth' with git clone. 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Nicolas Berniolles commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly I updated my JIRA with this git-client plugin and so far I didn't see this issue coming back. I should say the new plugin resolve the 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] [core] (JENKINS-8686) IO stream copies are not done properly
dogfood commented on JENKINS-8686 IO stream copies are not done properly Integrated in jenkins_main_trunk #2429 FIXED JENKINS-8686 (Revision dc94b7d0633c0a6e5375bdf1bec2b9dede461da3) Result = SUCCESS kohsuke : dc94b7d0633c0a6e5375bdf1bec2b9dede461da3 Files : core/src/main/java/hudson/util/StreamCopyThread.java core/src/main/java/hudson/Proc.java core/src/main/java/hudson/util/io/ZipArchiver.java cli/src/main/java/hudson/cli/CLI.java core/src/main/java/hudson/Util.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ec2] (JENKINS-17257) EC2 plugin fails to launch slave (IndexOutOfBoundsException)
t r
commented on JENKINS-17257
EC2 plugin fails to launch slave (IndexOutOfBoundsException)
We see this error as well. It happens quite often when trying to launch a bunch of new slaves at the same time. When you work with the ec2 api you have to assume that every call can fail, and even calls that succeed might not return the response that you expect. In this case the instance was launched but the subsequent status-polling returns an empty list where you'd expected our new instance to be.
The fix is to make the retry loop in EC2Computer.java check for the case where the DescribeInstancesRequest succeeds but returns an empty instance list. This same defensive approach should be done for all remote calls that might return lists of things. Don't assume that list.get(0) is safe.
I'll post the local hack that we're using to get by while we wait for the official fixes in the github master.
private Instance _describeInstance() throws AmazonClientException, InterruptedException {
// Sometimes even after a successful RunInstances, DescribeInstances
// returns an error for a few seconds. We do a few retries instead of
// failing instantly. See [JENKINS-15319].
Instance myInstance = null;
for (int i = 0; i 10; i++) {
myInstance = _describeInstanceOnce();
if (myInstance == null) {
// retry in 5 seconds.
Thread.sleep(5000);
continue;
}
}
if (myInstance == null)
throw new AmazonClientException("No reservation for " + getNode().getInstanceId());
return myInstance;
}
private Instance _describeInstanceOnce() {
Instance myInstance = null;
try {
DescribeInstancesRequest request = new DescribeInstancesRequest();
request.setInstanceIds(Collections.StringsingletonList(getNode().getInstanceId()));
ListReservation reservations = EC2Cloud.get().connect().describeInstances(request).getReservations();
if (reservations != null reservations.size() 0) {
Reservation reservation = reservations.get(0);
ListInstance instances = reservation.getInstances();
if (instances != null instances.size() 0) {
myInstance = instances.get(0);
}
}
} catch (Exception e) {
e.printStackTrace();
}
return myInstance;
}
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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Mark Waite resolved JENKINS-17186 as Fixed Linux: if there is a recursive directory within the git repo youre building, the initial checkout will fail badly Fixed by git-client-plugin 1.0.5 which switches the default implementation back to command line git. The JGit implementation is not yet complete enough to satisfy all the Jenkins use cases. Change By: Mark Waite (02/Apr/13 6:15 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] [s3] (JENKINS-15677) S3 plugin should retry few times if upload to S3 fails
David Glasser commented on JENKINS-15677 S3 plugin should retry few times if upload to S3 fails OK, you don't have to add this to the Java command-line: you have to add this to the JVM options for your slaves. But it doesn't seem to work! Namely, it does show up in the System information page for the slave, but it doesn't actually affect the code What confuses me is that https://github.com/aws/aws-sdk-java/commit/a3a2c56f27770e241f777a63034743d95d6a7486#L198R1057 sure makes it look like this support was added in 1.3.20 of AWS. And that's the version that the s3 plugin uses. But it still doesn't take effect! And hell... I even disassembled AmazonS3Client.class from inside the JAR and the code to do the getProperty is not there! 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] [s3] (JENKINS-15677) S3 plugin should retry few times if upload to S3 fails
David Glasser commented on JENKINS-15677 S3 plugin should retry few times if upload to S3 fails OK, it looks like it's actually added in 1.3.21, not 1.3.20. 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-14656) Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually
Jason Spangler commented on JENKINS-14656 Jenkins cannot guarantee that it will push the exact same build through a build pipeline if some of the steps are triggered manually Good investigation and workaround so far! I have a more complex situation where a parallel job uses the Join plugin to run multiple jobs in parallel then combines the results from multiple jobs. However, the upstream project and thus UPSTREAM_BUILD_NUMBER is always just the last job to complete from the parallel set so it can't access the build numbers for the other parallel jobs. 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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker
created JENKINS-17438
xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Issue Type:
Bug
Affects Versions:
current
Assignee:
Gregory Boissinot
Components:
xunit
Created:
02/Apr/13 8:14 PM
Description:
When using the xUnit Custom Tool and specifying a Global Property (ex. ${XUNIT_RFT_TO_JUNIT} ) as the Custom stylesheet, the property does not get resolved. This makes the plugin look for a file named "${XUNIT_RFT_TO_JUNIT}" in the workspace directory. When is should be looking for the path specified in the Global Property
Note: The Custom Tool Pattern accepts and resolves Global Properties just fine. (ex ${XUNIT_CUSTOM_XML} )
Project:
Jenkins
Priority:
Minor
Reporter:
Eric Anker
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] [xunit] (JENKINS-17438) xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved
Eric Anker updated JENKINS-17438 xunit - Custom Tool - Custom stylesheet - Global Property specified does not get resolved Config screenshot console screenshot Change By: Eric Anker (02/Apr/13 8:15 PM) Attachment: XUNIT_CUSTOM1.png Attachment: XUNIT_CUSTOM2.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] [subversion] (JENKINS-17431) 500 Internal Server Error on attempt to run a build
Slava Maslenitsyn commented on JENKINS-17431 500 Internal Server Error on attempt to run a build hello, my I also suggest yet another approach. 1. cd to checkout directory 2. capture hd1 the amount of hard drive space taken 3. run svn update . 4. capture hd2 the amount of hard drive space taken if hd1 != hd2 - there are changes in this working space - run the build. I think it will be even more efficient then local svn command, so less time spent on the build + more reliable. regards, Slava 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] [junit] (JENKINS-5698) Show test-result directly from reportng/testng generated html
Khalith Basha edited a comment on JENKINS-5698 Show test-result directly from reportng/testng generated html I would like to knw the plugin name?? could u please say ASAP 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
Victor Hugo commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace Please, take a look in my pull request on Github https://github.com/jenkinsci/xcode-plugin/pull/22 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Hajime Fujita commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I had a similar problem in my environment, where the master and the slave nodes use different username for jenkins. Say, "masteruser" for the master node and "slaveuser" for the slave. When login failed for the slave, Jenkins tried to connect to the slave node with "masteruser", according to the log file in the slave node (/var/log/auth.log, since it's Ubuntu-based host). When this happened, I came back to the slave node configuration page (Manage Jenkins - Manage Nodes - (particular slave node) - Configure). There were multiple credentials in "Launch Method - Credentials" drop down list. I could see four items, saying: slaveuser (slavehostname) masteruser (slavehostname) slaveuser (slavehostname) masteruser (slavehostname) Clearly something weird was going on there (duplicated entries). Anyway, I selected the third one for some reason (second and fourth are definitely the wrong ones), then it suddenly worked. 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] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Casey McGinty updated JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Change By: Casey McGinty (03/Apr/13 2:13 AM) Summary: Perforce quickcleanfailes QuickCleanDoesNotRemoveAllBuildFiles;Fails to removeallfiles,failestohaltbuild HalttheBuild 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] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Casey McGinty updated JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Change By: Casey McGinty (03/Apr/13 2:45 AM) Description: IhitacasewherethePerforcequickcleanoptiondoesnotremoveallofmyclassfiles.Thisleavesaclassfileinthe/classesoutputdirectory,andwhenrebuilt,blockstheanonymous(MyClass$Anon.class)filesfrombeinggenerated,breakingthebuild.Idonotseeanyerrormessagesthatindicatetherootcauseofthisissue.Thisissuestookmehourstotrackdownandverify.Ifquick-cleanhadabortedthebuildwhenitfails,thiswouldhavesavedalotofheadache. Hereisfailingdirectorybeforetheclean:d4/2/20133:52PMfirstpersond4/2/20133:52PMorbit-a---4/2/20133:52PM16553BasicView.class-a---4/2/20133:52PM4859BasicViewPropertyLimits.class-a---4/2/20133:52PM2793ViewElevationAnimator.class-a---4/2/20133:52PM470ViewModel.class-a---4/2/20133:52PM1237ViewPropertyAccessor$ElevationAccessor.class-a---4/2/20133:52PM913ViewPropertyAccessor$EyePositionAccessor.class-a---4/2/20133:52PM876ViewPropertyAccessor$HeadingAccessor.class-a---4/2/20133:52PM868ViewPropertyAccessor$PitchAccessor.class-a---4/2/20133:52PM1422ViewPropertyAccessor.class-a---4/2/20133:52PM826ViewPropertyLimits.class-a---4/2/20133:52PM1366ViewUtil$ViewState.class-a---4/2/20133:52PM11575ViewUtil.classAfterthecleanIget:d4/2/20134:43PMfirstpersond4/2/20134:43PMorbit-a---4/2/20133:52PM1422ViewPropertyAccessor.classAsfarasIcantell,thereisnoreasonwhythisfileshouldnothavebeenremoved. 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
Jay Graves commented on JENKINS-12800 Cant add xcodebuild parameters including whitespace The work around I use is to set a -xcconfig CodeSign.xcconfg and set your CODE_SIGN_IDENTITY="iPhone Distribution" inside there. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [ssh-slaves] (JENKINS-17366) ssh slave login via keyfile not working in 0.23
Stephen Morrison commented on JENKINS-17366 ssh slave login via keyfile not working in 0.23 I'm seeing something similar, where when I select the correct credential with the right username it works, but when I come back later the credential in the slave config has mysteriously changed to be the user of the Master and Jenkins can no longer log into the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Rob Petti commented on JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Newer versions of Windows will sometimes allow a file to be silently "deleted" but it won't actually be removed from the file system until all open file handled have been closed. I'll double check to make sure that the plugin at least throws a warning if a file isn't deleted, but I don't believe there is a lot else that can be done. 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] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Rob Petti edited a comment on JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Newer versions of Windows will sometimes allow a file to be silently "deleted" but it won't actually be removed from the file system until all open file handles have been closed. I'll double check to make sure that the plugin at least throws a warning if a file isn't deleted, but I don't believe there is a lot else that can be done. 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] [perforce] (JENKINS-17439) Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build
Casey McGinty commented on JENKINS-17439 Perforce Quick Clean Does Not Remove All Build Files; Fails to Halt the Build Rob, I know windows file locking can make it tricky to delete files. However in this case, there were probably 1500 or more class files, and the only file not deleted was the only listed above. I was able to consistently reproduce this bug, so it wasn't just a one-off case. If there is some debug information I can turn on, then I can get you the output from Jenkins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
