[JIRA] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds I upgrade to 1.598 and now when i click configure i get A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://IP:8080/adjuncts/19e9c96a/org/kohsuke/stapler/codemirror/lib/codemirror.js:1737 Added it here in case they are related. Also added the same message to the related bug. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26571) Job page becomes un responsive when there are a lot of builds in the queue
Arpit Gupta commented on JENKINS-26571 Job page becomes un responsive when there are a lot of builds in the queue Now when i click configure on a job i get another js un responsive message A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger, or let the script continue. Script: http://IP:8080/adjuncts/19e9c96a/org/kohsuke/stapler/codemirror/lib/codemirror.js:1737 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26739) Executors are dying since 1.597 - related to the directory layout change?
Daniel Beck commented on JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? Possible. Check the file named 'nextBuildNumber' in JENKINS_HOME/jobs/(jobname). It may be as simple as changing its contents. Anything in the logs to indicate how you got into this situation? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26742) giant memory hog
Daniel Beck resolved JENKINS-26742 as Incomplete giant memory hog This report contains not nearly enough information to investigate further. Please see https://wiki.jenkins-ci.org/display/JENKINS/How+to+report+an+issue for some instructions. Attaching a support bundle from Support Core Plugin may help. I'd also install the Monitoring Plugin and periodically check RAM usage there, as well as monitor the threads (https://wiki.jenkins-ci.org/display/JENKINS/Obtaining+a+thread+dump). Also, the JDK includes tools like jmap that allow you to analyze memory usage. Change By: Daniel Beck (02/Feb/15 10:14 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
Steven Christou assigned JENKINS-26391 to Steven Christou getAssignedLabel in MavenModule is implemented with lazy loading Change By: Steven Christou (02/Feb/15 10:13 PM) Assignee: FélixBelzunceArcos StevenChristou This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
Steven Christou updated JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Change By: Steven Christou (02/Feb/15 10:06 PM) Labels: lazy-loadingperformance Component/s: performance-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23369) Unable to check-in using bypass mode
SCM/JIRA link daemon commented on JENKINS-23369 Unable to check-in using bypass mode Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegrityCheckinTask.java http://jenkins-ci.org/commit/integrity-plugin/c8cc23f5a474418ac0879434ffdabf4a3ae1e93b Log: JENKINS-23369 Unable to check-in using bypass mode This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26743) Build record migration prints warnings for Promoted Builds promotions
Daniel Beck created JENKINS-26743 Build record migration prints warnings for Promoted Builds promotions Issue Type: Bug Assignee: Jesse Glick Components: core Created: 02/Feb/15 10:11 PM Description: On a newly set up instance of Jenkins ~1.600(ish), with Promoted Builds, the following is logged after creating a job with promotions, building, promoting, and restarting: Feb 02, 2015 10:18:56 PM jenkins.model.RunIdMigrator migrate INFO: Migrating build records in /Users/danielbeck/Jenkins-Home/jobs/jobname/promotions/Foo/builds Feb 02, 2015 10:18:56 PM jenkins.model.RunIdMigrator doMigrate WARNING: found unexpected dir lastStableBuild Feb 02, 2015 10:18:56 PM jenkins.model.RunIdMigrator doMigrate WARNING: found unexpected dir lastSuccessfulBuild Feb 02, 2015 10:18:56 PM jenkins.model.RunIdMigrator migrate These directories mentioned are actually symlinks. $ pwd /Users/danielbeck/Jenkins-Home/jobs/jobname/promotions/Foo/builds $ ls -l total 16 drwxr-xr-x+ 5 danielbeck staff 170 2 Feb 22:21 1 lrwxr-xr-x 1 danielbeck staff1 2 Feb 22:18 lastStableBuild - 1 lrwxr-xr-x 1 danielbeck staff1 2 Feb 22:18 lastSuccessfulBuild - 1 -rw-r--r--+ 1 danielbeck staff0 2 Feb 22:18 legacyIds While there seems to be no actual broken behavior, these warnings may still indicate something going wrong. Environment: Jenkins CI build from PR 1557 (Jenkins ver. 1.600-SNAPSHOT (private-01/31/2015 17:17 GMT-jenkins)) on OS X 10.9 Project: Jenkins Priority: Minor Reporter: Daniel Beck This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26743) Build record migration prints warnings for permalinks
Jesse Glick updated JENKINS-26743 Build record migration prints warnings for permalinks Not specific to Promoted Builds; true of any permalink. Harmless AFAIK but unintentional. Change By: Jesse Glick (02/Feb/15 10:22 PM) Summary: Buildrecordmigrationprintswarningsfor PromotedBuildspromotions permalinks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-24512) Add option to lock the created workspace to a host
dan tran reopened JENKINS-24512 Add option to lock the created workspace to a host Per Java API: InetAddress.getLocalHost().getHostName() returns host shortname and hostname command also returns short name. This means we need to have the client's hostname not to use fqdn format, but short format instead This is the error, I am currently seeing ERROR Client '' can only be used from host 'h.fqdn.name.com'. Change By: dan tran (02/Feb/15 10:07 PM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-26391) getAssignedLabel in MavenModule is implemented with lazy loading
Steven Christou updated JENKINS-26391 getAssignedLabel in MavenModule is implemented with lazy loading Upgrading priority to critical as something as simple as viewing the Labels build results can trigger this. Change By: Steven Christou (02/Feb/15 10:07 PM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26746) Very slow when there are many folders and projects.
Steve West created JENKINS-26746 Very slow when there are many folders and projects. Issue Type: Bug Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 03/Feb/15 12:27 AM Description: Performance of the delivery pipeline view degrades significantly when using a high number (100+) of folders and projects. A single user request will cause the Jenkins java process to tie up a full CPU. A thread dump during this situation shows usually all threads idle except those with stacks similar to the snippet below. Example thread stack: at java.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1066) at com.cloudbees.hudson.plugins.folder.Folder.getItems(Folder.java:503) at se.diabol.jenkins.pipeline.util.ProjectUtil.find(ProjectUtil.java:108) at se.diabol.jenkins.pipeline.util.ProjectUtil.find(ProjectUtil.java:110) at se.diabol.jenkins.pipeline.util.ProjectUtil.getProject(ProjectUtil.java:88) at se.diabol.jenkins.pipeline.util.BuildUtil.getUpstreamBuild(BuildUtil.java:40) at se.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:65) at se.diabol.jenkins.pipeline.util.BuildUtil.match(BuildUtil.java:83) at se.diabol.jenkins.pipeline.domain.Task.getLatestTask(Task.java:142) at se.diabol.jenkins.pipeline.domain.Stage.createLatestStage(Stage.java:188) at se.diabol.jenkins.pipeline.domain.Pipeline.createPipelineLatest(Pipeline.java:149) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getComponent(DeliveryPipelineView.java:328) at se.diabol.jenkins.pipeline.DeliveryPipelineView.getPipelines(DeliveryPipelineView.java:293) Environment: Jenkins 1.580.2, delivery-pipeline-plugin 0.8.8, build-pipeline-plugin 1.4.5, Ubuntu 12.04, Chrome, Oracle Java 1.7. Project: Jenkins Priority: Minor Reporter: Steve West This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
SCM/JIRA link daemon commented on JENKINS-26718 Cant discard promoted-builds Promotions Code changed in jenkins User: Ryan Campbell Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java http://jenkins-ci.org/commit/jenkins/327f7780133b2e6083f49686e43298af83b0dea6 Log: JENKINS-26718 Allow runs to be discarded even if their project can't be found by its fullname This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
SCM/JIRA link daemon commented on JENKINS-26718 Cant discard promoted-builds Promotions Code changed in jenkins User: Ryan Campbell Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java http://jenkins-ci.org/commit/jenkins/d6d96e14c11f0ea38ad18c3357012357eb07588d Log: Merge pull request #1557 from recampbell/JENKINS-26718 JENKINS-26718 OldDataMonitor: Handle poorly written project types Compare: https://github.com/jenkinsci/jenkins/compare/144a6da24af2...d6d96e14c11f This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26745) Uncaught ReferenceError: jobActions is not defined
Vasily Ivanov updated JENKINS-26745 Uncaught ReferenceError: jobActions is not defined Change By: Vasily Ivanov (03/Feb/15 12:27 AM) Attachment: Selection_054.png Attachment: Selection_053.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26745) Uncaught ReferenceError: jobActions is not defined
Vasily Ivanov updated JENKINS-26745 Uncaught ReferenceError: jobActions is not defined Change By: Vasily Ivanov (03/Feb/15 12:28 AM) Description: WallDisaplayfailstoloadwithJSerror:UncaughtReferenceError:jobActionsisnotdefined.Seeattachments. DowngradetoWallDisplayPluginver.0.6.27fixesit. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26746) Very slow when there are many folders and projects.
Steve West
updated JENKINS-26746
Very slow when there are many folders and projects.
Updated description to reference pull request that fixes the problem.
Change By:
Steve West
(03/Feb/15 12:47 AM)
Description:
Performanceofthedeliverypipelineviewdegradessignificantlywhenusingahighnumber(100+)offoldersandprojects.AsingleuserrequestwillcausetheJenkinsjavaprocesstotieupafullCPU.Athreaddumpduringthissituationshowsusuallyallthreadsidleexceptthosewithstackssimilartothesnippetbelow.Examplethreadstack:{code}atjava.util.Collections$UnmodifiableCollection$1.hasNext(Collections.java:1066)atcom.cloudbees.hudson.plugins.folder.Folder.getItems(Folder.java:503)atse.diabol.jenkins.pipeline.util.ProjectUtil.find(ProjectUtil.java:108)atse.diabol.jenkins.pipeline.util.ProjectUtil.find(ProjectUtil.java:110)atse.diabol.jenkins.pipeline.util.ProjectUtil.getProject(ProjectUtil.java:88)atse.diabol.jenkins.pipeline.util.BuildUtil.getUpstreamBuild(BuildUtil.java:40)atse.diabol.jenkins.pipeline.util.BuildUtil.getFirstUpstreamBuild(BuildUtil.java:65)atse.diabol.jenkins.pipeline.util.BuildUtil.match(BuildUtil.java:83)atse.diabol.jenkins.pipeline.domain.Task.getLatestTask(Task.java:142)atse.diabol.jenkins.pipeline.domain.Stage.createLatestStage(Stage.java:188)atse.diabol.jenkins.pipeline.domain.Pipeline.createPipelineLatest(Pipeline.java:149)atse.diabol.jenkins.pipeline.DeliveryPipelineView.getComponent(DeliveryPipelineView.java:328)atse.diabol.jenkins.pipeline.DeliveryPipelineView.getPipelines(DeliveryPipelineView.java:293){code}
Ihavecreated[pullrequest94|https://github.com/Diabol/delivery-pipeline-plugin/pull/94]toaddressthis.ThishasbeenverifiedinaproductionJenkinsenvironment.Also,CPUloadhasbeenshowntobesignificantlyreduced.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
dogfood commented on JENKINS-26718 Cant discard promoted-builds Promotions Integrated in jenkins_main_trunk #3962 JENKINS-26718 Allow runs to be discarded even if their project can't be found by its fullname (Revision 327f7780133b2e6083f49686e43298af83b0dea6) Result = SUCCESS ryan campbell : 327f7780133b2e6083f49686e43298af83b0dea6 Files : test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java core/src/main/java/hudson/diagnosis/OldDataMonitor.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
recampbell updated JENKINS-26718 Cant discard promoted-builds Promotions Change By: recampbell (02/Feb/15 11:51 PM) Labels: lts-candidate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22914) file transfer from slave to master failed with pipe closed
mstave commented on JENKINS-22914 file transfer from slave to master failed with pipe closed Seeing this issue on RHEL 6.5. Getting more and more frequent build failures due to this. Roughly a 6GB .tar.gz across a fast LAN. Using Jenkins 1.596. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26745) Uncaught ReferenceError: jobActions is not defined
Vasily Ivanov updated JENKINS-26745 Uncaught ReferenceError: jobActions is not defined Change By: Vasily Ivanov (03/Feb/15 12:29 AM) Environment: Jenkinsver.1.580.3WallDisplayPluginver.0.6.28 Browser:Chromever.39 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26312) Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden
Brian Carr commented on JENKINS-26312 Save/Apply buttons overlapped by footer, with SCM Sync Config Plugin, buttons are hidden Thanks for the explanation that the fix is in 1.598. We have the problem on 1.597 and eagerly await 1.598. Also, thanks for the workaround of disabling the footer. That worked very nicely for us. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26380) Deadlock between Queue and Jenkins model
Jesse Glick commented on JENKINS-26380 Deadlock between Queue and Jenkins model Made another fix in 1.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/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-26744) Support ALWAYS Continuation Condition in Multi-Phase Jobs
Christian Goetze created JENKINS-26744 Support ALWAYS Continuation Condition in Multi-Phase Jobs Issue Type: New Feature Assignee: Daniel Spilker Components: job-dsl-plugin Created: 03/Feb/15 12:09 AM Description: Jenkins UI supports it, so why not Job-DSL? Any attempt to use that results in a stack trace: 16:01:19 FATAL: Continuation Condition needs to be one of these values: SUCCESSFUL, UNSTABLE, COMPLETED 16:01:19 java.lang.IllegalArgumentException: Continuation Condition needs to be one of these values: SUCCESSFUL, UNSTABLE, COMPLETED 16:01:19 at com.google.common.base.Preconditions.checkArgument(Preconditions.java:92) 16:01:19 at com.google.common.base.Preconditions$checkArgument.call(Unknown Source) 16:01:19 at javaposse.jobdsl.dsl.helpers.step.StepContext.phase(StepContext.groovy:571) 16:01:19 at javaposse.jobdsl.dsl.helpers.step.StepContext$phase.callCurrent(Unknown Source) 16:01:19 at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:46) ... Project: Jenkins Priority: Minor Reporter: Christian Goetze This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [walldisplay-plugin] (JENKINS-26745) Uncaught ReferenceError: jobActions is not defined
Vasily Ivanov created JENKINS-26745 Uncaught ReferenceError: jobActions is not defined Issue Type: Bug Assignee: Christian Pelster Components: walldisplay-plugin Created: 03/Feb/15 12:27 AM Description: Wall Disaplay fails to load with JS error: "Uncaught ReferenceError: jobActions is not defined". See attachments. Environment: Jenkins ver. 1.580.3 Wall Display Plugin ver. 0.6.28 Project: Jenkins Priority: Blocker Reporter: Vasily Ivanov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ldap-plugin] (JENKINS-8569) DomainDnsZones UnknownHostException
Ivan Onushkin commented on JENKINS-8569 DomainDnsZones UnknownHostException Confirm on Jenkins ver. 1.598 ldap-1.8 But looks like the problem has gone after change ldap server value from "ldap.company.com" to "ldap://ldap.company.com" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Using the same workspace for different jobs is the problem. Perforce stores a 'have' list for each files synced into a workspace. The 'have' list is then used for subsequent syncs. If Perforce already thinks you have a file revision based on the 'have' list, it will not send you that file. Jenkins will use a different workspace root for each job e.g. c:\jenkins_home\job_1\ c:\jenkins_home\job_2\ If the same Perforce Workspace is used only one 'have' list is maintained, but the updates are now split across different paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala edited a comment on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not sure if it's the real issue. When I use the same workspace on different jobs they all point to the same folder. I thought this was implicit, that's why I didn't specify it. I Use the Use custom workspace option to force using the same folder. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Sebastiano Mandala commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not sure if it's the real issue. When I use the same workspace on different jobs they all point to the same folder (I thought this was implicit, that's why I didn't specify it) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multijob-plugin] (JENKINS-26738) Multi Job Plugin failed to inject variables into build
Lorelei McCollum created JENKINS-26738 Multi Job Plugin failed to inject variables into build Issue Type: Bug Assignee: Unassigned Components: multijob-plugin Created: 02/Feb/15 2:06 PM Description: Seeing this error for some of our jobs MultiJob - ERROR - Problems occurs on injecting env vars as a build step: null We have an acceptance parent mutli job that kicks off many jobs in parallel. It then copies artifacts from the triggered jobs If this step fails like the above then we cannot copy the artifacts as there is no ENV Var for the triggered build. Our pipeline then turns read and completely fails If there are more logs that I could provide please let me know Project: Jenkins Priority: Major Reporter: Lorelei McCollum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [artifactory-plugin] (JENKINS-26720) Artifactory plugin causes exception in project/configure page
Derrick Southerland commented on JENKINS-26720 Artifactory plugin causes exception in project/configure page I discovered this was caused because I had disabled the Maven Integration Plugin in Jenkins. Workaround: re-enable Maven plugin (of course). With the workaround, issue severity is greatly reduced. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26176) P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session
Paul Allen commented on JENKINS-26176 P4 plugin: Error Error occurred during the SSL handshake: invalid SSL session Thanks, for the link. I noticed a warning when I started up Jenkins, but thought that it was the Jenkins build server that needed updating. Still I have updated my local Java security. Kind regards, Paul This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [template-project-plugin] (JENKINS-24404) Environment variables not exported with Use SCM from another project
Claus Schneider commented on JENKINS-24404 Environment variables not exported with Use SCM from another project I have seen the same issue with GIT and GIT Plugin where the git trigger variables is not exported to the environment. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
aeschbacher updated JENKINS-26737 AD can not log on with email address (regression in 1.39) Change By: aeschbacher (02/Feb/15 10:43 AM) Environment: Jenkinsver1.580.3/ DebianWheezy(amd64) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26486) Workspace fails to update when Replace missing/modified files is checked
Paul Allen commented on JENKINS-26486 Workspace fails to update when Replace missing/modified files is checked There might be more clues in the Jenkins System log. 'Manage Jenkins' - 'System Log' - ' All Jenkins Logs' This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [performance-plugin] (JENKINS-26515) Concurrent builds using Performance plugin wait for post build task to be finished by the build started earlier which hasn’t finished yet
Barna Csorogi commented on JENKINS-26515 Concurrent builds using Performance plugin wait for post build task to be finished by the build started earlier which hasn’t finished yet PR submitted: https://github.com/jenkinsci/performance-plugin/pull/43 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [template-project-plugin] (JENKINS-26548) Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException
Ramakrishna Bejawar commented on JENKINS-26548 Jenkins scheduled build jobs fails randomly with java.lang.NullPointerException Ok, Thanks Daniel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [active-directory-plugin] (JENKINS-26737) AD can not log on with email address (regression in 1.39)
aeschbacher created JENKINS-26737 AD can not log on with email address (regression in 1.39) Issue Type: Bug Assignee: Unassigned Components: active-directory-plugin Created: 02/Feb/15 10:40 AM Description: When using Active Directory, connection with email (e.g. john@company.com) + Domain password fails. But: connection with AD account (e.g. ADGROUP1\johndoe) + domain password works as expected. the "Test" connection button returns "success" when using the email (e.g "Bind DN = john@company.com" and "Bind Password = domain password") This is a regression of version 1.39 (versions = 1.38 work) Environment: Debian Wheezy (amd64) Project: Jenkins Priority: Minor Reporter: aeschbacher This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-25145) Version Jenkins Configuration In Perforce
Paul Allen commented on JENKINS-25145 Version Jenkins Configuration In Perforce Do you know if this exists in a Jenkins plugin? I'm just wondering how I can access, store, view, and reload configurations. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-7139) HtmlPublisher should be able to handle wildcard paths to find multiple html files
Christoph Obexer commented on JENKINS-7139 HtmlPublisher should be able to handle wildcard paths to find multiple html files Has there been any progress on adding back pattern support? I have to deal with a directory that contains an version number and would like to simply use eg: "testresults-*/" as the directory (this would match a single directory in my case so I'm not sure if this is the correct request) Br, Christoph This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [repository-connector-plugin] (JENKINS-25620) Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1)
Dominik Bartholdi resolved JENKINS-25620 as Fixed Repository Connector Plugin failed to resolve dependency after upgrade (0.8.2 - 1.0.1) released as 1.1.0 Change By: Dominik Bartholdi (02/Feb/15 10:10 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen edited a comment on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable Using the same workspace for different jobs is the problem. Perforce stores a 'have' list entry for each file synced into a workspace. The 'have' list is then used for subsequent syncs. If Perforce already thinks you have a file revision based on the 'have' list, it will not send you that file. Jenkins will use a different workspace root for each job e.g. c:\jenkins_home\job_1\ c:\jenkins_home\job_2\ If the same Perforce Workspace is used only one 'have' list is maintained, but the updates are now split across different paths. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task-plugin] (JENKINS-26747) XUnit post-build actions cannot be saved
Alex Clifford created JENKINS-26747 XUnit post-build actions cannot be saved Issue Type: Bug Assignee: Unassigned Components: postbuild-task-plugin Created: 03/Feb/15 5:21 AM Description: Since updating a few minor versions to the latest I've noticed that when saving a Project's Configure page existing XUnist post-build actions get cleared and will not accept the values submitted. The config.xml for a working project has the following for the xunit section: xunit plugin="xunit@1.61" types PHPUnitJunitHudsonTestType patternsstesting/logs/testsuite.xml/pattern skipNoTestFilesfalse/skipNoTestFiles failIfNotNewtrue/failIfNotNew deleteOutputFilestrue/deleteOutputFiles stopProcessingIfErrortrue/stopProcessingIfError /PHPUnitJunitHudsonTestType /types thresholds org.jenkinsci.plugins.xunit.threshold.FailedThreshold unstableThreshold/unstableThreshold unstableNewThreshold/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.FailedThreshold org.jenkinsci.plugins.xunit.threshold.SkippedThreshold unstableThreshold/unstableThreshold unstableNewThreshold/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.SkippedThreshold /thresholds thresholdMode1/thresholdMode /xunit If I edit an existing project or clone our template to a new Project this section gets replaced with: xunit plugin="xunit@1.61" types/ thresholds org.jenkinsci.plugins.xunit.threshold.FailedThreshold unstableThreshold/unstableThreshold unstableNewThreshold/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.FailedThreshold org.jenkinsci.plugins.xunit.threshold.SkippedThreshold unstableThreshold/unstableThreshold unstableNewThreshold/unstableNewThreshold failureThreshold/failureThreshold failureNewThreshold/failureNewThreshold /org.jenkinsci.plugins.xunit.threshold.SkippedThreshold /thresholds thresholdMode1/thresholdMode /xunit Our builds then fail because we require the test report to be written. The workaround is to edit the correct values back into config.xml on the Jenkins master server and reload the configuration. It seems like the web interface's interaction with the REST API is breaking for this particular post-build action. Any thoughts Environment: Jenkins ver. 1.598 on Ubuntu 12.04 Project: Jenkins Labels: jenkins Priority: Major Reporter: Alex Clifford This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-26457) Ant release plugin
Aniruddha Chowdhury assigned JENKINS-26457 to Patrik Boström Ant release plugin Please look into this Change By: Aniruddha Chowdhury (03/Feb/15 3:45 AM) Assignee: PatrikBoström This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Geoff Bullen Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/f4a8d984a2b169219d6eb7187aaef49af9d9fc4c Log: Merge pull request #65 from patbos/JENKINS-20499 merged JENKINS-20499 Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/fe118c684376...f4a8d984a2b1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-20499) unable to retry job execution for failed job in build-pipeline
SCM/JIRA link daemon commented on JENKINS-20499 unable to retry job execution for failed job in build-pipeline Code changed in jenkins User: Patrik Boström Path: src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView.java src/main/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuild.java src/main/resources/au/com/centrumsystems/hudson/plugin/buildpipeline/BuildPipelineView/bpp.jelly src/test/java/au/com/centrumsystems/hudson/plugin/buildpipeline/PipelineBuildTest.java http://jenkins-ci.org/commit/build-pipeline-plugin/7a52b7429065821552f89946784853ee70a6d0dc Log: JENKINS-20499 If a job has two upstream dependencies and it has been triggered by anything except the manual trigger it will always take the first upstream job as the upstream dependency even if it is incorrect. Added check to not add a null Cause if upstream build is null. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-22066) PTC plugin has massive memory leak if scm names are not unique
SCM/JIRA link daemon commented on JENKINS-22066 PTC plugin has massive memory leak if scm names are not unique Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegritySCM/config.jelly http://jenkins-ci.org/commit/integrity-plugin/ed1cb6651df4e233778a9418c749073918b326bf Log: Integrity Configuration Names are now enforced to be unique JENKINS-25629 - Checkpoints are done against wrong project! JENKINS-22066 - PTC plugin has massive memory leak if scm names are not unique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25629) Checkpoints are done against wrong project!
SCM/JIRA link daemon commented on JENKINS-25629 Checkpoints are done against wrong project! Code changed in jenkins User: Cletus D'Souza Path: src/main/java/hudson/scm/IntegritySCM.java src/main/resources/hudson/scm/IntegritySCM/config.jelly http://jenkins-ci.org/commit/integrity-plugin/ed1cb6651df4e233778a9418c749073918b326bf Log: Integrity Configuration Names are now enforced to be unique JENKINS-25629 - Checkpoints are done against wrong project! JENKINS-22066 - PTC plugin has massive memory leak if scm names are not unique This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task-plugin] (JENKINS-26747) XUnit post-build actions cannot be saved
Alex Clifford
updated JENKINS-26747
XUnit post-build actions cannot be saved
Change By:
Alex Clifford
(03/Feb/15 5:23 AM)
Description:
SinceupdatingafewminorversionstothelatestIvenoticedthatwhensavingaProjectsConfigurepageexisting
XUnist
XUnit
post-buildactionsgetclearedandwillnotacceptthevaluessubmitted.Theconfig.xmlforaworkingprojecthasthefollowingforthe
xunit
XUnit
section:{code:xml}xunitplugin=xunit@1.61typesPHPUnitJunitHudsonTestTypepatternsstesting/logs/testsuite.xml/patternskipNoTestFilesfalse/skipNoTestFilesfailIfNotNewtrue/failIfNotNewdeleteOutputFilestrue/deleteOutputFilesstopProcessingIfErrortrue/stopProcessingIfError/PHPUnitJunitHudsonTestType/typesthresholdsorg.jenkinsci.plugins.xunit.threshold.FailedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.FailedThresholdorg.jenkinsci.plugins.xunit.threshold.SkippedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.SkippedThreshold/thresholdsthresholdMode1/thresholdMode/xunit{code}IfIeditanexistingprojectorcloneourtemplatetoanewProjectthissectiongetsreplacedwith:{code:xml}xunitplugin=xunit@1.61types/thresholdsorg.jenkinsci.plugins.xunit.threshold.FailedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.FailedThresholdorg.jenkinsci.plugins.xunit.threshold.SkippedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.SkippedThreshold/thresholdsthresholdMode1/thresholdMode/xunit{code}Ourbuildsthenfailbecausewerequirethetestreporttobewritten.Theworkaroundistoeditthecorrectvaluesbackintoconfig.xmlontheJenkinsmasterserverandreloadtheconfiguration.ItseemslikethewebinterfacesinteractionwiththeRESTAPIisbreakingforthisparticularpost-buildaction.Anythoughts
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [postbuild-task-plugin] (JENKINS-26747) XUnit post-build actions cannot be saved
Alex Clifford
updated JENKINS-26747
XUnit post-build actions cannot be saved
Change By:
Alex Clifford
(03/Feb/15 5:23 AM)
Description:
SinceupdatingafewminorversionstothelatestIvenoticedthatwhensavingaProjectsConfigurepageexistingXUnistpost-buildactionsgetclearedandwillnotacceptthevaluessubmitted.Theconfig.xmlforaworkingprojecthasthefollowingforthexunitsection:
-
{code:xml}
xunitplugin=xunit@1.61typesPHPUnitJunitHudsonTestTypepatternsstesting/logs/testsuite.xml/patternskipNoTestFilesfalse/skipNoTestFilesfailIfNotNewtrue/failIfNotNewdeleteOutputFilestrue/deleteOutputFilesstopProcessingIfErrortrue/stopProcessingIfError/PHPUnitJunitHudsonTestType/typesthresholdsorg.jenkinsci.plugins.xunit.threshold.FailedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.FailedThresholdorg.jenkinsci.plugins.xunit.threshold.SkippedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.SkippedThreshold/thresholdsthresholdMode1/thresholdMode/xunit
-
{code}
IfIeditanexistingprojectorcloneourtemplatetoanewProjectthissectiongetsreplacedwith:
-
{code:xml}
xunitplugin=xunit@1.61types/thresholdsorg.jenkinsci.plugins.xunit.threshold.FailedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.FailedThresholdorg.jenkinsci.plugins.xunit.threshold.SkippedThresholdunstableThreshold/unstableThresholdunstableNewThreshold/unstableNewThresholdfailureThreshold/failureThresholdfailureNewThreshold/failureNewThreshold/org.jenkinsci.plugins.xunit.threshold.SkippedThreshold/thresholdsthresholdMode1/thresholdMode/xunit
-
{code}
Ourbuildsthenfailbecausewerequirethetestreporttobewritten.Theworkaroundistoeditthecorrectvaluesbackintoconfig.xmlontheJenkinsmasterserverandreloadtheconfiguration.ItseemslikethewebinterfacesinteractionwiththeRESTAPIisbreakingforthisparticularpost-buildaction.Anythoughts
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-21102) Findbugs throws FileNotFoundException
seanf reopened JENKINS-21102 Findbugs throws FileNotFoundException I have been getting this error too, for quite some time. I suspect the real clue is in the nested FileNotFoundException, because org/apache/lucene/util/AttributeSource.java is not part of this project, Lucene is just used as a dependency. Grepping through my logs, it sometimes happens with a different file, which again does not exist in this project, only in a dependency. findbugs-maven-plugin:2.5.2 Jenkins ver. 1.580.1 FindBugs Plugin 4.57 [FINDBUGS] Can't copy source file: source=org/apache/lucene/util/AttributeSource.java, destination=1fd2cf2f.tmp java.io.IOException: Failed to copy org/apache/lucene/util/AttributeSource.java to /var/lib/jenkins/jobs/zanata-server-github-pull-requests/modules/org.zanata$zanata-model/builds/2015-02-03_16-13-21/workspace-files/1fd2cf2f.tmp at hudson.FilePath.copyTo(FilePath.java:1905) at hudson.plugins.analysis.core.HealthAwareReporter.copyFilesWithAnnotationsToBuildFolder(HealthAwareReporter.java:468) at hudson.plugins.analysis.core.HealthAwareReporter.postExecute(HealthAwareReporter.java:317) at hudson.maven.Maven3Builder$MavenExecutionListener.recordMojoEnded(Maven3Builder.java:634) at hudson.maven.Maven3Builder$MavenExecutionListener.mojoSucceeded(Maven3Builder.java:615) 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.MojoExecutor.executeForkedExecutions(MojoExecutor.java:365) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:199) 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:117) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.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:178) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.maven.Maven3Builder.call(Maven3Builder.java:136) at hudson.maven.Maven3Builder.call(Maven3Builder.java:71) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:262) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) Caused by: java.io.FileNotFoundException: org/apache/lucene/util/AttributeSource.java (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:146) at
[JIRA] [p4-plugin] (JENKINS-26506) Auto cleanup and sync as well as sync only are not reliable
Paul Allen commented on JENKINS-26506 Auto cleanup and sync as well as sync only are not reliable I am not familiar with a custom workspace option to point Jenkins jobs to the same folder. Is this under the 'Advanced Project Options' - 'Use custom workspace' option? I'm not sure why you would need to do this and it seems dangerous to overlap directories. Could you provide some detail on your use-case, there may be a simpler alternative. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26741) Copy Artifact plugin should allow for not failling build as an option
Lorelei McCollum created JENKINS-26741 Copy Artifact plugin should allow for not failling build as an option Issue Type: Bug Assignee: Unassigned Components: copyartifact-plugin Created: 02/Feb/15 3:45 PM Description: We run a lot of jobs in a multi job so that they run in parallel and then when that phase is done we copy artifacts from each of them back to that build The issue I am hitting is the Config space limit for a job. This is because I have to wrap the copy artifact in a conditional statement so that if the env var is set and not FAILED then copy the artifacts I would rather just say if copy artifacts fail ignore and keep going on and don't fail the build Currently if the copy artifacts step fails the build stops and fails and then nothing else happens Project: Jenkins Priority: Minor Reporter: Lorelei McCollum This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
Jesse Glick updated JENKINS-26718 Cant discard promoted-builds Promotions Change By: Jesse Glick (02/Feb/15 3:23 PM) Summary: Cantdiscardpromoted- buids builds Promotions This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26739) Executors are dying since 1.597 - related to the directory layout change?
Thomas Müller created JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Feb/15 2:34 PM Description: Thread has died java.lang.IllegalStateException: cannot create a build with number 8558 since that (or higher) is already in use among 8099, 8312, 8317, 8318, 8319, 8320, 8321, 8322, 8323, 8326, 8328, 8329, 8330, 8331, 8333, 8335, 8336, 8338, 8340, 8341, 8348, 8351, 8355, 8358, 8360, 8361, 8362, 8363, 8370, 8371, 8380, 8381, 8386, 8387, 8394, 8397, 8398, 8399, 8400, 8401, 8402, 8403, 8404, 8405, 8406, 8407, 8408, 8409, 8418, 8419, 8420, 8421, 8422, 8423, 8424, 8426, 8428, 8435, 8436, 8440, 8441, 8442, 8484, 8487, 8488, 8489, 8490, 8491, 8492, 8493, 8495, 8497, 8498, 8499, 8500, 8501, 8508, 8512, 8513, 8514, 8515, 8522, 8523, 8524, 8526, 8527, 8528, 8529, 8530, 8531, 8535, 8536, 8537, 8545, 8546, 8549, 8550, 8552, 8554, 8555, 8556, 8557, 8560, 8563 at jenkins.model.lazy.AbstractLazyLoadRunMap.proposeNewNumber(AbstractLazyLoadRunMap.java:361) at hudson.model.RunMap.put(RunMap.java:189) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:284) at hudson.matrix.MatrixConfiguration.newBuild(MatrixConfiguration.java:74) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:1205) at hudson.model.AbstractProject.createExecutable(AbstractProject.java:144) at hudson.model.Executor.run(Executor.java:213) more info Project: Jenkins Priority: Critical Reporter: Thomas Müller This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [parameterized-remote-trigger-plugin] (JENKINS-22231) Allow parameterized remote trigger to be a post-build action
Derrik Ammons commented on JENKINS-22231 Allow parameterized remote trigger to be a post-build action I, too, would like to use this feature. When will this be implemented? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26739) Executors are dying since 1.597 - related to the directory layout change?
Thomas Müller updated JENKINS-26739 Executors are dying since 1.597 - related to the directory layout change? Change By: Thomas Müller (02/Feb/15 2:36 PM) Environment: masteronLinux-2-3Linuxslaveswith10executors-1windowsslavewithoneexecutor.Problemonlyshowsuponlinuxslaveswherewehavethehighestload-upto30paralleljobs This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
Jesse Glick started work on JENKINS-26718 Cant discard promoted-builds Promotions Change By: Jesse Glick (02/Feb/15 3:24 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-26740) Failed to set Jenkins Identity header on email. java.lang.NullPointerException
podskalsky created JENKINS-26740 Failed to set Jenkins Identity header on email. java.lang.NullPointerException Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 02/Feb/15 3:24 PM Description: For example ... We had some faild builds. After fixes the build was now OK but the mail notification is failing !!! ERROR: Failed to set Jenkins Identity header on email. java.lang.NullPointerException at org.jenkinsci.main.modules.instance_identity.InstanceIdentity.get(InstanceIdentity.java:126) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.setJenkinsInstanceIdent(MimeMessageBuilder.java:184) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.buildMimeMessage(MimeMessageBuilder.java:162) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:391) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:201) at hudson.tasks.MailSender.createMail(MailSender.java:192) at hudson.tasks.MailSender.run(MailSender.java:107) at hudson.tasks.Mailer.perform(Mailer.java:141) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) ERROR: Publisher hudson.tasks.Mailer aborted due to exception java.lang.NullPointerException at javax.mail.internet.InternetAddress.toString(InternetAddress.java:461) at javax.mail.internet.InternetAddress.toString(InternetAddress.java:426) at javax.mail.internet.MimeMessage.setAddressHeader(MimeMessage.java:707) at javax.mail.internet.MimeMessage.setReplyTo(MimeMessage.java:694) at jenkins.plugins.mailer.tasks.MimeMessageBuilder.buildMimeMessage(MimeMessageBuilder.java:175) at hudson.tasks.MailSender.createEmptyMail(MailSender.java:391) at hudson.tasks.MailSender.createBackToNormalMail(MailSender.java:201) at hudson.tasks.MailSender.createMail(MailSender.java:192) at hudson.tasks.MailSender.run(MailSender.java:107) at hudson.tasks.Mailer.perform(Mailer.java:141) at hudson.tasks.BuildStepCompatibilityLayer.perform(BuildStepCompatibilityLayer.java:74) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1743) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Finished: FAILURE Workaround: downgrade to Mailer 1.12 Environment: Jenkins ver. 1.597 Mailer 1.13 (latest) Project: Jenkins Priority: Blocker Reporter: podskalsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For
[JIRA] [integrity-plugin] (JENKINS-25228) Using the integrity-plugin together with concurrent builds causes SQL Exceptions
Cletus DSouza commented on JENKINS-25228 Using the integrity-plugin together with concurrent builds causes SQL Exceptions JENKINS-25450 is also the same issue really. Closed out the other two duplicates in favor to track against this one. Looks like the 10.6/7 elimination of Derby is not going to be a reality. I will have to figure out how best to implement DB pool with just one instance for all jobs. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25629) Checkpoints are done against wrong project!
Cletus DSouza resolved JENKINS-25629 as Fixed Checkpoints are done against wrong project! I've implemented a uniqueness check to ensure Configuration Names are unique. This should not be happening anymore. Change By: Cletus DSouza (03/Feb/15 7:44 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-22066) PTC plugin has massive memory leak if scm names are not unique
Cletus DSouza resolved JENKINS-22066 as Fixed PTC plugin has massive memory leak if scm names are not unique Configuration Names have to be unique going forward. Hopefully this resolves your issue. Change By: Cletus DSouza (03/Feb/15 7:45 AM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23369) Unable to check-in using bypass mode
Cletus DSouza resolved JENKINS-23369 as Fixed Unable to check-in using bypass mode Ok, its fixed now. Change By: Cletus DSouza (03/Feb/15 7:45 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/d/optout.
[JIRA] [findbugs-plugin] (JENKINS-21102) Findbugs throws FileNotFoundException
Ulli Hafner commented on JENKINS-21102 Findbugs throws FileNotFoundException If the file is not there then it is clear why the file could not be copied... In the original report the file should be present in the workspace. So what is your expectation? Currently it is just a log message, should it be suppressed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-26016) PTC Plugin: Request to add postbuild action to label a project
Cletus DSouza commented on JENKINS-26016 PTC Plugin: Request to add postbuild action to label a project There's automatic labeling of the pre-build checkpoint after the build is done. Are you saying that doesn't work? Thanks! Cletus This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-25450) Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job).
Cletus DSouza resolved JENKINS-25450 as Duplicate Unexpected behavior of Jenkins Integrity plugin after SQL Exception inside plugin (no error returned to build job). This is another duplicate of JENKINS-25228 Change By: Cletus DSouza (03/Feb/15 7:50 AM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-14675) Schema 'DBUSER' does not exist error in integrity plugin
Cletus DSouza resolved JENKINS-14675 as Duplicate Schema DBUSER does not exist error in integrity plugin Closing this out as it is a duplicate of JENKINS-25228 Change By: Cletus DSouza (03/Feb/15 7:48 AM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-26514) Deadlock adding Docker node
SCM/JIRA link daemon commented on JENKINS-26514 Deadlock adding Docker node Code changed in jenkins User: magnayn Path: src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java http://jenkins-ci.org/commit/docker-plugin/bc399883dc958f9be723c020c6f0ed074d373acd Log: Merge pull request #141 from bschelberg/JENKINS-26514 JENKINS-26514 Lock Queue before calling Jenkins.addNode() Compare: https://github.com/jenkinsci/docker-plugin/compare/2d654695ee7a...bc399883dc95 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26741) Copy Artifact plugin should allow for not failling build as an option
Lorelei McCollum commented on JENKINS-26741 Copy Artifact plugin should allow for not failling build as an option Actually I think we can close this, the help didn't work on the optional check box for me, but after reading more on it, I think optional will solve my need! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26742) giant memory hog
Pablob P created JENKINS-26742 giant memory hog Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Feb/15 4:15 PM Description: I start manually jenkins using a bat file this way: cd C:\Program Files (x86)\Jenkins start /LOW java -jar jenkins.war after a day I see that java process takes 2BG of ram. I don't do much with jenkins, all it does it tries two svn repos every minute for updates and runs my script that does the update/revert/build. If I go to installed plugins tab I see these plugins with "uninstall" button. I assume that these were installed by me, right? build-name-setter GIT client plugin GIT plugin instant-messaging plugin MapDB API Plugin SCM API Plugin Skype notifier plugin Token Macro Plugin Environment: Win 2008 server Project: Jenkins Labels: memory memory-leak Priority: Major Reporter: Pablob P This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [docker-plugin] (JENKINS-26514) Deadlock adding Docker node
SCM/JIRA link daemon commented on JENKINS-26514 Deadlock adding Docker node Code changed in jenkins User: Bernie Schelberg Path: src/main/java/com/nirima/jenkins/plugins/docker/DockerCloud.java http://jenkins-ci.org/commit/docker-plugin/924390064df7a35cddc2a1d27e4ac3fe85add9f7 Log: JENKINS-26514 Lock Queue before calling Jenkins.addNode() This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26699) Workflow plugin silently breaks regular Groovy maps
Jesse Glick commented on JENKINS-26699 Workflow plugin silently breaks regular Groovy maps Someone also noted that some loop idioms use for example java.util.ArrayList$Itr, which is not Serializable, and so cannot be used in a workflow. I thought this was filed in JIRA but I do not see it now. Whether it is even fixable is another question; I can only imagine fixing it by making reference to JRE implementation details, which is not robust. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [p4-plugin] (JENKINS-24512) Add option to lock the created workspace to a host
dan tran commented on JENKINS-24512 Add option to lock the created workspace to a host I am seeing inconsistency in the hostname. For example, p4jenkins sets to full FQDN name of a slave, however at the save the command 'hostname' which is equivalent to InetAddress.getLocalHost().getHostName() return short name. Did you configure the client's at the master or at the slave node?? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ant-plugin] (JENKINS-26457) Ant release plugin
Aniruddha Chowdhury updated JENKINS-26457 Ant release plugin Change By: Aniruddha Chowdhury (03/Feb/15 3:43 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [versionnumber-plugin] (JENKINS-26729) Endless loop when evaluating environment variables
Jason W
updated JENKINS-26729
Endless loop when evaluating environment variables
Change By:
Jason W
(02/Feb/15 7:58 AM)
Description:
h5.RecreationHave2jobs:Job1triggersJob2usingtheTrigger/callbuildsonotherprojectsUsesPredefinedparameter:test_loop=${test_loop}Job2usesCreateaformattedversionnumberwhere:EnvironmentVariableName:test_loopVersionNumberFormatString:${test_loop}h5.OutcomeThiscausestheJob2tobestuckinanendlessloopastest_loopkeepsgettingtranslatedinto${test_loop}andtriestobetranslatedagainandagain...threadDumplooksasfollows:{code}Executor#0formaster:executingtest_endless_loop#5Executor#0formaster:executingtest_endless_loop#5Id=116Group=mainRUNNABLE atorg.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.formatVersionNumber(VersionNumberBuilder.java:341) atorg.jvnet.hudson.tools.versionnumber.VersionNumberBuilder.setUp(VersionNumberBuilder.java:364)...{code}Istumbledonthisbyaccidentandthisconfigurationshouldbeavoided,butstillit
cause
causes
ajobtobestuckinanendlessloopwhichcouldnotbestopped.Stoppingitwasonlybyrestartingtheserver.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Michael Shmulevich created JENKINS-26734 Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 02/Feb/15 8:12 AM Description: After an upgrade from 1.581 to 1.596 all the jobs that had a Multiple SCM configuration of Git/SVN or SVN/SVN stopped working, showing the following error in their console log: Updating [SVN URL removed] at revision '2015-02-02T08:51:12.932 +0100' At revision 110220 FATAL: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.scm.SVNRevisionState java.lang.ClassCastException: org.jenkinsci.plugins.multiplescms.MultiSCMRevisionState cannot be cast to hudson.scm.SVNRevisionState at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) at hudson.scm.SCM.checkout(SCM.java:484) at org.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) at hudson.model.AbstractProject.checkout(AbstractProject.java:1270) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) at com.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) at hudson.model.Run.execute(Run.java:1718) at com.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) At first, I thought the Multiple SCM plugin was the one to blame, but downgrading that one didn't provide any result. Unfortunately, the SVN client is a pinned plug-in, thus not easy to just upgrade. However, after un-pinning Subversion plugin and downgrading to 2.4.5, the SCM builds are working again. Environment: Jenkins 1.596 Project: Jenkins Priority: Major Reporter: Michael Shmulevich This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26015) Layout broken since 1.593
Benjamin Dewez commented on JENKINS-26015 Layout broken since 1.593 @BaskaranD No this screenshot seems to be good. This issue is about this screen : ScreenShot001.jpg ( The first one ). I have the main body that is display below the rest of the page in place of the normal place. But this CSS bug does not appear on any browser. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks commented on JENKINS-26612 svn: absolutely unacceptably SLOW I think I took them with 2.5, otherwise they would be useless. However, I switched between versions many times and the day was quite long, so it is possible that I did something wrong. I will take some new crash dumps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Michael Shmulevich
updated JENKINS-26734
Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Change By:
Michael Shmulevich
(02/Feb/15 8:36 AM)
Description:
Afteranupgradefrom1.581to1.596allthejobsthathadaMultipleSCMconfigurationofGit/SVNorSVN/SVNstoppedworking,showingthefollowingerrorintheirconsolelog:{noformat}Updating[SVNURLremoved]atrevision2015-02-02T08:51:12.932+0100Atrevision110220FATAL:org.jenkinsci.plugins.multiplescms.MultiSCMRevisionStatecannotbecasttohudson.scm.SVNRevisionStatejava.lang.ClassCastException:org.jenkinsci.plugins.multiplescms.MultiSCMRevisionStatecannotbecasttohudson.scm.SVNRevisionState athudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725) athudson.scm.SubversionSCM.checkout(SubversionSCM.java:860) athudson.scm.SCM.checkout(SCM.java:484) atorg.jenkinsci.plugins.multiplescms.MultiSCM.checkout(MultiSCM.java:117) athudson.model.AbstractProject.checkout(AbstractProject.java:1270) athudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:609) atjenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) athudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:531) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild$MultiJobRunnerImpl.run(MultiJobBuild.java:134) athudson.model.Run.execute(Run.java:1718) atcom.tikal.jenkins.plugins.multijob.MultiJobBuild.run(MultiJobBuild.java:73) athudson.model.ResourceController.execute(ResourceController.java:89) athudson.model.Executor.run(Executor.java:240){noformat}Atfirst,Ithoughtthe{{MultipleSCM}}pluginwastheonetoblame,butdowngradingthatonedidntprovideanyresult.Unfortunately,theSVNclientisa_pinned_plug-in,thusnoteasytojustupgrade.However,afterun-pinning{{Subversionplugin}}anddowngradingto2.4.5,the
SCM
{{MultipleSCMs}}
buildsareworkingagain.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups Jenkins Issues group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26612) svn: absolutely unacceptably SLOW
Tim Jaacks updated JENKINS-26612 svn: absolutely unacceptably SLOW OK, this time the line number is different, so obviously the dumps from friday night indeed were taken with the wrong version. This time it's definitely 2.5. Hope it helps. Change By: Tim Jaacks (02/Feb/15 8:52 AM) Attachment: jstack.4426.094557.124344340 Attachment: jstack.4426.094626.340372601 Attachment: jstack.4426.094622.376370885 Attachment: jstack.4426.094606.575594368 Attachment: jstack.4426.094634.612320840 Attachment: jstack.4426.094618.646872610 Attachment: jstack.4426.094638.649047043 Attachment: jstack.4426.094630.661041175 Attachment: jstack.4426.094610.707042864 Attachment: jstack.4426.094614.810515707 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [coverity-plugin] (JENKINS-26736) [COMMAND LINE ERROR] Extra token error in the cov-commit-defects and cov-analyze
Bakkiaraj Murugesan created JENKINS-26736 [COMMAND LINE ERROR] Extra token error in the cov-commit-defects and cov-analyze Issue Type: Bug Assignee: Ken Dang Components: coverity-plugin Created: 02/Feb/15 8:52 AM Description: I have upgraded to Coverity plugin 1.5.0. After the upgrade coverity builds started failing. I have following extra options in the job config page, Additional cov-analyze-java arguments: --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa space_here Additional cov-commit-defects arguments: --description "Test SW Commit" --ticker-mode none Build failed with following build error, Coverity cmd so far is: /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze, --dir, /home/JENKINS_HOME/coverity/temp-5110247036894018110.tmp, --cpp, --all, --ticker-mode, none, , --enable-constraint-fpp, , --enable-callgraph-metrics, --force, --hfa cov_infra_sw_Build $ /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze --dir /home/JENKINS_HOME/coverity/temp-5110247036894018110.tmp --cpp --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa Coverity Static Analysis version 7.5.0 on Linux 3.17.7-200.fc20.x86_64 x86_64 Internal version numbers: b5b2c6e5a6 p-gilroy-push-19219.652 COMMAND LINE ERROR Extra token '' at the end of the command line. Please only specify one value for each option and ensure that all options are preceded with the '' or '-' characters. Specify --help for assistance. Coverity /opt/cov-analysis-linux64-7.5.0/bin/cov-analyze returned 2, aborting... $ /opt/cov-analysis-linux64-7.5.0/bin/cov-commit-defects --dir /home/JENKINS_HOME/coverity/temp-8006006841231009923.tmp --host test.dom.com --port 6060 --stream test_sw --user test --description "Test SW Commit" --ticker-mode none COMMAND LINE ERROR Extra token 'SW' at the end of the command line. Please only specify one value for each option and ensure that all options are preceded with the '' or '-' characters. Specify --help for assistance. Coverity cov-commit-defects returned 2, aborting... When I ran the coverity commands manually, its working fine. Looks like some problem in parsing the command line arguments. To solve the issue, I found the following work around, I have changed job config like, Additional cov-analyze-java arguments: --all --ticker-mode none --enable-constraint-fpp --enable-callgraph-metrics --force --hfa Additional cov-commit-defects arguments: --description "Test_SW_Commit" --ticker-mode none Now build is working fine. Environment: Jenkins 1.598, Manual installation, Linux Cent OS 6.x, Sun JVM 1.7.x Coverity Analysis linux64 7.5.0 Project: Jenkins Labels: plugin coverity Priority: Critical Reporter: Bakkiaraj Murugesan This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
