[JIRA] [jacoco] (JENKINS-23579) jacoco 1.0.14 & 1.0.15 failed in analyziing some class file produced by jacoco-maven-plugin:0.6.2.201302030002
centic resolved JENKINS-23579 as Fixed jacoco 1.0.14 & 1.0.15 failed in analyziing some class file produced by jacoco-maven-plugin:0.6.2.201302030002 Resolvingthis based on the comment, please reopen if you still see this error with version 0.16 Change By: centic (02/Jul/14 7:07 AM) Status: Open Resolved Assignee: Ognjen Bubalo centic 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] [jacoco] (JENKINS-23579) jacoco 1.0.14 & 1.0.15 failed in analyziing some class file produced by jacoco-maven-plugin:0.6.2.201302030002
centic edited a comment on JENKINS-23579 jacoco 1.0.14 & 1.0.15 failed in analyziing some class file produced by jacoco-maven-plugin:0.6.2.201302030002 Resolvingthis based on the comment, please reopen if you still see this error with version 1.0.16 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Johannes Schmieder updated JENKINS-23645 Archiving artifacts does not preserve timestamps if filter is ** Change By: Johannes Schmieder (02/Jul/14 7:19 AM) Description: The timestamps of artifacts are not preserved when archiving artifacts, OR performing a CopyArtifact operation if the artifact filter is set to "**".For example the filter "myfolder\**" will preserve timestamps.We use mutiple chained Jenkins jobs to perform a build. If the timestamps of dependency files in the artifact passed between jobs is not preserved, then subsequent jobs will fail. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-23645) Archiving artifacts does not preserve timestamps if filter is **
Johannes Schmieder
updated JENKINS-23645
Archiving artifacts does not preserve timestamps if filter is **
Change By:
Johannes Schmieder
(02/Jul/14 7:24 AM)
Description:
The timestamps of artifacts are not preserved when archiving artifacts, OR performing a CopyArtifact operation if the artifact filter is set to "**".For example the filter
<
{
code
>
}
"myfolder\**"
{
code
>
}
will preserve timestamps.We use mutiple chained Jenkins jobs to perform a build. If the timestamps of dependency files in the artifact passed between jobs is not preserved, then subsequent jobs will fail.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [logging] (JENKINS-23649) The logging plugin should warn the user when a changelog is empty
Mads Nielsen created JENKINS-23649 The logging plugin should warn the user when a changelog is empty Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: logging Created: 02/Jul/14 7:34 AM Project: Jenkins Priority: Minor Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [logging] (JENKINS-23649) The logging plugin should warn the user when a changelog is empty (case 11552)
Mads Nielsen updated JENKINS-23649 The logging plugin should warn the user when a changelog is empty (case 11552) Change By: Mads Nielsen (02/Jul/14 7:38 AM) Summary: The logging plugin should warn the user when a changelog is empty ( case11552 case 11552 ) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 Just installed 1.2.3.1 Build still fail when "Use Maven Artifacts as Scan Path" is selected : 00:04:03.707 [DependencyCheck] OWASP Dependency-Check Plugin v1.2.3.1 00:04:03.719 [DependencyCheck] Executing Dependency-Check analysis with the following options: 00:04:03.719 [DependencyCheck] -name = jenkins-v1-plugin 00:04:03.719 [DependencyCheck] -scanPath = ERROR - PATH NOT SPECIFIED OR INVALID. 00:04:03.719 [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace 00:04:03.719 [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check-data 00:04:03.719 [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check.log 00:04:03.719 [DependencyCheck] -dataMirroringType = NIST CPE/CVE 00:04:03.719 [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-%d.xml 00:04:03.719 [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-%d.xml 00:04:03.719 [DependencyCheck] -useMavenArtifactsScanPath = true 00:04:03.719 [DependencyCheck] -jarAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -_javascript_AnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -archiveAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -assemblyAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nuspecAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nexusAnalyzerEnabled = false 00:04:03.719 [DependencyCheck] -showEvidence = false 00:04:03.719 [DependencyCheck] -format = XML 00:04:03.719 [DependencyCheck] -autoUpdate = true 00:04:03.719 [DependencyCheck] The scan path(s) specified are not valid. Please specify a valid path to scan. 00:04:03.720 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure 00:04:03.802 [DependencyCheck] Skipping publisher since build result is FAILURE For second job, Maven job too, I could add DC in post-build but "Use Maven Artifacts as Scan Path" is not available anymore. Screenshot attached, and issue 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] [logging] (JENKINS-23649) The logging plugin should warn the user when a changelog is empty (case11552)
Mads Nielsen updated JENKINS-23649 The logging plugin should warn the user when a changelog is empty (case11552) Change By: Mads Nielsen (02/Jul/14 7:38 AM) Summary: The logging plugin should warn the user when a changelog is empty (case11552) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez reopened JENKINS-23643 Regressions with 1.2.3 1.2.3.1 didn't fix problems Change By: Henri Gomez (02/Jul/14 7:40 AM) 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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez updated JENKINS-23643 Regressions with 1.2.3 Change By: Henri Gomez (02/Jul/14 7:40 AM) Attachment: Screenshot-20140702-093925.png Attachment: Screenshot-20140702-093904.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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez edited a comment on JENKINS-23643 Regressions with 1.2.3 Just installed 1.2.3.1 Build still fail when "Use Maven Artifacts as Scan Path" is selected : 00:04:03.707 [DependencyCheck] OWASP Dependency-Check Plugin v1.2.3.1 00:04:03.719 [DependencyCheck] Executing Dependency-Check analysis with the following options: 00:04:03.719 [DependencyCheck] -name = jenkins-v1-plugin 00:04:03.719 [DependencyCheck] -scanPath = ERROR - PATH NOT SPECIFIED OR INVALID. 00:04:03.719 [DependencyCheck] -outputDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace 00:04:03.719 [DependencyCheck] -dataDirectory = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check-data 00:04:03.719 [DependencyCheck] -verboseLogFile = /var/lib/mycorp/cijenkins/jobs/jenkins-v1-plugin/workspace/dependency-check.log 00:04:03.719 [DependencyCheck] -dataMirroringType = NIST CPE/CVE 00:04:03.719 [DependencyCheck] -cveUrl12Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl20Modified = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-modified.xml 00:04:03.719 [DependencyCheck] -cveUrl12Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-%d.xml 00:04:03.719 [DependencyCheck] -cveUrl20Base = http://swf-storage.lab1.lab.ptx.mycorp.int/downloads/nist/nvdcve-2.0-%d.xml 00:04:03.719 [DependencyCheck] -useMavenArtifactsScanPath = true 00:04:03.719 [DependencyCheck] -jarAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -_javascript_AnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -archiveAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -assemblyAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nuspecAnalyzerEnabled = true 00:04:03.719 [DependencyCheck] -nexusAnalyzerEnabled = false 00:04:03.719 [DependencyCheck] -showEvidence = false 00:04:03.719 [DependencyCheck] -format = XML 00:04:03.719 [DependencyCheck] -autoUpdate = true 00:04:03.719 [DependencyCheck] The scan path(s) specified are not valid. Please specify a valid path to scan. 00:04:03.720 Build step 'Invoke OWASP Dependency-Check analysis' marked build as failure 00:04:03.802 [DependencyCheck] Skipping publisher since build result is FAILURE For second job, Maven job too, I could add DC in post-build but "Use Maven Artifacts as Scan Path" is not available anymore. Screenshot attached, and issue reopened in post-step : in pre-step : This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [logging] (JENKINS-23649) The logging plugin should warn the user when a changelog is empty (case 11553)
Mads Nielsen updated JENKINS-23649 The logging plugin should warn the user when a changelog is empty (case 11553) Change By: Mads Nielsen (02/Jul/14 8:01 AM) Summary: The logging plugin should warn the user when a changelog is empty (case 11552 11553 ) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23191) ReverseBuildTrigger.threshold not consistently saved
Christian Langmann commented on JENKINS-23191 ReverseBuildTrigger.threshold not consistently saved It seems there is still a problem, don't know whether it is the same: Previously the "build after other project"-trigger was a mirror of the post-build-action "Build other project". Now, you can alter the "Build other project" (e.g. removing job C from PBA of job B) and the trigger in job C is not updated. On the other hand changes in trigger of job C are not reflected in job B anymore. Actually the settings in job C have no effect, ie. when no PBA is configured in B, job C is never triggered, whatever it's configuration is. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [plot] (JENKINS-4934) Plot data is retained for deleted builds
Oliver Gondža commented on JENKINS-4934 Plot data is retained for deleted builds Brian Smith: I agree, https://issues.jenkins-ci.org/browse/JENKINS-22575 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23191) ReverseBuildTrigger.threshold not consistently saved
Daniel Beck commented on JENKINS-23191 ReverseBuildTrigger.threshold not consistently saved Christian: This is a deliberate, documented change. Quoting the changelog for 1.560: The “upstream pseudo trigger” was also removed in favor of a true trigger configured on the downstream project; you may use either the post-build action or the trigger according to where you want this configuration stored, and who is authorized to change 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] [core] (JENKINS-23191) ReverseBuildTrigger.threshold not consistently saved
Daniel Beck edited a comment on JENKINS-23191 ReverseBuildTrigger.threshold not consistently saved Christian: This is a deliberate, documented change. Quoting the changelog for 1.560: The “upstream pseudo trigger” was also removed in favor of a true trigger configured on the downstream project; you may use either the post-build action or the trigger according to where you want this configuration stored, and who is authorized to change it. Actually the settings in job C have no effect, ie. when no PBA is configured in B, job C is never triggered, whatever it's configuration is. This could be a legitimate bug. Could you provide complete and detailed steps to reproduce this on a test instance with default plugins? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [plot] (JENKINS-22575) Plot loses data points for expired jobs
Oliver Gondža commented on JENKINS-22575 Plot loses data points for expired jobs AFAICT the data in csv files are not discarded, just not shown. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-23650) artifactoryPublish fails with Gradle 2.0
Jochen Kemnade created JENKINS-23650 artifactoryPublish fails with Gradle 2.0 Issue Type: Bug Affects Versions: current Assignee: yossis Components: artifactory Created: 02/Jul/14 8:22 AM Description: The artifactoryPublish task fails in a project that uses Gradle(w) 2.0: FAILURE: Build failed with an exception. * What went wrong: Execution failed for task ':artifactoryPublish'. > org/apache/ivy/core/IvyPatternHelper * Try: Run with --debug option to get more log output. * Exception is: org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':artifactoryPublish'. at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46) at org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35) at org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:64) at org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58) at org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:42) at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52) at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53) at org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43) at org.gradle.api.internal.AbstractTask.executeWithoutThrowingTaskFailure(AbstractTask.java:296) at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.executeTask(AbstractTaskPlanExecutor.java:79) at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.processTask(AbstractTaskPlanExecutor.java:63) at org.gradle.execution.taskgraph.AbstractTaskPlanExecutor$TaskExecutorWorker.run(AbstractTaskPlanExecutor.java:51) at org.gradle.internal.concurrent.DefaultExecutorFactory$StoppableExecutorImpl$1.run(DefaultExecutorFactory.java:64) Caused by: java.lang.NoClassDefFoundError: org/apache/ivy/core/IvyPatternHelper at org.jfrog.gradle.plugin.artifactory.task.BuildInfoConfigurationsTask.gradleDeployDetails(BuildInfoConfigurationsTask.java:455) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoConfigurationsTask.gradleDeployDetails(BuildInfoConfigurationsTask.java:410) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoConfigurationsTask.getArtifactDeployDetails(BuildInfoConfigurationsTask.java:390) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoConfigurationsTask_Decorated.getArtifactDeployDetails(Unknown Source) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoConfigurationsTask.collectDescriptorsAndArtifactsForUpload(BuildInfoConfigurationsTask.java:197) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoBaseTask.prepareAndDeploy(BuildInfoBaseTask.java:267) at org.jfrog.gradle.plugin.artifactory.task.BuildInfoBaseTask.collectProjectBuildInfo(BuildInfoBaseTask.java:365) at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:63) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.doExecute(AnnotationProcessingTaskFactory.java:218) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:211) at org.gradle.api.internal.project.taskfactory.AnnotationProcessingTaskFactory$StandardTaskAction.execute(AnnotationProcessingTaskFactory.java:200) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:570) at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:553) at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80) at or
[JIRA] [core] (JENKINS-23616) Jenkins RPM should have a dependency with x11-devel (required to properly render workspace)
Yaniv Kaul closed JENKINS-23616 as Cannot Reproduce Jenkins RPM should have a dependency with x11-devel (required to properly render workspace) I can't reproduce it now. Strange. I'll close this and if I'll see an execption again I'll re-open. Change By: Yaniv Kaul (02/Jul/14 8:24 AM) Status: Open Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23651) create maven job error
lslmail lslmail created JENKINS-23651 create maven job error Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 02/Jul/14 8:38 AM Description: Stack trace javax.servlet.ServletException: java.lang.AbstractMethodError: hudson.model.TopLevelItemDescriptor.newInstance(Lhudson/model/ItemGroup;Ljava/lang/String;)Lhudson/model/TopLevelItem; at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:778) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:74) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:46) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandl
[JIRA] [matrix-project] (JENKINS-23540) (our case 11519) Post build step not run and difficult to know why
Jonathan Grant commented on JENKINS-23540 (our case 11519) Post build step not run and difficult to know why Many thanks Jens My "Build a free-style software project" are working well. So I will stay using these now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-project] (JENKINS-23540) Post build step not run and difficult to know why
Jens Brejner updated JENKINS-23540 Post build step not run and difficult to know why Change By: Jens Brejner (02/Jul/14 8:48 AM) Summary: (our case 11519) Post build step not run and difficult to know why This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [matrix-project] (JENKINS-23540) Post build step not run and difficult to know why
Jens Brejner commented on JENKINS-23540 Post build step not run and difficult to know why Removing pseudolink to Praqma's internal tracker. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23647) Ability to fetch variant sub-project not just from variant root
stan T updated JENKINS-23647 Ability to fetch variant sub-project not just from variant root Change By: stan T (02/Jul/14 8:54 AM) Description: I tried fetching just one sub-project from a branch/variant, it was working from MKS as well as from command line, but when I tried using for example : #/Root_Project#Sub-project/Sub-sub-project#d=variant_name wheremy branch was created from Sub-project to its children, the fetch of Sub-sub-project failed using plugin.If I fetch from Sub-project e.g. #/Root_Project#Sub-project#d=variant_name then it succeeded. Error :Preparing to execute si projectinfo for #/Root_Project#Sub-project/Sub-sub-project#d=variant_nameAn API Exception was caught!The project #/Root_Project#Sub-project/Sub-sub-project#d=variant_name could not be located on the server [removed by poster]:18000: MKS125319: For subproject Sub-sub-project/project.pj the variant subproject on development path variant_name cannot be accessed because it is not part of the current project configuration and is not eligible to be accessed from the specified configuration: MKS125320: subproject Sub-sub-project/project.pj is not the root of development path variant_name.si projectinfo --user=[removed by poster] --port=18000 --hostname=[removed by poster] --project=#/Root_Project#Sub-project/Sub-sub-project#d=variant_name -- returned exit code 128Finished: FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nunit] (JENKINS-23652) Adding NUnit publisher to inheritance plugin project results in an unsaveable job
Ollie Edwards created JENKINS-23652 Adding NUnit publisher to inheritance plugin project results in an unsaveable job Issue Type: Bug Affects Versions: current Assignee: redsolo Components: nunit Created: 02/Jul/14 9:00 AM Description: 1. Install inheritance-plugin and NUnit plugin 2. Create new job of type inheritence 3. Add a post build action to publish NUnit report 4. Click save A loading spinner will appear but the job will never save. If you try to access the job from another tab the same thing occurs. The job is unrecoverable from the GUI, must delete the plugin manually from XML. I don't know which of the 2 plugins is causing this but I can't replicate with any other publisher. Environment: Jenkins 1.570, NUnit plugin 0.15, Inheritance plugin 1.5.0 Project: Jenkins Priority: Major Reporter: Ollie Edwards This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23647) Ability to fetch variant sub-project not just from variant root
stan T updated JENKINS-23647 Ability to fetch variant sub-project not just from variant root Change By: stan T (02/Jul/14 9:11 AM) Description: I tried fetching just one sub-project from a branch/variant, it was working from MKS as well as from command line, but when I tried using for example : #/Root_Project#Sub-project/Sub-sub-project#d=variant_name wheremy branch was created from Sub-project to its children, the fetch of Sub-sub-project failed using plugin.If I fetch from Sub-project e.g. #/Root_Project#Sub-project#d=variant_name then it succeeded. Error :Preparing to execute si projectinfo for #/Root_Project#Sub-project/Sub-sub-project#d=variant_nameAn API Exception was caught!The project #/Root_Project#Sub-project/Sub-sub-project#d=variant_name could not be located on the server [removed by poster]:18000: MKS125319: For subproject Sub-sub-project/project.pj the variant subproject on development path variant_name cannot be accessed because it is not part of the current project configuration and is not eligible to be accessed from the specified configuration: MKS125320: subproject Sub-sub-project/project.pj is not the root of development path variant_name.si projectinfo --user=[removed by poster] --port=18000 --hostname=[removed by poster] --project=#/Root_Project#Sub-project/Sub-sub-project#d=variant_name -- returned exit code 128Finished: FAILURE Using commandline, this is working :si createsandbox --project=/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_name . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [config-rotator] (JENKINS-23653) Improve performance while establishing view (case 11425)
Mads Nielsen created JENKINS-23653 Improve performance while establishing view (case 11425) Issue Type: Improvement Affects Versions: current Assignee: Praqma Support Components: config-rotator Created: 02/Jul/14 9:15 AM Project: Jenkins Priority: Major Reporter: Mads Nielsen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [nunit] (JENKINS-23652) Adding NUnit publisher to inheritance plugin project results in an unsaveable job
Ollie Edwards updated JENKINS-23652 Adding NUnit publisher to inheritance plugin project results in an unsaveable job Change By: Ollie Edwards (02/Jul/14 9:16 AM) Component/s: project-inheritance This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Sean Wang created JENKINS-23654 UpdateCenter stuck at preparation phase when jenkins server is behind GFW Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: update-center Created: 02/Jul/14 9:16 AM Description: Try to install a plugin in PluginManager; click "Install and restart". in UpdateCenter, screen stuck at "Preparation Checking internet connectivity". No logs printed out in `var/log/jenkins/jenkins.log` This bug is caused by method `getConnectionCheckUrl` using url "google.com" to check connectivity. https://github.com/jenkinsci/jenkins/blob/afd8da49901775900a80eb2b2a9746b01156b0ba/core/src/main/java/hudson/model/UpdateCenter.java#L841 Environment: MacOS X Mavericks; jenkins Mac installation package; Server is in PR. China without any proxies. Google.com cannot accessed due to GFW blocking Project: Jenkins Labels: jenkins plugin Priority: Major Reporter: Sean Wang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds] (JENKINS-20492) Re-Execute promotion button is gone
Vincent Mos commented on JENKINS-20492 Re-Execute promotion button is gone I like to add i also have problems with the Rexecute Button that is not shown. I have a job with 3 different promotion tasks. Two Of them show the reexecute button. One of them isn't. I can not find any difference in the configuration between the 3 that justifies this difference. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23655) Jenkins Windows Service SVN checkout permissions problem
Jonathan Grant created JENKINS-23655 Jenkins Windows Service SVN checkout permissions problem Issue Type: Bug Assignee: Unassigned Components: core Created: 02/Jul/14 9:27 AM Description: Hello Could I report a possible problem with Jenkins Service. On Windows this runs as group "LocalService", this then follows my "Build a free-style software project" item, which does: SVN checkout Build step calls my "build.bat" build.bat has problems copying file, because all files and directories checked out from SVN by Jenkins have Owner "Administrators" If I change the Jenkins Service in Control Panel->Administrative Tools->Services to run as a specific user "OFFICE\builduser" (Rather than "Local System account"). I delete the SVN checkout, and run again the Jenkins Item, I still see all files and directories checked out by Jenkins have Owner "Administrators". Any idea how to get files to be checked out by Jenkins to have the correct Owner? If I login to the machine as builduser, "run CMD.exe as Administrator", it can run build.bat without problems, so it seems a permissions problem. build.bat runs some cygwin commands, that otherwise work when run as a regular user (me on my machine, or the machine with Jenkins) Thanks for any suggestions. Project: Jenkins Priority: Major Reporter: Jonathan Grant This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23647) Ability to fetch variant sub-project not just from variant root
stan T updated JENKINS-23647 Ability to fetch variant sub-project not just from variant root Change By: stan T (02/Jul/14 9:28 AM) Description: I tried fetching just one sub-project from a branch/variant, it was working from MKS as well as from command line, but when I tried using for example : #/Root_Project#Sub-project/Sub-sub-project#d=variant_name wheremy branch was created from Sub-project to its children, the fetch of Sub-sub-project failed using plugin.If I fetch from Sub-project e.g. #/Root_Project#Sub-project#d=variant_name then it succeeded.Error :Preparing to execute si projectinfo for #/Root_Project#Sub-project/Sub-sub-project#d=variant_nameAn API Exception was caught!The project #/Root_Project#Sub-project/Sub-sub-project#d=variant_name could not be located on the server [removed by poster]:18000: MKS125319: For subproject Sub-sub-project/project.pj the variant subproject on development path variant_name cannot be accessed because it is not part of the current project configuration and is not eligible to be accessed from the specified configuration: MKS125320: subproject Sub-sub-project/project.pj is not the root of development path variant_name.si projectinfo --user=[removed by poster] --port=18000 --hostname=[removed by poster] --project=#/Root_Project#Sub-project/Sub-sub-project#d=variant_name -- returned exit code 128Finished: FAILUREUsing commandline command line , this is working :si projectinfo --project=/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_namesi createsandbox --project=/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_name . This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
commented on JENKINS-23643
Regressions with 1.2.3
I took a look at commit (https://github.com/hgomez/dependency-check-plugin/commit/9c29b7e321c192f9ac1a02d404f07d0b168ecfc7) and see some problems.
First, when you create post-pre step, instance didn't exist and so test for Maven is not executed :
if test="${instance.isMaven(it.getClass())}">
Also isMaven() in buildescriptor shouldn't use clazz but provided parm :
public boolean isMaven(Classextends AbstractProject> aP) {
return MavenModuleSet.class.isAssignableFrom(aP) || MavenModule.class.isAssignableFrom(aP);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-23647) Ability to fetch variant sub-project not just from variant root
stan T updated JENKINS-23647 Ability to fetch variant sub-project not just from variant root Change By: stan T (02/Jul/14 9:35 AM) Description: I tried fetching just one sub-project from a branch/variant, it was working from MKS as well as from command line, but when I tried using for example : #/Root_Project#Sub-project/Sub-sub-project#d=variant_name wheremy branch was created from Sub-project to its children, the fetch of Sub-sub-project failed using plugin.If I fetch from Sub-project e.g. #/Root_Project#Sub-project#d=variant_name then it succeeded.Error :Preparing to execute si projectinfo for #/Root_Project#Sub-project/Sub-sub-project#d=variant_nameAn API Exception was caught!The project #/Root_Project#Sub-project/Sub-sub-project#d=variant_name could not be located on the server [removed by poster]:18000: MKS125319: For subproject Sub-sub-project/project.pj the variant subproject on development path variant_name cannot be accessed because it is not part of the current project configuration and is not eligible to be accessed from the specified configuration: MKS125320: subproject Sub-sub-project/project.pj is not the root of development path variant_name.si projectinfo --user=[removed by poster] --port=18000 --hostname=[removed by poster] --project=#/Root_Project#Sub-project/Sub-sub-project#d=variant_name -- returned exit code 128Finished: FAILUREUsing command line, this is working :si projectinfo --project=/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_namesi createsandbox --project=/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_name . I tried working around it, instead of using :#/Root_Project#Sub-project/Sub-sub-project#d=variant_nameI used :/Root_Project/Sub-project/Sub-sub-project/project.pj --devpath=variant_namebut to no avail.. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
commented on JENKINS-23643
Regressions with 1.2.3
I noticed an error about missing artifacts.json :
java.io.FileNotFoundException: /var/lib/mycorp/cijenkins/jobs/svn-v1-hook/builds/2014-07-02_11-38-57/com.mycorp.v1link$v1link/archive/artifacts.json
There is artifacts.json in job workspace but not there and with another timestamp
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_10-29-56/archive/artifacts.json
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_11-39-03/archive/artifacts.json
/var/lib/mycorp/cijenkins/jobs/svn-v1-hook/modules/com.mycorp.rdops.connectors$svn-v1-hook/builds/2014-07-02_11-36-06/archive/artifacts.json
I took a look in artifacts.json, it seems empty :
{"@type":"java.util.LinkedHashSet"}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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-name-setter] (JENKINS-23639) EnvInject squelches changes to $BUILD_DISPLAY_NAME made by build name setter plugin
Ollie Edwards updated JENKINS-23639 EnvInject squelches changes to $BUILD_DISPLAY_NAME made by build name setter plugin Change By: Ollie Edwards (02/Jul/14 9:45 AM) Component/s: build-name-setter This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23626) Build Queue no longer has "cancel all" like Hudson version 2.2.1
Jonathan Grant commented on JENKINS-23626 Build Queue no longer has "cancel all" like Hudson version 2.2.1 Thank you for the effort of making this Daniel Any chance of providing a built version? I'm just using an installed version of Jenkins at present. Or even better, could it be added to the official Jenkins install next version please. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez
edited a comment on JENKINS-23643
Regressions with 1.2.3
I took a look at commit (https://github.com/jenkinsci/dependency-check-plugin/commit/9c29b7e321c192f9ac1a02d404f07d0b168ecfc7) and see some problems.
First, when you create post-pre step, instance didn't exist and so test for Maven is not executed :
if test="${instance.isMaven(it.getClass())}">
Also isMaven() in buildescriptor shouldn't use clazz but provided parm :
public boolean isMaven(Classextends AbstractProject> aP) {
return MavenModuleSet.class.isAssignableFrom(aP) || MavenModule.class.isAssignableFrom(aP);
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [dependency-check-jenkins] (JENKINS-23643) Regressions with 1.2.3
Henri Gomez commented on JENKINS-23643 Regressions with 1.2.3 I also reviewed artifacts.json generation and it won't works. Pom object passed in MavenArtifactRecorder is not real Maven pom but a Jenkins facade. pom.getArtifacts() didn't returns expected artifacts. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23656) GitSCM checks wrong branch for changes
Artem Alexandrov created JENKINS-23656 GitSCM checks wrong branch for changes Issue Type: Bug Assignee: Nicolas De Loof Components: git-client Created: 02/Jul/14 10:17 AM Description: Steps: 1. Setup a repo with such branches: A/SameNameBranch B/SameNameBranch 2. Setup job to poll "B/SameNameBranch" 3. Watch never ending changes Expected: plugin executes this command on getting current commit hash: git ls-remote -h g...@repo.org:user/some.git B/SameNameBranch Actual: plugin executes WRONG command on getting current commit hash: git ls-remote -h g...@repo.org:user/some.git SameNameBranch It skips full branch name and only uses last path component. This command then returns list of all branches ending with "SameNameBranch", and "A" version has different commit than the needed one. Please just make it to call command with full branch name Environment: Jenkins ver. 1.570; Git Client 1.9.1 Project: Jenkins Labels: git scm polling Priority: Critical Reporter: Artem Alexandrov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Pascal Grippi commented on JENKINS-21985 java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler Hi, It looks we are curently experiencing the same issue. We have a slave rinnung on Win8 without issue using the artifact publisher and it work for a while without any problem. But with another slave running on Lunix computer (Linux ubuntu-jenkins-uklab-node002 3.2.0-64-generic #97-Ubuntu SMP Wed Jun 4 22:03:48 UTC 2014 i686 i686 i386 GNU/Linux) it is not possible to make it works even with the most simplest Job. log: [EnvInject] - Loading node environment variables. Building remotely on UBUNTU-JENKINS-UKLAB-NODE002 in workspace /var/jenkins/workspace/t_artifact_jnr_posix_issue Run condition [Execute Shell] enabling prebuild for step [Archive the artifacts] [t_artifact_jnr_posix_issue] $ /bin/sh -xe /tmp/CommandInterpreterCondition1191287595508755352.sh + touch test.txt Run condition [Execute Shell] enabling perform for step [Archive the artifacts] Archiving artifacts ERROR: Failed to archive artifacts: test.txt java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.FilePath.copyRecursiveTo(FilePath.java:2016) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.remoting.Channel$3.adapt(Channel.java:755) at hudson.remoting.Channel$3.adapt(Channel.java:750) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.FilePath.copyRecursiveTo(FilePath.java:2014) ... 15 more Caused by: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:101) at hudson.util.DirScanner.scanSingle(DirScanner.java:49) at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2540) at hudson.FilePath.writeToTar(FilePath.java:2052) at hudson.FilePath.access$1000(FilePath.java:172) at hudson.FilePath$41.invoke(FilePath.java:1993) at hudson.FilePath$41.invoke(FilePath.java:1989) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: jnr.posix.POSIXHandler (WebAppClassLoader=Jenkins v1.548@1dd49247 did not find class file) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch2(RemoteClassLoader.java:727) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:777) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:784) at sun.reflect.GeneratedMethodAccessor5170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.remoting.Remote
[JIRA] [core] (JENKINS-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Pascal Grippi edited a comment on JENKINS-21985 java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler Hi, It looks we are curently experiencing the same issue. We have a slave rinnung on Win8 without issue using the artifact publisher and it work for a while without any problem. But with another slave running on Lunix computer (Linux ubuntu-jenkins-uklab-node002 3.2.0-64-generic #97-Ubuntu SMP Wed Jun 4 22:03:48 UTC 2014 i686 i686 i386 GNU/Linux) it is not possible to make it works even with the most simplest Job. Edit: Jenkins ver. 1.548 log: [EnvInject] - Loading node environment variables. Building remotely on UBUNTU-JENKINS-UKLAB-NODE002 in workspace /var/jenkins/workspace/t_artifact_jnr_posix_issue Run condition [Execute Shell] enabling prebuild for step [Archive the artifacts] [t_artifact_jnr_posix_issue] $ /bin/sh -xe /tmp/CommandInterpreterCondition1191287595508755352.sh + touch test.txt Run condition [Execute Shell] enabling perform for step [Archive the artifacts] Archiving artifacts ERROR: Failed to archive artifacts: test.txt java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.FilePath.copyRecursiveTo(FilePath.java:2016) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.remoting.Channel$3.adapt(Channel.java:755) at hudson.remoting.Channel$3.adapt(Channel.java:750) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.FilePath.copyRecursiveTo(FilePath.java:2014) ... 15 more Caused by: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:101) at hudson.util.DirScanner.scanSingle(DirScanner.java:49) at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2540) at hudson.FilePath.writeToTar(FilePath.java:2052) at hudson.FilePath.access$1000(FilePath.java:172) at hudson.FilePath$41.invoke(FilePath.java:1993) at hudson.FilePath$41.invoke(FilePath.java:1989) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: jnr.posix.POSIXHandler (WebAppClassLoader=Jenkins v1.548@1dd49247 did not find class file) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch2(RemoteClassLoader.java:727) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:777) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:784) at sun.reflect.GeneratedMethodAccessor5170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java
[JIRA] [core] (JENKINS-23191) ReverseBuildTrigger.threshold not consistently saved
Christian Langmann commented on JENKINS-23191 ReverseBuildTrigger.threshold not consistently saved Seems to be a problem of the Maven-job: Setup "job A" as Freestyle Project Setup "job B" as Freestyle Project and set "job A" as trigger (Status shows job A as Upstream Project) Setup "job Maven-B" as Maven Project and set "job A" as trigger (Status does not show any upstream project) When "job A" is build and finishes, "job B" is triggered, but not "job Maven-B" You can make "job Maven-B" triggered by "job A" by setting it as a Post-Build-Action in "job A" This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [other] (JENKINS-23478) Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central
Oliver Gondža updated JENKINS-23478 Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central Change By: Oliver Gondža (02/Jul/14 10:33 AM) Component/s: other Component/s: artifact-diff This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-23656) GitSCM checks wrong branch for changes
Artem Alexandrov resolved JENKINS-23656 as Duplicate GitSCM checks wrong branch for changes https://issues.jenkins-ci.org/browse/JENKINS-23266 Change By: Artem Alexandrov (02/Jul/14 10:35 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] [other] (JENKINS-23478) Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central
Oliver Gondža commented on JENKINS-23478 Could not find artifact javax.xml:jaxrpc-api:jar:1.1.3 in central I doubt this is a Jenkins issue. Linked jar[1] does not seems to exist. [1] http://repo.maven.apache.org/maven2/javax/xml/jaxrpc-api/1.1.3/jaxrpc-api-1.1.3.jar This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ownership] (JENKINS-23657) Icon background is not transparent
Oliver Gondža created JENKINS-23657 Icon background is not transparent Issue Type: Bug Assignee: Oleg Nenashev Attachments: manage_ownership_icon.png Components: ownership Created: 02/Jul/14 10:50 AM Description: Screenshot attached Project: Jenkins Priority: Trivial Reporter: Oliver Gondža This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23651) create maven job error
lslmail lslmail resolved JENKINS-23651 as Won't Fix create maven job error maven plugin upgrade to new version, and resolved Change By: lslmail lslmail (02/Jul/14 10:53 AM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ci-game] (JENKINS-23658) CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Ireneusz Makowski created JENKINS-23658 CI Game plugin throws exception after upgrade to Jenkins 1.554.3 Issue Type: Bug Affects Versions: current Assignee: redsolo Components: ci-game, core Created: 02/Jul/14 11:05 AM Description: We have following exception after upgrade to latest version of Jenkins: ERROR: Publisher hudson.plugins.cigame.GamePublisher aborted due to exception java.lang.NullPointerException at java.util.LinkedList$ListItr.next(Unknown Source) at hudson.plugins.cigame.model.ScoreCard.record(ScoreCard.java:121) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:60) at hudson.plugins.cigame.GamePublisher.perform(GamePublisher.java:45) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:45) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.cleanUp(Build.java:192) at hudson.model.Run.execute(Run.java:1730) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Environment: Windows 2008 R2 64bit Jenkins 1.554.3 Project: Jenkins Priority: Blocker Reporter: Ireneusz Makowski This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-13390) "Build whenever a SNAPSHOT dependency is built" should work in way that is more expected
Guy Rooms commented on JENKINS-13390 "Build whenever a SNAPSHOT dependency is built" should work in way that is more expected Also ran into this problem: I would also expect to have all downstream jobs triggered Apart from that discussion (whether or not all jobs should be triggered), I believe it is not acceptable to have all those downstream jobs displayed as downstream jobs while they are not being triggered. In current behavior, logging could at least be improved to indicate that (or why) some jobs were not triggered 'on purpose'. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Pascal Grippi edited a comment on JENKINS-21985 java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler Hi, It looks we are curently experiencing the same issue. We have a slave rinnung on Win8 without issue using the artifact publisher and it worked for a while without any problem. But with another slave running on Lunix computer (Linux ubuntu-jenkins-uklab-node002 3.2.0-64-generic #97-Ubuntu SMP Wed Jun 4 22:03:48 UTC 2014 i686 i686 i386 GNU/Linux) it is not possible to make it works even with the most simple Job. Edit: Jenkins ver. 1.548 log: [EnvInject] - Loading node environment variables. Building remotely on UBUNTU-JENKINS-UKLAB-NODE002 in workspace /var/jenkins/workspace/t_artifact_jnr_posix_issue Run condition [Execute Shell] enabling prebuild for step [Archive the artifacts] [t_artifact_jnr_posix_issue] $ /bin/sh -xe /tmp/CommandInterpreterCondition1191287595508755352.sh + touch test.txt Run condition [Execute Shell] enabling perform for step [Archive the artifacts] Archiving artifacts ERROR: Failed to archive artifacts: test.txt java.io.IOException: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.FilePath.copyRecursiveTo(FilePath.java:2016) at jenkins.model.StandardArtifactManager.archive(StandardArtifactManager.java:57) at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:140) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$2.run(BuildStepRunner.java:110) at org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail.conditionalRun(BuildStepRunner.java:154) at org.jenkins_ci.plugins.run_condition.BuildStepRunner.perform(BuildStepRunner.java:105) at org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder.perform(SingleConditionalBuilder.java:108) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:784) at hudson.model.Build$BuildExecution.build(Build.java:199) at hudson.model.Build$BuildExecution.doRun(Build.java:160) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:565) at hudson.model.Run.execute(Run.java:1670) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:231) Caused by: java.util.concurrent.ExecutionException: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.remoting.Channel$3.adapt(Channel.java:755) at hudson.remoting.Channel$3.adapt(Channel.java:750) at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55) at hudson.FilePath.copyRecursiveTo(FilePath.java:2014) ... 15 more Caused by: java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler at hudson.util.IOUtils.mode(IOUtils.java:125) at hudson.util.io.TarArchiver.visit(TarArchiver.java:101) at hudson.util.DirScanner.scanSingle(DirScanner.java:49) at hudson.FilePath$ExplicitlySpecifiedDirScanner.scan(FilePath.java:2540) at hudson.FilePath.writeToTar(FilePath.java:2052) at hudson.FilePath.access$1000(FilePath.java:172) at hudson.FilePath$41.invoke(FilePath.java:1993) at hudson.FilePath$41.invoke(FilePath.java:1989) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2461) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:328) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1$1.run(Engine.java:63) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.ClassNotFoundException: jnr.posix.POSIXHandler (WebAppClassLoader=Jenkins v1.548@1dd49247 did not find class file) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch2(RemoteClassLoader.java:727) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch4(RemoteClassLoader.java:777) at hudson.remoting.RemoteClassLoader$ClassLoaderProxy.fetch3(RemoteClassLoader.java:784) at sun.reflect.GeneratedMethodAccessor5170.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java
[JIRA] [update-center] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Sean Wang updated JENKINS-23654 UpdateCenter stuck at preparation phase when jenkins server is behind GFW Change By: Sean Wang (02/Jul/14 11:53 AM) Description: Try to install a plugin in PluginManager; click "Install and restart".in UpdateCenter, screen stuck at "Preparation Checking internet connectivity".No logs printed out in `var/log/jenkins/jenkins.log`This bug is caused by method `getConnectionCheckUrl` using url "google.com" to check connectivity.https://github.com/jenkinsci/jenkins/blob/afd8da49901775900a80eb2b2a9746b01156b0ba/core/src/main/java/hudson/model/UpdateCenter.java#L841 --- update:I just built jenkins.war replaced the google.com with another url. But It still not work.I got these warnings:七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of ssh-credentials for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of credentials for plugin ssh-credentials七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of git-client for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Dependent install of ssh-credentials for plugin git-client already added, skipping七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of scm-api for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Dependent install of credentials for plugin git already added, skipping This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Sean Wang updated JENKINS-23654 UpdateCenter stuck at preparation phase when jenkins server is behind GFW Change By: Sean Wang (02/Jul/14 11:56 AM) Description: Try to install a plugin in PluginManager; click "Install and restart".in UpdateCenter, screen stuck at "Preparation Checking internet connectivity".No logs printed out in `var/log/jenkins/jenkins.log`This bug is caused by method `getConnectionCheckUrl` using url "google.com" to check connectivity.https://github.com/jenkinsci/jenkins/blob/afd8da49901775900a80eb2b2a9746b01156b0ba/core/src/main/java/hudson/model/UpdateCenter.java#L841--- update:I just built jenkins.war replaced the google.com with another url. But It still not work.I got these warnings : , and the log is the same when using 'google.com' url. So it may not be the url problem. 七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of ssh-credentials for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of credentials for plugin ssh-credentials七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of git-client for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Dependent install of ssh-credentials for plugin git-client already added, skipping七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Adding dependent install of scm-api for plugin git七月 02, 2014 7:49:14 下午 hudson.model.UpdateSite$Plugin deploy警告: Dependent install of credentials for plugin git already added, skipping This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Bernie Durfee commented on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate I thought the Jenkins Git plugin runs Git from the command line, but the error is a Java error. Why is the URL being hit via 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] [integrity-plugin] (JENKINS-23647) Ability to fetch variant sub-project not just from variant root
Cletus D'Souza resolved JENKINS-23647 as Won't Fix Ability to fetch variant sub-project not just from variant root To correctly figure out the 'Configuration Path' for a project/subproject, you need to open the project/subproject in that context (variant in this case) in the Integrity Client GUI. Then go to Project --> Views --> View Information. This will provide you with the correct configuration path. Cut-n-paste that configuration path in Jenkins. If for some reason that doesn't work, then this is a core product problem and you will need to open an issue with PTC Integrity Support. There is nothing that can be done from a plugin perspective. Change By: Cletus D'Souza (02/Jul/14 1:05 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-23638) Error in Checkin not failing job
Cletus D'Souza commented on JENKINS-23638 Error in Checkin not failing job Isn't there a Jenkins preference to fail the build if any 'Build Step' fails? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Mark Waite commented on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate Command line git will prompt for a password if required. Jenkins cannot answer that password prompt, so it makes a best effort (and largely successful effort) to detect if the git command line would prompt for a password before it calls command line git. The failing case is deep inside the Java runtime while the git client plugin was detecting if the call to command line git would have blocked prompting for a password. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [claim] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.
Jeff G commented on JENKINS-23513 Claim plugin doesn't allow you to claim unstable builds. I would also really like to see this improvement done. In our environment, we have nightly integration tests which run and are flagged as unstable if any of their tests fail. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds] (JENKINS-10068) Ability to remove a Promotion on a promoted build
Landis Almand commented on JENKINS-10068 Ability to remove a Promotion on a promoted build Related, also need related promotions to be deleted when a build is deleted. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
vjuranek commented on JENKINS-23617 Cannot use spaces in groovy script parameters using some groovy executable parameters with spaces seems to me quite rare use case for which using CommandLine seems to me like an overkill. Would some more simple solution like quoting parameter with spaces and using e.g. reg. exp. for parsing solve your problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client] (JENKINS-22675) Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate
Bernie Durfee commented on JENKINS-22675 Jenkins GIT Plugin unable to access repository using HTTPS with self-signed certificate Gotcha, so Jenkins hits the URL in advance of calling Git. I fixed the issue by adding the certificate to the cacerts keystore in the JVM that Jenkins is using. I have the 'skip certificate check' plugin installed, but was still getting the error until I added the certificate. Shouldn't that plugin work in this instance? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
Daniel Beck edited a comment on JENKINS-23617 Cannot use spaces in groovy script parameters (stupid comment) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
Daniel Beck commented on JENKINS-23617 Cannot use spaces in groovy script parameters Would http://javadoc.jenkins-ci.org/hudson/util/ArgumentListBuilder.html work here? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23638) Error in Checkin not failing job
Daniel Beck commented on JENKINS-23638 Error in Checkin not failing job Failing when this happens should be default Jenkins behavior. What version of Jenkins is this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [tracking-git] (JENKINS-23659) tracking-git: Use parameter or environment variable to specify which build to track
Geoff Cummings created JENKINS-23659 tracking-git: Use parameter or environment variable to specify which build to track Issue Type: Improvement Affects Versions: current Assignee: Unassigned Components: tracking-git Created: 02/Jul/14 3:25 PM Description: Hi, I would like to be able to use a build parameter to choose which build of the project to track instead of only the lastSuccessful, lastFailed etc... example configuration: Create project_B, Add RunParameter Name: VERSION_TO_BUILD Project: Project_A Filter: Stable Builds Only Enable Track Git source of another project. Project to Track: Project_A Build to Track: By Number Build Number: $VERSION_TO_BUILD_NUMBER Behaviour When I click Build on Project B I will be shown a dropdown containing a list of Stable builds for project_A. I select one of the builds, lets say #10, and click Build. Run parameter plugin will populate the environment variable VERSION_TO_BUILD_NUMBER = 10 the Tracking Git plugin will resolve the $VERSION_TO_BUILD_NUMBER and track Project A build #10 thanks Geoff Project: Jenkins Priority: Major Reporter: Geoff Cummings This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [update-center] (JENKINS-23654) UpdateCenter stuck at preparation phase when jenkins server is behind GFW
Daniel Beck commented on JENKINS-23654 UpdateCenter stuck at preparation phase when jenkins server is behind GFW The connection check URL actually used is part of the update center metadata, see the comment. You'll need to host your own update center and replace the URL with one that can be reached from your network. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ci-game] (JENKINS-23658) CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Daniel Beck updated JENKINS-23658 CI Game plugin throws exception after upgrade to Jenkins 1.554.3 Trivial workaround available: Disable or remove the plugin for the affected jobs or from the instance. Reducing priority because of that. Does Jenkins have entries in 'Manage Old Data'? What version of Jenkins were you upgrading from? Change By: Daniel Beck (02/Jul/14 3:38 PM) Priority: Blocker Minor This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [claim] (JENKINS-23513) Claim plugin doesn't allow you to claim unstable builds.
Scott J commented on JENKINS-23513 Claim plugin doesn't allow you to claim unstable builds. We have a similar policy. An unstable build is just as bad as a failed build, so it would be really nice to be able to use the Claim Plugin in that scenario. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy] (JENKINS-23617) Cannot use spaces in groovy script parameters
enterit commented on JENKINS-23617 Cannot use spaces in groovy script parameters Why do you think using spaces is a quite rare use case? It may happen quite often, especially if other build params are passed to the script, like job description, text chunks etc. There is any easy workaround if you specify script text. But not if you specify script name to execute. If adding this new dependency is undesirable, we could copy CommandLine.parse(..) implementation. Ideally we should not be parsing command line at all, but hudson.Launcher.ProcStarter does not seem to accept single-string command. I do not think there is an easy way to parse command line using regexp - it can be error-prone. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [tracking-git] (JENKINS-23659) tracking-git: Use parameter or environment variable to specify which build to track
Geoff Cummings commented on JENKINS-23659 tracking-git: Use parameter or environment variable to specify which build to track Added first pass at this in the following pull request: https://github.com/jenkinsci/tracking-git-plugin/pull/1/ current state: Not pretty but it works so please provide feedback and advice... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23657) user.gif icon background is not transparent
Oleg Nenashev updated JENKINS-23657 user.gif icon background is not transparent Change By: Oleg Nenashev (02/Jul/14 4:43 PM) Summary: Icon user.gif icon background is not transparent Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23657) Icon background is not transparent
Oleg Nenashev commented on JENKINS-23657 Icon background is not transparent @Oliver Ownership Plugins takes icons from the Jenkins core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-2717) svn polling without checkout or update
Fernando Devegili commented on JENKINS-2717 svn polling without checkout or update I'm having this issue as well, a fix would be just great. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ci-game] (JENKINS-23658) CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Oleg Nenashev
edited a comment on JENKINS-23658
CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Seems the issue is unrelated to the core
@Ireneusz
What version of the cigame plugin do you use?
ScoreCard.java
121:for (RuleSet set : ruleBook.getRuleSets()) {
122: record(build, set, listener);
123:}
The plugin returns the null RuleBook, which is being returned by GameDescriptor(seems to be impossible is the last cigame version)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ci-game] (JENKINS-23658) CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Oleg Nenashev
commented on JENKINS-23658
CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Seems the issue is unrelated to the core
@Ireneusz
What version of the cigame plugin do you use?
ScoreCard.java
121:for (RuleSet set : ruleBook.getRuleSets()) Unknown macro: {
122}
The plugin returns the null RuleBook, which is being returned by GameDescriptor(seems to be impossible is the last cigame version)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [ci-game] (JENKINS-23658) CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Oleg Nenashev
edited a comment on JENKINS-23658
CI Game plugin throws exception after upgrade to Jenkins 1.554.3
Seems the issue is unrelated to the core
@Ireneusz
What version of the cigame plugin do you use?
ScoreCard.java
121:for (RuleSet set : ruleBook.getRuleSets()) {
122: record(build, set, listener);
123:}
The plugin occasionally gets the null RuleBook, which is being returned by GameDescriptor(seems to be impossible is the last cigame version)
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Timmy Brolin commented on JENKINS-19994 Unable to delete workspace I am frequently getting this error as well. But I am using Vault, not git. The error I am getting is: "" Deleting project workspace... Cannot delete workspace: java.io.IOException: Remote call on slave1 failed ERROR: Cannot delete workspace: java.io.IOException: Remote call on slave1 failed Finished: FAILURE "" Running on windows 7... Is this the same problem, or a completely different problem? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-23626) Build Queue no longer has "cancel all" like Hudson version 2.2.1
Daniel Beck commented on JENKINS-23626 Build Queue no longer has "cancel all" like Hudson version 2.2.1 I'm pretty sure the use case is not common enough to warrant a core change, and bundling new plugins is a massive can of worms (and now only done for backwards compatibility). Worry not though, the Jenkins default install has everything you need to build the plugin, except maybe the Git plugin. Set up a Maven installation with auto-installer of version 3.0.5 or newer in the global config, create a maven project, specify the Git SCM URL https://github.com/daniel-beck/clear-queue-widget to check out, and save. Click 'Build' and wait a minute or so. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-21985) java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler
Daniel Beck commented on JENKINS-21985 java.lang.NoClassDefFoundError: jnr/posix/POSIXHandler Are there other exceptions earlier in the (system-wide or slave) log that indicate a failure to cache/load jar files on the slave? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plugin] (JENKINS-23626) Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1)
Oleg Nenashev updated JENKINS-23626 Implement "cancel all" action for the Build Queue (like Hudson version 2.2.1) Updated the issue according to the discussion @Daniel, I think the feature should be available as a plugin. AFAIK, there's no plugins with similar functionality, hence it could be required to create a new one. Change By: Oleg Nenashev (02/Jul/14 7:00 PM) Summary: Build Queue no longer has Implement "cancel all" action for the Build Queue ( like Hudson version 2.2.1 ) Issue Type: Bug New Feature Component/s: plugin Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23646) Build tokens should be replaced by build token root plugin
Jesse Glick updated JENKINS-23646 Build tokens should be replaced by build token root plugin Build tokens work fine if anonymous users have read access, which is true in many Jenkins installations, though certainly not the more heavily secured ones. But simply “deprecating” this feature built into Jenkins core is not straightforward for compatibility reasons; it is intertwined with several other features. Change By: Jesse Glick (02/Jul/14 7:01 PM) Summary: Build token plugin tokens should be replaced by build token root plugin Issue Type: Bug Task Component/s: core Component/s: build-token-root This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion] (JENKINS-23146) StringIndexOutOfBoundsException on subversion checkout
Reece Johnston commented on JENKINS-23146 StringIndexOutOfBoundsException on subversion checkout Also, I should add that I needed the svnexternals fix from 2.4, so after realizing your branch was off of 2.3, I went ahead and merged your branch and the 2.4 tag. Then, I compiled and loaded my own custom version of the plugin with your fix and all of 2.4's features. Thus far, everything has been running great, and that's with hundreds of builds going through the system. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [accurev] (JENKINS-11461) FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset
Laura Neff commented on JENKINS-11461 FATAL: hudson.remoting.RequestAbortedException: java.net.SocketException: Connection reset Seeing this on Jenkins 1.532.3. Both Jenkins master and slaves running on Windows 7, as services. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [buildgraph-view] (JENKINS-23607) BuildGraph page doesn't load if some builds are queued
stuart rowe commented on JENKINS-23607 BuildGraph page doesn't load if some builds are queued I believe the getBuild() member method of JobInvocation is blocking as get() is called on the underlying Future object. The getBuild() method is called for the JobInvocation target of each FlowRun.JobEdge in the FlowRun Job graph when collecting all downstream Runs for the Flow. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-flow] (JENKINS-23607) BuildGraph page doesn't load if some builds are queued
stuart rowe updated JENKINS-23607 BuildGraph page doesn't load if some builds are queued Change By: stuart rowe (02/Jul/14 7:58 PM) Component/s: build-flow This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23660) Attached log in Jenkins email incomplete
Reinhard Karbas created JENKINS-23660 Attached log in Jenkins email incomplete Issue Type: Bug Affects Versions: current Assignee: Alex Earl Components: core, email-ext Created: 02/Jul/14 8:03 PM Description: I recently upgraded my Jenkins server from 1.559 to 1.570 and now the attached logs for the build jobs that run on the MAC are incomplete I had them attached as compressed file using the email-ext plugin, but with this version of Jenkins parts of the log are missing When attaching the uncompressed log I only get the first 2 MB of the log, which on the server has a size of about 14 MB Either the plugin has a problem or the log is not flushed out of memory before processing the post jobs. There are no error messages in the Jenkins log file The version of the email-ext plugin is 2.38.1 For now I am not attaching the log file to my job emails so I have to click on the link in the email to check the output Environment: Server SLES 11 SP2, client MAC OS X Mavericks Project: Jenkins Priority: Minor Reporter: Reinhard Karbas This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23660) Attached log in Jenkins email incomplete
Alex Earl commented on JENKINS-23660 Attached log in Jenkins email incomplete Email-ext is only built and tested against the LTS release,. Since you are using bleeding edge, you are almost guaranteed to have issues. This probably won't be looked at until the Jenkins release becomes LTS. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23660) Attached log in Jenkins email incomplete
Reinhard Karbas commented on JENKINS-23660 Attached log in Jenkins email incomplete Please explain what LTS compared to bleeding edge means The version of Jenkins that I am using is officially released! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23660) Attached log in Jenkins email incomplete
Alex Earl commented on JENKINS-23660 Attached log in Jenkins email incomplete LTS is Long Term Support, which is a more stable, tested version of Jenkins. Jenkins releases often and the latest versions will possibly have issues, especially with plugins that are developed against the LTS version. If there are changes in the core, then they will not be handled in email-ext until such a time as 1.570 (or something after it) becomes the new LTS release. The next LTS release will be based on 1.565 I believe. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-8722) Make the BuildNumber that artifacts were copied from available to later build steps.
Nathan Perry commented on JENKINS-8722 Make the BuildNumber that artifacts were copied from available to later build steps. This bugfix just helped me out and is perfect with the project name in the environment variable name. Thanks. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven2] (JENKINS-11333) Make fingerprinting configurable in Maven projects
Joseph Benken commented on JENKINS-11333 Make fingerprinting configurable in Maven projects Does this address https://issues.jenkins-ci.org/browse/JENKINS-18615? Is there a target version for this enhancement? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git] (JENKINS-19994) Unable to delete workspace
Mark Waite commented on JENKINS-19994 Unable to delete workspace As far as I can tell, that is a completely different problem. You probably want to report a bug against the Vault 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] [github] (JENKINS-23661) github webhook failing
Daniel Craigmile created JENKINS-23661 github webhook failing Issue Type: Bug Assignee: Unassigned Components: github Created: 02/Jul/14 9:11 PM Description: Getting this error when the github webhook is invoked: WARNING: Error while serving http://my-ci-server/github-webhook/ java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.lang.Thread.run(Thread.java:744) [...] Caused by: java.lang.IllegalArgumentException: Github Webhook event of type null is not supported. Only push events are current supported at com.cloudbees.jenkins.GitHubWebHook.doIndex(GitHubWebHook.java:160) ... 71 more Environment: Jenkins version 1.570 Project: Jenkins Priority: Major Reporter: Daniel Craigmile This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23661) github webhook failing
Daniel Craigmile
updated JENKINS-23661
github webhook failing
Change By:
Daniel Craigmile
(02/Jul/14 9:14 PM)
Description:
Getting this error when the github webhook is invoked:
{code}
WARNING: Error while serving http://my-ci-server/github-webhook/java.lang.reflect.InvocationTargetExceptionat sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at java.lang.Thread.run(Thread.java:744)[...]Caused by: java.lang.IllegalArgumentException: Github Webhook event of type null is not supported. Only push events are current supportedat com.cloudbees.jenkins.GitHubWebHook.doIndex(GitHubWebHook.java:160)... 71 more
{code}
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [github] (JENKINS-23662) Github Plugin 1.9 broke webhook trigger
Mark Keisler created JENKINS-23662 Github Plugin 1.9 broke webhook trigger Issue Type: Bug Assignee: Unassigned Attachments: jlog Components: github Created: 02/Jul/14 9:14 PM Description: Upgrading to Github Plugin 1.9 broke webhook build triggers. Reverted to 1.8 and all is well. Error log attached. Environment: debian wheezy x86_64, github enterprise Project: Jenkins Labels: github Priority: Major Reporter: Mark Keisler This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-23127) broken ProjectNamingStrategy Extension
SCM/JIRA link daemon commented on JENKINS-23127 broken ProjectNamingStrategy Extension Code changed in jenkins User: Kanstantsin Shautsou Path: core/src/main/java/jenkins/model/GlobalProjectNamingStrategyConfiguration.java http://jenkins-ci.org/commit/jenkins/afe7da541642e40d60982d459e2802ae81357e34 Log: [FIXED JENKINS-23127] Allow loading classes from plugins. (cherry picked from commit 9568986efb1f435ca2c95422c57fcf579c8bf222) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-20559) hudson.Launcher:ProcStarter::envs() may throw NPE
SCM/JIRA link daemon commented on JENKINS-20559 hudson.Launcher:ProcStarter::envs() may throw NPE Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/Launcher.java http://jenkins-ci.org/commit/jenkins/1273668ba3b47fd344405ba4c49ec5a83ea9b508 Log: [FIXED JENKINS-20559] - ProcStarter: Check for null before cloning of environment variables list Resolves https://issues.jenkins-ci.org/browse/JENKINS-20559 BTW, I also need to add some tests to "Test Harness" in order to improve coverage of nested operations. These test require a fix for https://issues.jenkins-ci.org/browse/JENKINS-19454 Signed-off-by: Oleg Nenashev (cherry picked from commit ef943a3ee69529a9f41353f134043ed3363f12e0) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22693) Resource leak in hudson.model.FileParameterValue
SCM/JIRA link daemon commented on JENKINS-22693 Resource leak in hudson.model.FileParameterValue Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/model/FileParameterValue.java http://jenkins-ci.org/commit/jenkins/eb9cbead0b117e0544871d17e7077e7837a60bb7 Log: [FIXED JENKINS-22693] - Properly close InputStreams in FileParameterValue Signed-off-by: Oleg Nenashev (cherry picked from commit 8767ddb192cf752c7d28f512884b9ecd3b9cdbd4) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15094) Parameters: NPE in canTake() procedures may kill all executors
SCM/JIRA link daemon commented on JENKINS-15094 Parameters: NPE in canTake() procedures may kill all executors Code changed in jenkins User: Oleg Nenashev Path: core/src/main/java/hudson/cli/BuildCommand.java core/src/main/java/hudson/model/ParameterDefinition.java core/src/main/java/hudson/model/ParametersAction.java core/src/main/java/hudson/model/ParametersDefinitionProperty.java http://jenkins-ci.org/commit/jenkins/b6b94ea5e7a89068728c0a65e6323ca6991c7ddb Log: [FIXED JENKINS-15094] - Handle null parameter values in BuildCommand (CLI) and Parameter classes (CLI). The change adds missing checks for null ParameterValue, which may be passed from the CLI. It prevents the death of Jenkins executors during the canTake() check of node labels. Signed-off-by: Oleg Nenashev (cherry picked from commit 7b894f57b78be0e4d847fe1c971955d2cbb08e58) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-22934) Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken
SCM/JIRA link daemon commented on JENKINS-22934 Rules for showing/hiding SCMTrigger.pollingThreadCount option are broken Code changed in jenkins User: Daniel Beck Path: core/src/main/java/hudson/triggers/SCMTrigger.java core/src/main/resources/hudson/triggers/SCMTrigger/global.jelly http://jenkins-ci.org/commit/jenkins/7860c4e62003617c6fbb16d71c9eccfde9f10db7 Log: [FIXED JENKINS-22934] Show poll thread count option when necessary. Show the option when the configured value is not the default Show the option even when projects are in other ItemGroups Only consider AbstractProjects (cherry picked from commit e4902e7e8ab7a21e84ea21a36395b0e2a5077019) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
