[JIRA] [copy-to-slave] (JENKINS-18899) Child job finishes with SUCCESS status even before copy-to-plugin finishes copying files from slave to master
Vivekanand SV created JENKINS-18899 Child job finishes with SUCCESS status even before copy-to-plugin finishes copying files from slave to master Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Components: copy-to-slave Created: 24/Jul/13 6:02 AM Description: Scenario: I have jenkins installed (debian package) as master in Ubuntu, have 2 slaves for 32/64 bit Windows 7. I run some test cases in the slave windows OS' and use the use this plugin to get back the files to master. This is a multi configuration job and after child jobs (1 child job each for 2 slaves) are finished I publish combined HTML reports in the parent job. Now the problem that I face here is, the child job finishes with "SUCCESS" without waiting for the copy-to-plugin post build action to finish. So the HTML Publisher in the parent job fails as the files are not yet copied to the master. Note 1 : - Though the child job finishes, the copy-to-slave plugin continues to work and files are successfully copied to the master. Note 2 : - The child job finishes before the post build action only for copy-to-plugin, it waits till the post build actions are finished for other plugins. Environment: Jenkins version - 1.523 Master OS - Ubuntu 12.04 Slave OS - Windows 7 Copy To Slave Plugin - 1.4 Project: Jenkins Priority: Major Reporter: Vivekanand SV This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copy-to-slave] (JENKINS-18899) Child job finishes with SUCCESS status even before copy-to-plugin finishes copying files from slave to master
Vivekanand SV updated JENKINS-18899 Child job finishes with SUCCESS status even before copy-to-plugin finishes copying files from slave to master Change By: Vivekanand SV (24/Jul/13 6:05 AM) Description: Scenario:Ihavejenkinsinstalled(debianpackage)asmasterinUbuntu,have2slavesfor32/64bitWindows7.IrunsometestcasesintheslavewindowsOSanduse theuse thisplugintogetbackthe files testcaseresults tomaster.Thisisamulticonfigurationjobandafterchildjobs(1childjobeachfor2slaves)arefinishedIpublishcombinedHTMLreportsintheparentjob.NowtheproblemthatIfacehereis,thechildjobfinisheswithSUCCESSwithoutwaitingforthecopy-to-pluginpostbuildactiontofinish.SotheHTMLPublisherintheparentjobfailsasthefilesarenotyetcopiedtothemaster.*Note1*:-Thoughthechildjobfinishes,thecopy-to-slaveplugincontinuestoworkandfilesaresuccessfullycopiedtothemaster.*Note2*:-Thechildjobfinishesbeforethepostbuildactiononlyforcopy-to-plugin,itwaitstillthepostbuildactionsarefinishedforotherplugins. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-17096) Differences in config spec detected when config spec is read from file
SCM/JIRA link daemon commented on JENKINS-17096 Differences in config spec detected when config spec is read from file Code changed in jenkins User: Vincent Latombe Path: src/main/java/hudson/plugins/clearcase/ConfigSpec.java src/test/java/hudson/plugins/clearcase/ConfigSpecTest.java src/test/resources/hudson/plugins/clearcase/ct-catcs-2-CRLF.log src/test/resources/hudson/plugins/clearcase/ct-catcs-2-LF.log http://jenkins-ci.org/commit/clearcase-plugin/732b41ecd594ad6b662edafbcea8cf0b046a9f0e Log: JENKINS-17096 Convert OS specific separators upfront in ConfigSpec Raw config spec may have been defined with different OS separators, leading to issues when comparing them. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer] (JENKINS-18883) Value of cron 'Deploy Periodically' not visible
Raphael CHAUMIER resolved JENKINS-18883 as Fixed Value of cron Deploy Periodically not visible Change By: Raphael CHAUMIER (24/Jul/13 7:20 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18881) NPE on DeploymentTaskResult
Raphael CHAUMIER resolved JENKINS-18881 as Fixed NPE on DeploymentTaskResult Change By: Raphael CHAUMIER (24/Jul/13 7:21 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-17300) weblogic.Deployer custom arguments
Raphael CHAUMIER resolved JENKINS-17300 as Fixed weblogic.Deployer custom arguments Change By: Raphael CHAUMIER (24/Jul/13 7:23 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [jobconfighistory] (JENKINS-18900) [JobConfigurationHistory] Wrong history being displayed
Steffen Breitbach created JENKINS-18900 [JobConfigurationHistory] Wrong history being displayed Issue Type: Bug Affects Versions: current Assignee: Mirko Friedenhagen Attachments: Job Configuration History Jenkins.png Components: jobconfighistory Created: 24/Jul/13 7:23 AM Description: When clicking on "Job Config History" from within a job, it seems that all (global) recent job changes are being displayed rather than the job changes of the job itself. On the other hand, the actual configuration changes of the job itself are missing (see the screenshot). Clicking on the "View as XML" link however will display the correct xml that belongs to the job as it seems. config-history directory listing drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-42-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-54-08 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_11-54-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_12-50-06 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-02-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-02-24 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_13-21-05 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-26-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-28-01 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-04-27_14-42-55 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-05-16_09-40-55 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-06_09-16-45 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-09-11 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-09-14 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-19_15-10-19 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-06-28_09-24-09 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-02_11-52-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-02_11-57-28 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-05-38 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-06-40 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-11-04 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_12-26-12 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_14-47-51 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_14-57-27 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_15-09-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-06_15-16-25 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-07_01-02-23 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-10_17-32-07 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-10_17-32-09 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-15_16-18-29 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-15_16-19-11 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-16_08-09-36 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-16_08-09-37 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-08-27_17-22-28 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-12_13-58-03 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-51-05 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-52-07 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-09-24_16-52-08 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-46 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-47 drwxr-xr-x 2 jboss jboss 41 Feb 27 20:41 2012-11-22_10-32-49 Environment: Jenkins 1.509.2 LTS Job Configuration History 2.4 Tomcat 6.0.36 Java 1.7.0 u25-b15 Project: Jenkins Labels: plugin plugins job Priority: Major Reporter: Steffen Breitbach
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Raphael CHAUMIER resolved JENKINS-18812 as Fixed Redeployment feature Change By: Raphael CHAUMIER (24/Jul/13 7:25 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Raphael CHAUMIER commented on JENKINS-18812 Redeployment feature I've just released the 2.4 version with a new feature. See 'Override deployment execution' chapter in the plugin documentation This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer] (JENKINS-17035) Updated wiki
Raphael CHAUMIER closed JENKINS-17035 as Fixed Updated wiki Change By: Raphael CHAUMIER (24/Jul/13 7:26 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] [weblogic-deployer] (JENKINS-16808) deployment of more files
Raphael CHAUMIER closed JENKINS-16808 as Fixed deployment of more files Change By: Raphael CHAUMIER (24/Jul/13 7:25 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] [weblogic-deployer] (JENKINS-18882) Add icon with transparency
Raphael CHAUMIER updated JENKINS-18882 Add icon with transparency Change By: Raphael CHAUMIER (24/Jul/13 7:28 AM) Due Date: 24/Jul/13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer] (JENKINS-17879) Needs the ability to use Weblogic created keystore user and key files instead of having a plain-text administration password out in a config file
Raphael CHAUMIER closed JENKINS-17879 as Fixed Needs the ability to use Weblogic created keystore user and key files instead of having a plain-text administration password out in a config file Change By: Raphael CHAUMIER (24/Jul/13 7:27 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] [weblogic-deployer] (JENKINS-14041) Hide admin password
Raphael CHAUMIER commented on JENKINS-14041 Hide admin password Since 2.3 version, you can user userconfigfile parameter to hide password This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [weblogic-deployer] (JENKINS-14041) Hide admin password
Raphael CHAUMIER closed JENKINS-14041 as Postponed Hide admin password Change By: Raphael CHAUMIER (24/Jul/13 7:29 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] [weblogic-deployer] (JENKINS-18812) Redeployment feature
Miquel Serralta commented on JENKINS-18812 Redeployment feature Gorgeous!! I will try it as soon I can. I let you know. 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-18441) Maven 2 jobs fail (exception in MavenFingerprinter)
newenigma reopened JENKINS-18441 Maven 2 jobs fail (exception in MavenFingerprinter) Hi This issue is still occurring for me on 1.523 From looking so far, it is only happening on Maven builds with packaging of pom. Change By: newenigma (24/Jul/13 9:11 AM) Resolution: Fixed Status: Resolved Reopened Assignee: JesseGlick MarcSanfacon This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18901) Non-ASCII characters in app name cause upload to fail
Malcolm Box created JENKINS-18901 Non-ASCII characters in app name cause upload to fail Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: testflight Created: 24/Jul/13 9:17 AM Description: Changing an Android app name to include the string "RTÉ" causes subsequent Testflight uploads to fail: Uploading to testflight File: /Users/admin/.jenkins/jobs/The Hit Android/workspace/android/TheHit2013/bin/TheHit2013-debug.apk POST Request: testflight.TestflightUploader$UploadRequest@1aee419f[filePaths=**/debug.apk,dsymPath=,apiToken=**,teamToken=***,notifyTeam=false,buildNotes=The Hit Android automatic build No changes since last build ,file=/Users/admin/.jenkins/jobs/The Hit Android/workspace/android/TheHit2013/bin/TheHit2013-debug.apk,dsymFile=null,lists=tellybug,replace=false,proxyHost=null,proxyUser=null,proxyPass=,proxyPort=0,debug=true] Incorrect response code: 400 'ascii' codec can't decode byte 0xc3 in position 2: ordinal not in range(128) Here's the character details - note the 0xc3 byte É LATIN CAPITAL LETTER E WITH ACUTE Unicode: U+00C9, UTF-8: C3 89 Uploading the APK directly via the Testflight web UI works as expected. Environment: Mac OS X 10. Project: Jenkins Labels: plugin Priority: Major Reporter: Malcolm Box This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [gui] (JENKINS-14556) Timeline is wrong when tests are executed in parallel
evernat commented on JENKINS-14556 Timeline is wrong when tests are executed in parallel Is it reproduced with a recent Jenkins version? If yes, can you explain how do you execute tests in parallel? Or better yet, can you give a scenario to reproduce? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18441) Maven 2 jobs fail (exception in MavenFingerprinter)
newenigma edited a comment on JENKINS-18441 Maven 2 jobs fail (exception in MavenFingerprinter) Hi This issue is still occurring for me on 1.523 From looking so far, it is only happening on Maven builds with packaging of pom. EDIT: Scrap above comment, I can see it is still happening on Maven builds with packaging of war and jar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
joseph nelson commented on JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex We are seeing this bug on our jenkins instance. It does NOT appear to cause build failure with all Maven 2.2.1 POMs, only one project of several is having this issue after upgrading to Jenkins versions 1.517 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-7089) OutOfMemoryError while parsing 11 mb log file
vdupain reopened JENKINS-7089 OutOfMemoryError while parsing 11 mb log file We have the same issue: OutOfMemoryError. Build was successfull whereas there are tests failures. In one of the surefire-reports directory, there is more than 400 Mb of files. Workaround was to add more memory to the job (-Xmx2048m to MAVEN_OPTS). [ERROR] There are test failures. Please refer to /data/jenkins-agents/local-slave-2/workspace/MEZZO-pdo-100pro-ps-ci/pdo-100pro-ps-mediation/target/surefire-reports for the individual test results. [JENKINS] Recording test results java.io.IOException: Remote call on channel failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) at $Proxy2.execute(Unknown Source) at hudson.maven.MavenBuildProxy$Filter.execute(MavenBuildProxy.java:191) at hudson.maven.reporters.SurefireArchiver.postExecute(SurefireArchiver.java:160) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:453) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:435) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:87) at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:228) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.jvnet.hudson.maven3.launcher.Maven3Launcher.main(Maven3Launcher.java:79) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.plexus.classworlds.launcher.Launcher.launchStandard(Launcher.java:329) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:239) at org.jvnet.hudson.maven3.agent.Maven3Main.launch(Maven3Main.java:158) at hudson.maven.Maven3Builder.call(Maven3Builder.java:100) at hudson.maven.Maven3Builder.call(Maven3Builder.java:66) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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) Caused by: java.lang.OutOfMemoryError: Java heap space at java.util.Arrays.copyOf(Arrays.java:2786) at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:94) at java.io.ObjectOutputStream$BlockDataOutputStream.drain(ObjectOutputStream.java:1847) at java.io.ObjectOutputStream$BlockDataOutputStream.setBlockDataMode(ObjectOutputStream.java:1756) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1169) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:330) at hudson.remoting.UserRequest._serialize(UserRequest.java:155) at hudson.remoting.UserRequest.serialize(UserRequest.java:164) at
[JIRA] [warnings] (JENKINS-7089) OutOfMemoryError while parsing 11 mb log file
vdupain updated JENKINS-7089 OutOfMemoryError while parsing 11 mb log file Change By: vdupain (24/Jul/13 9:21 AM) Environment: WindowsslaveofWindowsmaster ,jenkins1.509.2masterandslavesonLinuxRHEL This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18902) Clicking the (detail) link under Changes in dependency shows incorrect changes
Timo Kamarainen created JENKINS-18902 Clicking the (detail) link under Changes in dependency shows incorrect changes Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 24/Jul/13 9:22 AM Description: When looking at build results for a specific build number, for a build that has dependencies to other builds, the (detail) link for "Changes in dependency" shows incorrect changes. For example, if the dependency has gone from #16 - #19 the details show changes for build #16 as well. This is incorrect since the changes for the build #16 have already been included in the previous build. In short, the details for a dependency from #16 - #19 should really show changes from #17 - #19. Environment: Jenkins ver. 1.522 Project: Jenkins Labels: jenkins gui Priority: Minor Reporter: Timo Kamarainen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
joseph nelson commented on JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Throwing this out there as a possible cause: I turned on verbose logging for Maven and noticed the following: 02:31:33 Loaded org.apache.commons.codec.digest.DigestUtils from file:/home/builduser/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar When I looked up that package's javadocs for the the md5Hex method, I see: (http://commons.apache.org/proper/commons-codec/apidocs/org/apache/commons/codec/digest/DigestUtils.html#md5Hex(java.io.InputStream) md5Hex public static String md5Hex(InputStream data) throws IOException Calculates the MD5 digest and returns the value as a 32 character hex string. Parameters: data - Data to digest Returns: MD5 digest as a hex string Throws: IOException - On error reading from the stream Since: 1.4 That this method only exists since 1.4 version of this JAR is a good canidate for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18441) Maven 2 jobs fail (exception in MavenFingerprinter)
newenigma resolved JENKINS-18441 as Fixed Maven 2 jobs fail (exception in MavenFingerprinter) Change By: newenigma (24/Jul/13 9:49 AM) Status: Reopened Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [infrastructure] (JENKINS-14095) RedHat RPM has different checksum than repository metadata
evernat commented on JENKINS-14095 RedHat RPM has different checksum than repository metadata @billy paul Is it still an 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] [www] (JENKINS-18903) In a jobs page Build history showing build completed but in jenkins home page in BuildExecutor Status showing that job is currently running
Renjini K R created JENKINS-18903 In a jobs page Build history showing build completed but in jenkins home page in BuildExecutor Status showing that job is currently running Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: jenkins_build executor status.PNG, jobs_build _history.PNG Components: www Created: 24/Jul/13 10:07 AM Description: In Jenkins dashboard, builld executor status showing build number 39 for job 'x' is progressing. In job 'x' build history, it is showing build number 39 completed , but build number 40 is pending. Due Date: 24/Jul/13 12:00 AM Environment: Os : CentOs 64 bit Java Version: 1.7.0_11 Project: Jenkins Labels: jenkins Priority: Major Reporter: Renjini K R This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14713) Cancel permission is granted for users having build permission
Hangsu Ma assigned JENKINS-14713 to Hangsu Ma Cancel permission is granted for users having build permission Change By: Hangsu Ma (24/Jul/13 10:10 AM) Assignee: HangsuMa This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
SCM/JIRA link daemon commented on JENKINS-13247 disk usage should not follow symlinks Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/hudson/plugins/disk_usage/DiskUsageThread.java http://jenkins-ci.org/commit/disk-usage-plugin/361984ea3af33b8cbbb6910e2e8ad8e8bac431a3 Log: JENKINS-13247 don't calculate symlinks Tested with one file and symlink to it in workspace. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
SCM/JIRA link daemon commented on JENKINS-13247 disk usage should not follow symlinks Code changed in jenkins User: Vojtěch Juránek Path: .gitignore src/main/java/hudson/plugins/disk_usage/DiskUsageThread.java http://jenkins-ci.org/commit/disk-usage-plugin/e1334059b37d17c0885fb940ce20fc41a1515163 Log: Merge pull request #12 from KostyaSha/master JENKINS-13247 don't calculate symlink file size Compare: https://github.com/jenkinsci/disk-usage-plugin/compare/301ef38d342e...e1334059b37d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [eloyente] (JENKINS-18770) ElOyente plugin blocks jenkins configuration page
SCM/JIRA link daemon commented on JENKINS-18770 ElOyente plugin blocks jenkins configuration page Code changed in jenkins User: Isabel Fernandez Diaz Path: pom.xml src/main/java/com/technicolor/eloyente/ElOyente.java src/main/java/com/technicolor/eloyente/XPathExpressionHandler.java src/main/resources/com/technicolor/eloyente/ElOyente/config.jelly http://jenkins-ci.org/commit/eloyente-plugin/1b12f4784a6d95638b1ae2086ff9751f2f315199 Log: Bug fixed: https://issues.jenkins-ci.org/browse/JENKINS-18770 (crash saving main configuration). Added validation for xpath expressions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [safe-restart] (JENKINS-18904) Restarting when builds are running
Corneil du Plessis created JENKINS-18904 Restarting when builds are running Issue Type: Bug Assignee: Unassigned Components: safe-restart Created: 24/Jul/13 10:48 AM Description: I noticed that after we started adding slaves the safe-restart would just restart Jenkins even when builds are still active on master and/or slave Environment: Jenkins 1.520 safe-restart 0.3 Project: Jenkins Priority: Critical Reporter: Corneil du Plessis This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18424) NPE while reading config.xml
Steffen Flemming commented on JENKINS-18424 NPE while reading config.xml With Jenkins ver. 1.523 and all plugins up2date issue persists! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [www] (JENKINS-18905) A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build of the same job.
Renjini K R created JENKINS-18905 A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build of the same job. Issue Type: Bug Affects Versions: current Assignee: Unassigned Attachments: Capture38.PNG, Capture39.PNG Components: www Created: 24/Jul/13 11:27 AM Description: 38th build of a job completed and it sent a email notification using email-ext plugin at the same time we got email notification of the next build of the same job. Due Date: 24/Jul/13 12:00 AM Environment: os:CentOS 64 java version 1.7.0_11 Project: Jenkins Labels: jenkins Priority: Major Reporter: Renjini K R This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [www] (JENKINS-18905) A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build .
Renjini K R updated JENKINS-18905 A job completed and sent email notification using email-extension plugin.at the same time we got email notification of the next build . Change By: Renjini K R (24/Jul/13 11:28 AM) Summary: Ajobcompletedandsentemailnotificationusingemail-extensionplugin.atthesametimewegotemailnotificationofthenextbuild ofthesamejob . Description: 38thbuildofajobcompletedanditsentaemailnotificationusingemail-extpluginatthesametimewegotemailnotificationofthenextbuild ofthesamejob . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18633) User with the right READ is able to change main server description
Raphael CHAUMIER assigned JENKINS-18633 to Raphael CHAUMIER User with the right READ is able to change main server description Change By: Raphael CHAUMIER (24/Jul/13 11:42 AM) Assignee: RaphaelCHAUMIER This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-13247) disk usage should not follow symlinks
vjuranek commented on JENKINS-13247 disk usage should not follow symlinks Hi, I merged PR #12. Before I release it, what the concerns about performance actually are about? On JDK7, there's native support for checking if the file is symlink, on older JDKs rest of the hudson.Util.isSymlink() will be used, but it doesn't seem me that is would cause any significant issues. If I miss something, please let me know and I'll make skipping symlinks optional. 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] [ssh-slaves] (JENKINS-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Johnny Willemsen commented on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel We see here similar problems, time of the slaves is out of sync according to Jenkins with 5 months, but that is not the case. With Solaris 10 x86_64 and Sparc slaves we also have problems connecting using the same error, Solaris 10 ships with "java full version "1.5.0_12-b04" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18706) ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel
Johnny Willemsen edited a comment on JENKINS-18706 ssh-saves 0.27 and jenknis 1.522 not working: java.io.IOException: Unexpected termination of the channel We see here similar problems, time of the slaves is out of sync according to Jenkins with 5 months, but that is not the case. With Solaris 10 x86_64 and Sparc slaves we also have problems connecting using the same error, Solaris 10 ships with "java full version "1.5.0_12-b04". The log when I am using Java webstart: Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Locating server among [http://jenkins.remedy.nl/] Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins.remedy.nl:45673 Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Jul 24, 2013 1:15:46 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connected Jul 24, 2013 1:15:47 PM hudson.remoting.SynchronousCommandTransport$ReaderThread run SEVERE: I/O error in channel channel java.io.IOException: Unexpected termination of the channel at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:50) Caused by: java.io.EOFException at java.io.ObjectInputStream$BlockDataInputStream.peekByte(ObjectInputStream.java:2498) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1273) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348) at hudson.remoting.Command.readFrom(Command.java:92) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:72) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48) Jul 24, 2013 1:15:47 PM hudson.remoting.jnlp.Main$CuiListener status This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17960) Indicate if tests don't go to plan
Bruno P. Kinoshita updated JENKINS-17960 Indicate if tests dont go to plan Change By: Bruno P. Kinoshita (24/Jul/13 12:42 PM) Labels: 1.13 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17781) TAP Plugin: fails to report errors for TAP streams where # tests run doesn't match plan
Bruno P. Kinoshita updated JENKINS-17781 TAP Plugin: fails to report errors for TAP streams where # tests run doesnt match plan Change By: Bruno P. Kinoshita (24/Jul/13 12:44 PM) Labels: 1.13 parse-errortap This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [vs-code-metrics] (JENKINS-18369) Jenkins lock metrics.xml file
Yasuyuki Saito resolved JENKINS-18369 as Fixed Jenkins lock metrics.xml file Release complete. Change By: Yasuyuki Saito (24/Jul/13 12:59 PM) 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] [core] (JENKINS-17116) gracefull job termination
Martin dAnjou commented on JENKINS-17116 gracefull job termination Jenkins leaks processes when jobs are killed. I think this is related to this issue, so instead of creating a new bug report, I am adding this comment. To reproduce the process leak, create a new freestyle job from a fresh install, and enter this script: #!/usr/bin/python import signal import time print "Main 1" def handler(*ignored): print "Ignored 1" time.sleep(120) print "Ignored 2" print "Main 2" signal.signal(signal.SIGTERM, handler) print "Main 3" time.sleep(120) print "Main 4" Then execute the build, and after a few seconds once the build is running, hit the red x button to kill the job. After the job is killed and Jenkins is done, go to the terminal and look for the python process. You should find something like this: $ ps -efH ... mdanjou 2154 2150 0 08:22 pts/000:00:00 bash mdanjou 2531 2154 16 08:24 pts/000:00:36 java -jar jenkins.war mdanjou 2601 2531 0 08:25 pts/000:00:00 /usr/bin/python /tmp/hudson3048464595979281901.sh The python script is still in memory, and still executing. However, Jenkins has cut the ties to the python script. Jenkins must not cut the ties until the script is done. In this comment, the script is a simple example, in real project scripts, the signal handler is used to clean up temporary files, and to terminate gracefully (e.g. killing other spawned processes). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
joseph nelson commented on JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Isolated it to this: extensions extension groupIdorg.springframework.build.aws/groupId artifactIdorg.springframework.build.aws.maven/artifactId version3.0.0.RELEASE/version /extension /extensions If I remove that extension, the error goes away. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-18164) Matrix Jobs Do Not Get Run When Updating a Dynamic Axis
tim johnston commented on JENKINS-18164 Matrix Jobs Do Not Get Run When Updating a Dynamic Axis Some more log output. It seems like the workUnit is fine, because the two pieces of axis data displayed in hudson.model.queue.WorkUnit@e617 is correct. For some reason, it appears that task.createExecutable() is returning null. FINE: Executor #0 for QMWFCRP1 completed null in 0ms Jul 23, 2013 6:31:04 PM hudson.model.Executor run SEVERE: Executor threw an exception java.lang.NullPointerException at hudson.model.Executor.run(Executor.java:234) Jul 23, 2013 6:31:04 PM hudson.model.Executor FINE: Executor #0 for QMWFCRP1 is going to execute null Jul 23, 2013 6:31:04 PM hudson.model.Executor FINE: Executor #0 for QMWFCRP1 grabbed hudson.model.queue.WorkUnit@e617work=RunJTF » WFS_Hours_Common_SCTAndCT,All.WFS.MSS.07.00.01.parfixes from queue This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-11286) Git plugin does not timeout
c Kirschner commented on JENKINS-11286 Git plugin does not timeout 1 year and 4 months later this is still an issue. In our Jenkins are regularly (2 times or more a week) git processes wich stall / hang forever. Its quite annoying if these fill all scm slots and our entire build server does nothing. To get it running again i have to kill all git and git-remote-https processes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [active-directory] (JENKINS-18906) Problem with Active Directory plugin and Role-Based Strategy plugin working together
Angelo Cordova created JENKINS-18906 Problem with Active Directory plugin and Role-Based Strategy plugin working together Issue Type: Bug Affects Versions: current Assignee: Daniel Petisme Attachments: stacktrace1.txt, stacktrace2.txt Components: active-directory, role-strategy Created: 24/Jul/13 1:47 PM Description: Hello everyone I'm totally lost in this moment. It's my first approach to Jenkins and I need to figure out if it's possible to combine both plugins named above. When we configured Jenkins at the beginning, we used "Jenkins's own user database" (for security realm) and "Matrix-Based security" (for authorization). So we could create an give permissions to user manually. That was fine, but we are a big number of users, and it takes a lot of time to set up every user manually. So we try something "better". We change Access control configuration. For Security realm, now we use "Active directory" (it should be ok, because we use the same for other systems/programs) so every user can access using the "user" and "password" of corporative e-mail account. And for Authorization we use "Role-Based Strategy", so instead of giving specific permission user by user, we created "groups" (e.g. admin, developer, visitor, etc.) and every user is assigned to a group, and we give different permission to different groups. With this, the first problem was, when we logged in, we have no permissions (just read) and nobody had admin permission. Trying to solve this issue, I access to Jenkins "config.xml" file and set up one admin. I logged in with this admin account, and I got access to everything, but when I went to the users list(Manage and assign Roles - Assign role), it was empty, just my name were there but with a red error message: "Failed to test the validity of the user name " and a link saying "show details". I pressed the link an got the following: (see stacktrace1.txt) After making some research I found this page https://wiki.jenkins-ci.org/display/JENKINS/Active+Directory+plugin and followed the instructions of "Troubleshooting", then I got this: (see stacktrace2.txt) So I don't know how to fix this, I've searched on the web but I didn't find information about using these two plugins together. Can somebody help me? More information is needed? Hope you can help me Environment: Ubuntu Server 11.04 32 bits(jenkins server), Windows XP sp3 32 bits (client), Jenkins version 1.480.3, Active directory plugin version 1.33, Role strategy plugin version 1.1.2 Project: Jenkins Labels: jenkins configuration plugins active_directory, role_strategy Priority: Major Reporter: Angelo Cordova This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [parameterized-trigger] (JENKINS-10147) Add 'poll SCM' option to build step
Ladislav Toldy commented on JENKINS-10147 Add poll SCM option to build step Polling feature would be nice to have.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] (JENKINS-17882) ClearCase polling not effective for MultiSite
Pawel Josefsson commented on JENKINS-17882 ClearCase polling not effective for MultiSite Handling of epoch numbers could adress this issue. I'm not sure the problem is possible to solve in a 100% bullet proof way since ClearCase doesn't have an absolute ID of what you see in a view (regardless of dyn or snapshot). workaround is to use labels and locks which are replicated if I recall things correctly. Master build site have to create baseline of locked labels from local and remote sites to construct a config_spec and manufacture a change report, basically you won't get any help from the CC plugin someone might have better idea or tricks... Not sure if UCM works better... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [git] (JENKINS-11286) Git plugin does not timeout
Karol Depka Pradzinski stopped work on JENKINS-11286 Git plugin does not timeout Change By: Karol Depka Pradzinski (24/Jul/13 2:07 PM) Status: InProgress Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-11286) Git plugin does not timeout
Olivier Jolit commented on JENKINS-11286 Git plugin does not timeout Same problem here, for each temporary network failure we have to restart our jenkins installations. Apparently assignee has no activity since October 2011, I guess it's not "In Progress" anymore. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-11286) Git plugin does not timeout
Karol Depka Pradzinski assigned JENKINS-11286 to Unassigned Git plugin does not timeout Change By: Karol Depka Pradzinski (24/Jul/13 2:08 PM) Assignee: KarolDepkaPradzinski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-11286) Git plugin does not timeout
Karol Depka Pradzinski commented on JENKINS-11286 Git plugin does not timeout Hi Guys. Due to time constraints, I was not able to fix this bug. Earlier I forgot to change the status and un-assign 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] [core] (JENKINS-18813) AbstractProject.removeTrigger raises UnsupportedOperationException
Nathan McDonald commented on JENKINS-18813 AbstractProject.removeTrigger raises UnsupportedOperationException Pull request to address issue: https://github.com/jenkinsci/jenkins/pull/880 This just ensures the add and remote trigger methods only use Iterator#remove and Collection#add, as these are supported by DescribableList. This seemed a smaller change then adding index support to DescribableList. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-1241) force using HEAD SVN version for build
Kevin Phillips commented on JENKINS-1241 force using HEAD SVN version for build I just recently exploited yet another SVN revision number bug that is kind of tangientially related to this one. See JENKINS-18907 for details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips created JENKINS-18907 Add feature to expose the latest revision number of a checkout Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: subversion Created: 24/Jul/13 2:35 PM Description: Currently the SVN plugin only provides a single SVN revision number for any given URL (ignoring for the moment the fact you can provide multiple URLs in one configuration). Further, this one SVN revision number is the revision of the "last modification" to the repository URL provided in the configuration. This version number is sufficient in certain use cases but not in every use case. One example of this is when a given SVN URL uses externals to non-static revisions of other sources. In this case, the SVN plugin incorrectly reports the last change for the root URL and ignores the revisions of all externals. Ideally this plugin would either provide the option or expose as a secondary Jenkins property the HEAD or latest checkout / repository revision instead of / as well as the last changed revision. This would allow jobs configured with a single SVN URL with external dependencies to use the latest checkout revision as the unique ID for the checkout. Environment: Win7 x64 Jenkins v1.590.1 SVN plugin v1.48 Project: Jenkins Priority: Major Reporter: Kevin Phillips This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
kutzi commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout So to summarize/rephrase your request: you want to have the revisions of the SVN externals as environment variables? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
kutzi commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout IMO the plugin works as designed as AFAIK it returns pretty much the same, what svn info would return as 'Last Changed Rev' Externals are a different beast. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
kutzi commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout BTW: what other example than externals do you see when a single revision number is not sufficient? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout Thanks for the prompt response. I just re-phrased the description to be a bit more clear. Let me know if it makes more sense now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [port-allocator] (JENKINS-18908) Port Allocator v1.6 serializes all builds
magnayn
created JENKINS-18908
Port Allocator v1.6 serializes all builds
Issue Type:
Bug
Assignee:
ramapulavarthi
Components:
port-allocator
Created:
24/Jul/13 2:59 PM
Description:
We upgraded Port allocator (and lots of other things), and found the strange and unexpected behaviour that our builds seemed not to be running correctly on slaves.
After much digging, the finger points to the upgrade of port allocator.
The following groovy script shows why:
def q = Jenkins.getInstance().getQueue();
q.getClass().getDeclaredFields().each() { it-println "$it.name"; }
def fld = ResourceController.class.getDeclaredField("inUse");
fld.setAccessible(true);
def result = fld.get(q);
def fld2 = ResourceList.class.getDeclaredField("all");
fld2.setAccessible(true);
result.each() {
def result2 = fld2.get(it);
result2.each() { res - println "... ${res.class}"; }
}
Gives
...
... class hudson.model.Resource
... class hudson.model.Resource
Result: {standalone port SHUTDOWN_PORT(1)=W1, standalone port HTTP_PORT(1)=W1}
The first build through is blocking every other build, which just sits there for multiple hours until complete. Since they are on entirely different slaves (computers), this is particularly wrong.
We had to downgrade to 1.5 to fix this.
Project:
Jenkins
Priority:
Major
Reporter:
magnayn
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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-18909) Provide a UI way to determine why a build is waiting
magnayn created JENKINS-18909 Provide a UI way to determine why a build is waiting Issue Type: Improvement Assignee: Unassigned Components: core Created: 24/Jul/13 3:02 PM Description: Whilst diagnosing JENKINS-18908, I had to delve into reflecting out the contents of Jenkins.getInstance().getQueue(). That's quite hard to do unless you fire up Groovy console. It would be very useful to be able to see, in the UI, why a build is stuck in the ResourceController, what it's waiting for, c. Without the digging it looked very much like an environment / ssh / bug in Jenkins, but in reality it was just an errant plugin.. Project: Jenkins Priority: Major Reporter: magnayn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout Potential Use Case #1: Suppose you have an SVN module that uses one or more SVN externals to pull in dependent projects. For the sake of simplicity lets further assume that all said externals use the same repository as the root module. Finally, let also assume that you are trying to keep up to date with the bleeding edge version of each of those externals and to do so you are using the head revisions of the target branches of each of them. In this case, when you do a checkout or update you are not only updating your root folder / module to its latest revision, you are also updating all of your externals to their latest revisions. Now since this is a mixed revision checkout getting a single unique identifier for the whole checkout is problematic. However, in this particular use case you can approximate it by using the "latest revision" of the local working folder (primarily as a side effect to the fact that all externals use the same root repo and SVN revision numbers are globally unique across any given repo). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-14713) Cancel permission is granted for users having build permission
Hangsu Ma commented on JENKINS-14713 Cancel permission is granted for users having build permission The script in the link below will explicit grant Cancel permission to user with Build permission. So the configuration will be compatible after this change. https://wiki.jenkins-ci.org/x/fAAhB This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copy-project-link] (JENKINS-18910) CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins)
Gavin Goodrich created JENKINS-18910 CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins) Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: copy-project-link Created: 24/Jul/13 3:13 PM Description: In Jenkins 1.454, the copy project link plugin does not work when copying a job which is using the new 'display name' feature. You can repro with these steps: create job A and go to the configure page. click the Advanced... button next in the 'Advanced Project Options section. set the Display Name to something like 'My job' save the config page on the main job page, click the 'Copy project' link to copy it note the URL has the (internal) job name 'A' (good) enter a new job name, and click OK. At this point, you get an error message of the form: Error No such job: My job A workaround is to use the normal 'new job' approach for copying a job. Project: Jenkins Priority: Minor Reporter: Gavin Goodrich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [copy-project-link] (JENKINS-18910) CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins)
Gavin Goodrich updated JENKINS-18910 CopyProjectLink plugin: does not work with non-root url (http://hostname/jenkins) Change By: Gavin Goodrich (24/Jul/13 3:15 PM) Description: InJenkins1.454, WhenIinstalled the copyprojectlink copyprojectlink plugin doesnotworkwhencopyingajobwhichisusingthenewdisplaynamefeature.Youcanreprowiththesesteps:-createjobA and go attempted to theconfigurepage.-clicktheAdvanced...buttonnextintheAdvancedProjectOptionssection.-settheDisplayNametosomethinglikeMyjob-savetheconfigpage-onthemainjobpage,clicktheCopyprojectlinkto copy it-notetheURLhasthe(internal)jobname--A(good)-enter a newjobname,andclickOK.Atthispoint,youget projectIwasimmediatelymetwith anerror messageoftheform that : Error TherequestedURL/checkJobNamewasnotfoundonthisserver. Nosuchjob OurserverwasalreadysetupwhenIaddedjenkinsandIsimplymadeitusehttp : Myjob //hostname/jenkins Aworkaroundis Itappearsthatthispluginalwayswants to use bein the normalnewjobapproachforcopyingajob root . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18387) Jenkins sometimes fails to restart successfully
Matt Kraai commented on JENKINS-18387 Jenkins sometimes fails to restart successfully This problem also appears to have happened when I restarted Jenkins after downloading the .war file for 1.524. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout Potential Use Case #2: Suppose a site has a single SVN repository for all of their code modules and this repository is shared across many teams and projects. In such a case there are typically commits occurring frequently enough that CI builds - even those triggered my non SCM changes - are likely to get a new "latest revision" every time they do an SVN update. In such a case it is feasible to use the SVN revision number as a universal unique identifier for any particular build of any particular module. For convenience it is handy to propagate this revision number throughout the system, using it as the unique identifier for all CI artifacts (builds, tests, releases, packages, etc.) Now, in order for such a configuration to rely on the SVN revision number being unique (at least in most cases) they need to leverage the "latest" revision number of a working folder rather than the "last changed" revision - particularly for those cases when a build is manually triggered (manual triggers would do an SVN update even if there were no changes to that particular module, and the resulting "latest revision" would be updated accordingly). In such a configuration using the last change revision can not always ensure uniqueness in the build number, however so long as the frequency of modifications to the central repository is high enough (which in a large system it typically is) the "latest" revision can effectively be used. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18907) Add feature to expose the latest revision number of a checkout
Kevin Phillips commented on JENKINS-18907 Add feature to expose the latest revision number of a checkout Potential Use Case #3: Suppose again that you have a single SVN repository and you have a Jenkins configuration with 2 jobs, one dependent on the other, both stored in this single repository. Next lets suppose you have the Parameterized Trigger Plugin installed and configured so that downstream job A triggers upstream job B, passing along the Subversion revision number - to ensure the triggered instance of Job B uses the same revision as job A. Now, lets suppose you are working on a change that requires modification to both module A and B. Since both modules are in independent folders (albeit in the same repo) the commits to module A and B will generate two unique revision numbers (say revision 123 and 124 respectively). So when job A triggers (ie: via an SCM polling operation) it will first do an update to module A and set the SVN revision number. Now because the Jenkins plugin uses the last change revision it will set the revision of this execution to 123. Once complete job A will trigger job B passing revision 123 - and job B will fail... because it needs revision 124 to be successful. In this case, if Jenkins were to use the "latest revision" rather than the "last change revision", then job A would have performed its update and pulled down the latest version of itself (ie: v123) but the latest revision would actually be v124 (assuming that both changes were committed before job A started it's build - which is often the case so long as you have a reasonable "quiet period" configured for the job). Then, if this more appropriate version number were propagated to job B then it would have succeeded as expected. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [timestamper] (JENKINS-17779) Timestamps incorrect in .../console when truncated
stevengbrown commented on JENKINS-17779 Timestamps incorrect in .../console when truncated Included in Timestamper 1.5.5. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-1241) force using HEAD SVN version for build
Kevin Phillips edited a comment on JENKINS-1241 force using HEAD SVN version for build I just recently exploited yet another SVN revision number bug that is kind of tangientially related to this one. Correction - I've added a new enhancement request for the SVN plugin that may partially circumvent some of the use cases people are discussing here. See JENKINS-18907 for details. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [timestamper] (JENKINS-18826) Ability to change the timestamp format on a per-job basis
stevengbrown updated JENKINS-18826 Ability to change the timestamp format on a per-job basis Changed to an Improvement. Change By: stevengbrown (24/Jul/13 3:52 PM) Summary: ability Ability tochange thetimestamp format timestamps onaper-jobbasis Issue Type: Bug Improvement Assignee: stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [timestamper] (JENKINS-18795) Timestamper sometimes does not update its timestamps
stevengbrown assigned JENKINS-18795 to Dirk Kuypers Timestamper sometimes does not update its timestamps I suspect this is a duplicate of JENKINS-17779. Is this happening for the .../console URL or for the .../consoleFull URL? Which version of the Timestamper plugin were you running? Can you still reproduce this with Timestamper 1.5.5? Change By: stevengbrown (24/Jul/13 3:59 PM) Assignee: stevengbrown DirkKuypers This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [timestamper] (JENKINS-18795) Timestamper sometimes does not update its timestamps
Dirk Kuypers commented on JENKINS-18795 Timestamper sometimes does not update its timestamps I used TimeStamper 1.5.4. My update center does not show 1.5.5 yet Currently I am seeing small differences in console as in consoleFull: consoleFull: 03:44:50 03:44:48.354 INFO - Executing post-job class org.sonar.plugins.dbcleaner.ProjectPurgePostJob 03:44:50 03:44:48.365 INFO - - Keep one snapshot per day between 2013-06-26 and 2013-07-23 03:44:50 03:44:48.366 INFO - - Delete snapshot: 2013-07-23T09:47:44+0200 183533 03:44:50 03:44:48.456 INFO - - Delete snapshot: 2013-07-23T09:57:54+0200 185425 03:44:50 03:44:48.602 INFO - - Delete snapshot: 2013-07-23T10:08:56+0200 185710 03:44:50 03:44:48.661 INFO - - Delete snapshot: 2013-07-23T10:16:57+0200 185995 03:44:50 03:44:48.849 INFO - - Delete snapshot: 2013-07-23T10:27:11+0200 186280 console: 03:44:48 03:44:48.354 INFO - Executing post-job class org.sonar.plugins.dbcleaner.ProjectPurgePostJob 03:44:48 03:44:48.365 INFO - - Keep one snapshot per day between 2013-06-26 and 2013-07-23 03:44:49 03:44:48.366 INFO - - Delete snapshot: 2013-07-23T09:47:44+0200 183533 03:44:50 03:44:48.456 INFO - - Delete snapshot: 2013-07-23T09:57:54+0200 185425 03:44:50 03:44:48.602 INFO - - Delete snapshot: 2013-07-23T10:08:56+0200 185710 03:44:50 03:44:48.661 INFO - - Delete snapshot: 2013-07-23T10:16:57+0200 185995 03:44:50 03:44:48.849 INFO - - Delete snapshot: 2013-07-23T10:27:11+0200 186280 I will try 1.55 as soon I will see it in the update center. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18885) Parse errors with Git's TAP test suite, part 2
Sebastian Schuberth
commented on JENKINS-18885
Parse errors with Gits TAP test suite, part 2
Thanks a lot, I can confirm all issues were addressed. There are just some very minor cosmetic issues left which I do not think justify to reopening this issues. But for the sake of completeness I'll mention them here:
Regarding 2), the dot at the end of the sentence got lost: Instead of "No parse errors found." it now says "No parse errors found".
Regarding 3), I now think the choice should probably have been to use singular ("Result") because that's what Jenkins itself is using in the "Latest Test Result" link.
Regarding 4), the 404 is gone, but the table contains entries like "4 - - pretend we have a known breakage". Why are there two consecutive dashes? And the test number "4" is not very useful by itself without mentioning the test it belongs to ("t-basic.sh" in this example).
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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] [view-job-filters] (JENKINS-18911) Views should find all jobs that are discoverable OR read (currently only read)
Christian Höltje created JENKINS-18911 Views should find all jobs that are discoverable OR read (currently only read) Issue Type: Bug Assignee: Jacob Robertson Components: view-job-filters Created: 24/Jul/13 4:31 PM Description: If I use matrix or the Role Strategy plugin and set anonymous's job permissions to be "discoverable" (but not "read") then I expect the jobs to be shown in the view. What actually happens is the jobs are missing from the view. Project: Jenkins Priority: Major Reporter: Christian Höltje This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-4692) DiskUsage graph is misleading.
Kanstantsin Shautsou commented on JENKINS-4692 DiskUsage graph is misleading. So what we should plot and where? Does worskpace space for each build saved to build history? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-11546) disk usage plugin: wrong workspace size with global workspaces
Kanstantsin Shautsou commented on JENKINS-11546 disk usage plugin: wrong workspace size with global workspaces Why do you use multiple jobs on one workspace? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [disk-usage] (JENKINS-18555) Send warn email to admin before disk space exceeds configured size per server and/or per job
Kanstantsin Shautsou commented on JENKINS-18555 Send warn email to admin before disk space exceeds configured size per server and/or per job Server diskspace monitored by jenkins. Per job size is duplicated. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-1241) force using HEAD SVN version for build
Kevin Phillips commented on JENKINS-1241 force using HEAD SVN version for build NOTE Upon further review, I think the failure condition I was describing in my earlier comment may in fact be indicative of the different SVN revision numbers available in a typical working folder (e.g.: last change revision vs latest revision). As such if the other improvement request I recently created were to be implemented this problem may be avoidable. By leveraging the "latest revision" instead of the "last change revision" the @HEAD "workaround" mentioned here just may work. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Walter Kacynski created JENKINS-18912 Token macro help text is duplicated many times Issue Type: Bug Assignee: domi Components: conditional-buildstep, email-ext, run-condition, token-macro Created: 24/Jul/13 4:53 PM Description: When expanding the help sections in Editable Email notification or Conditional Run action, the sections for the Token Macro help text are duplicate many times. This makes the help almost unusable as there is a mass amount of scrolling that is required to figure out which options are available for use. Jenkins 1.510 Token Macro 1.8 Email Extension 2.30.2 Run condition .10 conditional-buildstep 1.3 Project: Jenkins Priority: Minor Reporter: Walter Kacynski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Walter Kacynski assigned JENKINS-18912 to Alex Earl Token macro help text is duplicated many times Change By: Walter Kacynski (24/Jul/13 4:55 PM) Assignee: domi AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Alex Earl commented on JENKINS-18912 Token macro help text is duplicated many times Please post a screenshot. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [warnings] (JENKINS-18913) DoxygenParser does not handle global messages following local messages correctly
Olaf Mandel created JENKINS-18913 DoxygenParser does not handle global messages following local messages correctly Issue Type: Bug Affects Versions: current Assignee: Ulli Hafner Components: warnings Created: 24/Jul/13 5:01 PM Description: When the Doxygen log contains global messages (without a filename or function name) following a local message (with a filename or a function name), then the global message is considered part of the local message. Example: /home/user/myproject/helper/SimpleTimer.h:19: Error: Unexpected character `"' error: Could not read image `/home/user/myproject/html/struct_foo_graph.png' generated by dot! The above is parsed as only one message, it should be two. Project: Jenkins Priority: Major Reporter: Olaf Mandel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Walter Kacynski updated JENKINS-18912 Token macro help text is duplicated many times Change By: Walter Kacynski (24/Jul/13 5:11 PM) Attachment: repeatingtokens.jpg This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [warnings] (JENKINS-18913) DoxygenParser does not handle global messages following local messages correctly
Olaf Mandel commented on JENKINS-18913 DoxygenParser does not handle global messages following local messages correctly Link to pull request: https://github.com/jenkinsci/warnings-plugin/pull/28 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18885) Parse errors with Git's TAP test suite, part 2
Bruno P. Kinoshita commented on JENKINS-18885 Parse errors with Gits TAP test suite, part 2 2) Could you show me an example? Here I see only a H?Parse errors/H? followed by No parse errors found, in the bottom of the TAP Test Results UI 3) Hmmm, well... haha, we can fix it again later while working on other issues 4) I think the consecutives dashes were already there, but without the test number. There was a block of code, where I was retrieving the test name. This block of code had a dumb bug, where I was doing something like return a == b ? bla bla + bla bla : bla bla... I don't recall exactly what was wrong, but it was never returning the desired value. Now it always return: TEST_NUMBER + SPACE + TEST_DESCRIPTION Being that the SPACE + TEST_DESCRIPTION part is added iff the TEST_DESCRIPTION is not blank. And TEST_DESCRIPTION is equivalent to the TAP Test Result name/description. IOW: ok 1 - How's it going? ok - STATUS 1 - TEST_NUMBER How's it going - TEST_DESCRIPTION I'm not entirely happy with this approach, since sometimes it returns simply the test_number. Feel free to file another issue for this, but I'll probably take a look on it only in 1.14, 1.15 (Friday release is 1.13). Cheers, and thanks again for the feedback! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18441) Maven 2 jobs fail (exception in MavenFingerprinter)
Jesse Glick commented on JENKINS-18441 Maven 2 jobs fail (exception in MavenFingerprinter) Right, the fix is only in a release candidate so far. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
Jesse Glick started work on JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Change By: Jesse Glick (24/Jul/13 5:32 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [maven2] (JENKINS-18178) All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex
Jesse Glick commented on JENKINS-18178 All Maven 2 builds fail with java.lang.NoSuchMethodError DigestUtils.md5Hex Bingo, that is what I needed to reproduce. Thanks @josephnelson! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Daniel S commented on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We are experiencing the same issue: FATAL: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild java.lang.RuntimeException: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild Is the any workaround or possible solution for this. We run in a continuous deployment environment and this keeps causing false failures in our tests (at least 3 - 4 a 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Walter Kacynski commented on JENKINS-18912 Token macro help text is duplicated many times The problem still occurs for with with token-macro 1.7 However, reverting to version 1.6 fixes this problem the caveat being that some of the token options are no longer displayed. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-17704) Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild
Daniel S edited a comment on JENKINS-17704 Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild We are experiencing the same issue: FATAL: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild java.lang.RuntimeException: Failed to serialize com.tikal.jenkins.plugins.multijob.MultiJobBuild#subBuilds for class com.tikal.jenkins.plugins.multijob.MultiJobBuild Is the any workaround or possible solution for this. We run in a continuous deployment environment and this keeps causing false failures in our tests (at least 3 - 4 a day). Note we are current running Jenkins MultiJob Plugin version 1.9 on Jenkins Version 1.480.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [disk-usage] (JENKINS-16856) Plugin uses hostname for links instead of ip address
Kanstantsin Shautsou commented on JENKINS-16856 Plugin uses hostname for links instead of ip address How i can reproduce this problem? Do you have any proxying/frontends/overrides? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Alex Earl commented on JENKINS-18912 Token macro help text is duplicated many times In looking at the source for run-condition and conditional-buildstep, I am not seeing where they are showing the token help. Which plugin did you take the screenshot of? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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] [conditional-buildstep] (JENKINS-18912) Token macro help text is duplicated many times
Alex Earl commented on JENKINS-18912 Token macro help text is duplicated many times Also, here is the diff between 1.6 and 1.7, nothing major there, so I'm not sure how 1.6 would not show the issue. https://github.com/jenkinsci/token-macro-plugin/compare/token-macro-1.6...token-macro-1.7 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this 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-18459) IOException: No Such File
Jesse Glick resolved JENKINS-18459 as Duplicate IOException: No Such File Change By: Jesse Glick (24/Jul/13 5:55 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] [publish-over-ssh] (JENKINS-17058) Publish over SSH plugin XML configuration cannot be read on jenkins start up.
Bryce Schober commented on JENKINS-17058 Publish over SSH plugin XML configuration cannot be read on jenkins start up. I had exactly this problem as well. I tried downgrading the plugin to 1.9, which didn't help. Then I tried upgrading from 1.509.2 LTS to 1.524 latest, and that didn't help. Then I downgraded back to 1.509.2 LTS w/ the 1.9 plugin, and that seems to be ok now... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [core] (JENKINS-18641) People View does Not Populate (makeStaplerProxy)
Shannon Kerr
commented on JENKINS-18641
People View does Not Populate (makeStaplerProxy)
I still see this in 1.524:
Includes all known “users”, including login identities which the current security realm can enumerate, as well as people mentioned in commit messages in recorded changelogs.
makeStaplerProxy('/$stapler/bound/12572177-4402-44ca-8049-11c6c791c655','b3eb158c-2164-4cee-bd76-ca4fe6ccb71c',news), display);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this 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.
