[JIRA] (JENKINS-47333) file parameter not working in pipeline job
Title: Message Title Paolo Lambojon commented on JENKINS-47333 Re: file parameter not working in pipeline job Issue still persists today. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56748) Execution Report not triggered
Title: Message Title Daniel Gront assigned an issue to Roy Lu Jenkins / JENKINS-56748 Execution Report not triggered Change By: Daniel Gront Assignee: Daniel Gront Roy Lu Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-54018) NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled
Title: Message Title Owen Mehegan commented on JENKINS-54018 Re: NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled I have seen this issue in a situation where JDK Tools plugin was removed from a master where it had been installed and used. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-54018) NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-54018 NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled Change By: Owen Mehegan Summary: Exception on UI after Manually uploading Plugins NoClassDefFoundError: Lhudson/tools/JDKInstaller when JDK Tools plugin is uninstalled Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-54018) Exception on UI after Manually uploading Plugins
Title: Message Title Owen Mehegan assigned an issue to Devin Nusbaum Jenkins / JENKINS-54018 Exception on UI after Manually uploading Plugins Change By: Owen Mehegan Assignee: Bruno P. Kinoshita Devin Nusbaum Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-54018) Exception on UI after Manually uploading Plugins
Title: Message Title Owen Mehegan updated an issue Jenkins / JENKINS-54018 Exception on UI after Manually uploading Plugins Change By: Owen Mehegan Component/s: active-choices-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title Owen Mehegan commented on JENKINS-51307 Re: Declarative pipeline and docker entrypoint We have seen in two different cases that upgrading to 1.15.1 fixes this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51307) Declarative pipeline and docker entrypoint
Title: Message Title Owen Mehegan commented on JENKINS-51307 Re: Declarative pipeline and docker entrypoint We have seen in two different cases that upgrading to 1.15.1 fixes this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55605) can only click on the first active parallel stage, others running but cannot click
Title: Message Title Josh McDonald commented on JENKINS-55605 Re: can only click on the first active parallel stage, others running but cannot click I think I've got it solved without breaking anything It's a bit of a maze in that part of the codebase, and the issue was caused by some old code trying to grok the graph that was unaware of the relatively new support for sequential-stage parallel branches. PR here https://github.com/jenkinsci/blueocean-plugin/pull/1941 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51429) schedule-build-plugin - build with parameters
Title: Message Title Abhijeet Zope commented on JENKINS-51429 Re: schedule-build-plugin - build with parameters Martin Spielmann Thanks a lot. This helped me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-53840) job-dsl-plugin unknown protocol when use in dir with mixed separator
Title: Message Title
XiaoYao LingHu edited a comment on JENKINS-53840
Re: job-dsl-plugin unknown protocol when use in dir with mixed separator
[~daspilker] Only wrong in windows system and also use step ‘dir’ . { panel code:java }node { //not use step 'dir' writeFile file: 'foo/bar/test.groovy', text: 'job("example")' jobDsl targets: 'foo\\bar/test.groovy' //use step 'dir' no mixed separator dir("D:\\") { writeFile file: 'foo/bar/test.groovy', text: 'job("example")' jobDsl targets: 'foo\\bar/test.groovy' } //use step 'dir' with mixed separator dir("D:\\foo/bar") { writeFile file: 'test.groovy', text: 'job("example")' jobDsl targets: 'test.groovy' } } { panel code }{ panel code:java }Running in Durability level: MAX_SURVIVABILITY [Pipeline] nodeRunning nodeRunning on [ Jenkins |http://localhost:8080/computer/(master)/] in D:\Program\Jenkins\workspace\test [Pipeline] { [Pipeline] writeFile [Pipeline] jobDslProcessing jobDslProcessing DSL script test.groovyExisting items:GeneratedJob \ {name='example'} [Pipeline] dirRunning dirRunning in D:\ [Pipeline] { [Pipeline] writeFile [Pipeline] jobDslProcessing jobDslProcessing DSL script test.groovyExisting items:GeneratedJob \ {name='example'} [Pipeline] } [Pipeline] // dir [Pipeline] dirRunning dirRunning in D:\foo/bar [Pipeline] { [Pipeline] writeFile [Pipeline] jobDsl [Pipeline] } [Pipeline] // dir [Pipeline] } [Pipeline] // node [Pipeline] End of Pipelinejava Pipelinejava .net.MalformedURLException: unknown protocol: d at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source) { panel code }
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options,
[JIRA] (JENKINS-53840) job-dsl-plugin unknown protocol when use in dir with mixed separator
Title: Message Title XiaoYao LingHu assigned an issue to Daniel Spilker Additional comments Jenkins / JENKINS-53840 job-dsl-plugin unknown protocol when use in dir with mixed separator Change By: XiaoYao LingHu Assignee: XiaoYao LingHu Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-53840) job-dsl-plugin unknown protocol when use in dir with mixed separator
Title: Message Title
XiaoYao LingHu commented on JENKINS-53840
Re: job-dsl-plugin unknown protocol when use in dir with mixed separator
Daniel Spilker Only wrong in windows system and also use step ‘dir’.
node {
//not use step 'dir' writeFile file: 'foo/bar/test.groovy', text: 'job("example")' jobDsl targets: 'foobar/test.groovy'
//use step 'dir' no mixed separator dir("D:")
Unknown macro: { writeFile file}
//use step 'dir' with mixed separator dir("D:foo/bar")
Unknown macro: { writeFile file}
}
Running in Durability level: MAX_SURVIVABILITY[Pipeline] nodeRunning on Jenkins in D:\Program\Jenkins\workspace\test[Pipeline]
Unknown macro: {[Pipeline] writeFile[Pipeline] jobDslProcessing DSL script test.groovy Existing items}
[Pipeline] dirRunning in D:[Pipeline]
Unknown macro: {[Pipeline] writeFile[Pipeline] jobDslProcessing DSL script test.groovy Existing items}
[Pipeline] }[Pipeline] // dir[Pipeline] dirRunning in D:\foo/bar[Pipeline]
Unknown macro: {[Pipeline] writeFile[Pipeline] jobDsl[Pipeline] }
[Pipeline] // dir[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinejava.net.MalformedURLException: unknown protocol: d at java.net.URL.(Unknown Source) at java.net.URL.(Unknown Source)
[JIRA] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Olivier Lamy commented on JENKINS-56747 Re: Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Gil Br I need more details: You upgraded from which version? what is your java version? please note the coming 2.169 will have a new option to configure cipher (due to security issues recent version has been more strict regarding cipher list exclusion) (see https://github.com/eclipse/jetty.project/issues/2807 so this might the cause of your problem?) with coming 2.169 you will be able to change the cipher exclusion list see JENKINS-56591 ) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56591) make cipher exclusion configurable in Winstone
Title: Message Title Olivier Lamy commented on JENKINS-56591 Re: make cipher exclusion configurable in Winstone --excludeCipherSuites= set the ciphers to exclude (comma separated, use blank quote " " to exclude none) (default is // Exclude weak / insecure ciphers "^.*_(MD5|SHA|SHA1)$", // Exclude ciphers that don't support forward secrecy "^TLS_RSA_.*$", // The following exclusions are present to cleanup known bad cipher // suites that may be accidentally included via include patterns. // The default enabled cipher list in Java will not include these // (but they are available in the supported list). "^SSL_.*$", "^.*_NULL_.*$", "^.*_anon_.*$" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55503) Warnings trend graph (type distribution) portlet
Title: Message Title Ulli Hafner commented on JENKINS-55503 Re: Warnings trend graph (type distribution) portlet Sorry, this was a too short description indeed. In Jenkins dashboard view you currently configure the view by clicking edit. Then a new view opens where you (or the admin) can fill in the values of the view (dashboards, jobs, etc). Then you press SAVE and see the results. If I remember correctly, one user can create such view, and every other user uses the same configuration and cannot change it. On the other hand, the new warnings-ng details view (URL job/build/checkstyle as an example) show a new view with the issues table, pie charts and the history chart. This view can be configured by the user without opening a new configuration view. Just change the content of the accordion using < and > and the current visible chart will be stored for each user. There is no configuration screen. Now the question is: how should the configuration of the portlet work? Using the former or latter way? Or a combination of both? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56228) Job triggered multiple times by maven dependencies
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-56228 Re: Job triggered multiple times by maven dependencies PR merged [~amir_schnell] can you please test https://github.com/jenkinsci/pipeline-maven-plugin/releases/tag/pipeline-maven-3.6.8-beta-2 ? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title Brendan Holmes updated JENKINS-56739 Jenkins / JENKINS-56739 job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..." Change By: Brendan Holmes Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title Brendan Holmes closed an issue as Not A Defect Jenkins / JENKINS-56739 job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..." Change By: Brendan Holmes Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-43820) Stage name must be a string literal
Title: Message Title Adam BH commented on JENKINS-43820 Re: Stage name must be a string literal Since no response is being made by CloudBees my best guess is they wanted to encourage static stage names because the legacy build history (not BO, maybe others too) view shows history best when stages don't change names dynamically. Anyone who has ever changed stages over time knows their history on this view gets reset when doing. My use case for this wasn't to change the stage name(s) between builds but just to avoid some repeated strings with a variable used by a bool parameter (the key, not value), my label, and my stage name. I'll echo others, this feels rather arbitrary and the silence is more frustrating than 'No because X'...the key part being 'because X'. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-54735) Pipeline retry clause: optionally delay between retries
Title: Message Title
Adam Brousseau commented on JENKINS-54735
Re: Pipeline retry clause: optionally delay between retries
in response to the workaround, what about this...?
ret = false
retry(5) {
if (ret) {
sleep time: 30, unit: 'SECONDS'
} else {
ret = true
}
sh 'some-failure-prone-script'
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-41670) job not created when name ends with whitespace but no exception
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-41670 job not created when name ends with whitespace but no exception Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56737) Java compiler warnings parser can't cope with Maven timestamps in log
Title: Message Title Ulli Hafner assigned an issue to Unassigned Jenkins / JENKINS-56737 Java compiler warnings parser can't cope with Maven timestamps in log Change By: Ulli Hafner Assignee: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-43778) singleConditionalBuilder closure creates FATAL: null java.lang.StackOverFlow error using runner{ run() }
Title: Message Title
Daniel Spilker assigned an issue to Unassigned
Jenkins / JENKINS-43778
singleConditionalBuilder closure creates FATAL: null java.lang.StackOverFlow error using runner{ run() }
Change By:
Daniel Spilker
Assignee:
Daniel Spilker
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-56737) Java compiler warnings parser can't cope with Maven timestamps in log
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-56737 Java compiler warnings parser can't cope with Maven timestamps in log Change By: Ulli Hafner Component/s: analysis-model Component/s: analysis-model-api-plugin Labels: help-wanted newbie-friendly Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56737) Java compiler warnings parser can't cope with Maven timestamps in log
Title: Message Title Ulli Hafner commented on JENKINS-56737 Re: Java compiler warnings parser can't cope with Maven timestamps in log It does allow something in front of [WARNING] but that must be included in brackets. It is quite hard to solve that in general since the logger format could be changed to something completely different... But I think it should be possible to improve that regex to ignore everything before [WARNING]. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-52816) scm poll triggers even there is no change in repository(bitbucket)
Title: Message Title Daniel Spilker updated JENKINS-52816 Jenkins / JENKINS-52816 scm poll triggers even there is no change in repository(bitbucket) Change By: Daniel Spilker Status: Open Fixed but Unreleased Assignee: Daniel Spilker Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51211) FSTrigger Polling not working because of SecurityException
Title: Message Title Andy chu edited a comment on JENKINS-51211 Re: FSTrigger Polling not working because of SecurityException according to this post[https://jenkins.io/blog/2018/03/15/jep-200-lts/#applying-workarounds]You can "work around" the issue by providing the following JAVA opts and restart you Jenkins-Dhudson.remoting.ClassFilter=org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger , org.jenkinsci.lib.xtrigger.AbstractTrigger I try it on Plugin 0.39 and it seem to work for me. Hope this help Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56470) Support ssh_agent_plugin with ssh_steps_plugin
Title: Message Title Naresh Rayapati commented on JENKINS-56470 Re: Support ssh_agent_plugin with ssh_steps_plugin sshagent is injecting these credentials to native linux process running on the jenkins agent, which is going to be in memory and no one can hack it. These steps are designed to run commands on the remote nodes but not on the Jenkins agents, so I think it is a bit hacky to use sshagent step. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-50712) branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-50712 branchSources in MultibranchWorkflowJob and PipelineJob asking for vulnerable signature approvals when running in sandbox Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-53840) job-dsl-plugin unknown protocol when use in dir with mixed separator
Title: Message Title
Daniel Spilker assigned an issue to XiaoYao LingHu
I can not reproduce the problem. This pipeline script works for me:
node {
writeFile file: 'foo/bar/test.groovy', text: 'job("example")'
jobDsl targets: 'foo\\bar/test.groovy'
}
Started by user admin
Running as admin
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] node
Running on Jenkins in /var/jenkins_home/workspace/example-pipe
[Pipeline] {
[Pipeline] writeFile
[Pipeline] jobDsl
Processing DSL script foo/bar/test.groovy
Added items:
GeneratedJob{name='example'}
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
Finished: SUCCESS
Jenkins / JENKINS-53840
job-dsl-plugin unknown protocol when use in dir with mixed separator
Change By:
Daniel Spilker
Assignee:
Daniel Spilker XiaoYao LingHu
Add Comment
[JIRA] (JENKINS-53840) job-dsl-plugin unknown protocol when use in dir with mixed separator
Title: Message Title Daniel Spilker assigned an issue to Daniel Spilker Jenkins / JENKINS-53840 job-dsl-plugin unknown protocol when use in dir with mixed separator Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title Daniel Spilker updated JENKINS-56739 See https://github.com/jenkinsci/job-dsl-plugin/wiki/Migration#migrating-to-170 Jenkins / JENKINS-56739 job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..." Change By: Daniel Spilker Status: Open Fixed but Unreleased Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56228) Job triggered multiple times by maven dependencies
Title: Message Title Cyrille Le Clerc commented on JENKINS-56228 Re: Job triggered multiple times by maven dependencies PR merged Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-41715) Git credentials selection + git ls-remote test of config is wonky
Title: Message Title robert mundkowsky commented on JENKINS-41715 Re: Git credentials selection + git ls-remote test of config is wonky I have a very similar problem. If I use a SSH key with a passphrase then I get "Too many authentication failures for git" inconsistently. Some days it works and some days it does not. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51211) FSTrigger Polling not working because of SecurityException
Title: Message Title Andy chu commented on JENKINS-51211 Re: FSTrigger Polling not working because of SecurityException according to this post https://jenkins.io/blog/2018/03/15/jep-200-lts/#applying-workarounds You can "work around" the issue by providing the following JAVA opts and restart you Jenkins -Dhudson.remoting.ClassFilter=org.jenkinsci.plugins.fstrigger.triggers.FolderContentTrigger I try it on Plugin 0.39 and it seem to work for me. Hope this help Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56399) Performance plugin not filtering trend data
Title: Message Title Miccah Castorina commented on JENKINS-56399 Re: Performance plugin not filtering trend data Andrey Pokhilko any progress? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56750) Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test.
Title: Message Title Jim Sears created an issue Jenkins / JENKINS-56750 Micro Focus Application Automation Tools - Build log incorrect for multiple test instances of the same test. Issue Type: Bug Assignee: Carles Capdevila Attachments: build.log, RunResults.png, Tests about to run.png Components: log-file-filter-plugin Created: 2019-03-25 19:29 Environment: The Quality Center plug-in is 5.6.2. I had 5.7 installed but had an issue with a parameter "length cannot be zero" so I had to downgrade. That issue is affecting other users as well. My reporting issue happens in both 5.6.2 and .57. About Jenkins 2.150.1 Jenkins is a community-developed open-source automation server. Jenkins depends on the following 3rd party libraries Mavenized dependencies Name Maven ID License Jenkins war org.jenkins-ci.main:jenkins-war:2.150.1 The MIT license Utility around Java Crypto API org.jenkins-ci:crypto-util:1.1 MIT License HttpCommons Client library commons-httpclient:commons-httpclient:3.1-jenkins-1 Apache License 2.0 AOP alliance aopalliance:aopalliance:1.0 Public Domain Google Guice - Core Library com.google.inject:guice:4.0 The Apache Software License, Version 2.0 Agent installer module org.jenkins-ci.modules:slave-installer:1.6 MIT License Spring Framework: DAO org.springframework:spring-dao:1.2.9 The Apache Software License, Version 2.0 Apache Groovy org.codehaus.groovy:groovy-all:2.4.12 The Apache Software License, Version 2.0 Stapler Groovy module org.kohsuke.stapler:stapler-groovy:1.256 2-clause BSD license Constant Pool Scanner org.jenkins-ci:constant-pool-scanner:1.2 NetBeans CDDL/GPL jbcrypt org.connectbot.jbcrypt:jbcrypt:1.0.0 ISC SSH CLI client authenticator org.jenkins-ci.modules:ssh-cli-auth:1.4 MIT License ASM Commons org.ow2.asm:asm-commons:5.0.3 BSD Symbol annotation org.jenkins-ci:symbol-annotation:1.1 MIT License Jenkins core org.jenkins-ci.main:jenkins-core:2.150.1 The MIT license Windows agent installer org.jenkins-ci.modules:windows-slave-installer:1.9.2 MIT License Commons Digester commons-digester:commons-digester:2.1 The Apache Software License, Version 2.0 Java binding for libpam.so org.kohsuke:libpam4j:1.11 The MIT license Commons IO commons-io:commons-io:2.4 The Apache Software License, Version 2.0 jnr-posix com.github.jnr:jnr-posix:3.0.45 Eclipse Public License - v 1.0 GNU General Public License Version 2 GNU Lesser General Public License Version 2.1
[JIRA] (JENKINS-56605) Cannot use custom agent directive in Jenkinsfile
Title: Message Title David Rajnic commented on JENKINS-56605 Re: Cannot use custom agent directive in Jenkinsfile Andrew Bayer so there is no other way I can just simply wrap existing agent.docker directive into custom directive? The solution you've proposed seems quite a big for something that is already implemented in docker-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56009) Log audit events for user credentials
Title: Message Title Bhavika Rana assigned an issue to David Olorundare Jenkins / JENKINS-56009 Log audit events for user credentials Change By: Bhavika Rana Assignee: Bhavika Rana David Olorundare Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Christopher Smith edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Recently ran into issues with plugins and we did a update of all plugins. As soon as that was done this problem started occurring for us. Tried a bunch of workarounds so far and none of it seems to work. Adding the workaround Aaron suggested. Even manually deleting the contents of workspace myself doesn't seem to fix the issue either as the next time a job runs and goes to pull down a branch it fails due to permissions. My C:\Jenkins\workspace folder on the Slave node where these files should be being cleaned up is basically wide open right now with Everyone having full permission. I assume this is still related to some kind of lock?Note: The below should says {code:java} */.git/** {code} but the second asterisk isn't coming through.{panel}**/.git/** exclude and Apply pattern also on directories set in the Workspace Cleanup config in the job* [WS-CLEANUP] Deleting project workspace... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}{panel}**/.git/** exclude, Apply pattern also on directories, and Disable deferred wipeout set in the Workspace Cleanup config in the job* [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}
Add Comment
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Christopher Smith edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Recently ran into issues with plugins and we did a update of all plugins. As soon as that was done this problem started occurring for us. Tried a bunch of workarounds so far and none of it seems to work. Adding the workaround Aaron suggested. Even manually deleting the contents of workspace myself doesn't seem to fix the issue either as the next time a job runs and goes to pull down a branch it fails due to permissions. My C:\Jenkins\workspace folder on the Slave node where these files should be being cleaned up is basically wide open right now with Everyone having full permission. I assume this is still related to some kind of lock? Note: The below should says */.git/** but the second asterisk isn't coming through. {panel}**/.git/** exclude and Apply pattern also on directories set in the Workspace Cleanup config in the job*[WS-CLEANUP] Deleting project workspace... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}{panel}**/.git/** exclude, Apply pattern also on directories, and Disable deferred wipeout set in the Workspace Cleanup config in the job*[WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE{panel}
Add Comment
[JIRA] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title
Christopher Smith edited a comment on JENKINS-55836
Re: Unable to delete workspace due to locked git .pack file
Recently ran into issues with plugins and we did a update of all plugins. As soon as that was done this problem started occurring for us. Tried a bunch of workarounds so far and none of it seems to work. Adding the workaround Aaron suggested. Even manually deleting the contents of workspace myself doesn't seem to fix the issue either as the next time a job runs and goes to pull down a branch it fails due to permissions. My C:\Jenkins\workspace folder on the Slave node where these files should be being cleaned up is basically wide open right now with Everyone having full permission. I assume this is still related to some kind of lock? {panel :title= } * * /.git/** exclude and Apply pattern also on directories set in the Workspace Cleanup config in the job } * [WS-CLEANUP] Deleting project workspace...ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 eventsFinished: FAILURE{panel} {panel :title= } * * /.git/** exclude, Apply pattern also on directories, and Disable deferred wipeout set in the Workspace Cleanup config in the job } * [WS-CLEANUP] Deleting project workspace...[WS-CLEANUP] Deferred wipeout is disabled by the job configuration...ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts.sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 eventsFinished: FAILURE{panel}
Add Comment
[JIRA] (JENKINS-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title Craig Rodrigues commented on JENKINS-56672 Re: Artifacts tab in blue ocean does not have link to view an artifact The behavior of the browser is determined by what the server sends back in the HTTP Content-Type field, and also the internal list of mime-types in the browser. If you appends */view/* to a URL, it triggers this behavior in Jenkins: https://github.com/jenkinsci/jenkins/blob/master/core/src/main/java/hudson/model/DirectoryBrowserSupport.java#L308 It sets a pseudo-name to plain.txt, so that tricks the browser into trying to render the file in the browser. In my artifacts directory, I generate a lot of YAML files ending with .yml extension, so I want to be able to view them in the browser just like in the legacy UI, in addition to being able to download them. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-56747 Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Change By: Daniel Beck Labels: regression security Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56749) Default audit log destination does not work with mvn hpi:run
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-56749 Default audit log destination does not work with mvn hpi:run Issue Type: Bug Assignee: Unassigned Components: audit-log-plugin Created: 2019-03-25 18:46 Labels: newbie-friendly Priority: Minor Reporter: Matt Sicker When I run the plugin using mvn hpi:run, the audit log output goes to logs/audit.log instead of the expected location work/logs/audit.log. This bug is caused by log4j2.xml only checking for the environment variable named JENKINS_HOME when it should fall back to trying the system property named JENKINS_HOME as well before defaulting to the current directory. Add Comment
[JIRA] (JENKINS-28335) Step to run Git commands w/ credentials & tool (was: GitPublisher support)
Title: Message Title
Michael Beaumont edited a comment on JENKINS-28335
Re: Step to run Git commands w/ credentials & tool (was: GitPublisher support)
I think I've come up with a good workaround. We can set the following at the beginning of our build (declarative pipeline in a Github organization):{code:java}sh 'git config --local credential.helper "!p() { echo username=\\$GIT_USERNAME; echo password=\\$GIT_PASSWORD; }; p"'{code}See [git credential helpers|https://git-scm.com/docs/api-credentials#_credential_helpers] Then, when we want to use the credentials we can use a block like the following: {code:java}sh 'git tag -m "" ${VERSION_NUMBER}'withCredentials([ usernamePassword(credentialsId: 'github', usernameVariable: 'GIT_USERNAME', passwordVariable: 'GIT_PASSWORD')]) { sh 'git push origin ${VERSION_NUMBER}'}{code}This way we don't have to even repeat the URL for the {{origin}} remote, which is already set.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-55836) Unable to delete workspace due to locked git .pack file
Title: Message Title Christopher Smith commented on JENKINS-55836 Re: Unable to delete workspace due to locked git .pack file Recently ran into issues with plugins and we did a update of all plugins. As soon as that was done this problem started occurring for us. Tried a bunch of workarounds so far and none of it seems to work. Adding the workaround Aaron suggested. Even manually deleting the contents of workspace myself doesn't seem to fix the issue either as the next time a job runs and goes to pull down a branch it fails due to permissions. My C:\Jenkins\workspace folder on the Slave node where these files should be being cleaned up is basically wide open right now with Everyone having full permission. I assume this is still related to some kind of lock? /.git/* exclude and Apply pattern also on directories set in the Workspace Cleanup config in the job [WS-CLEANUP] Deleting project workspace... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE /.git/* exclude, Apply pattern also on directories, and Disable deferred wipeout set in the Workspace Cleanup config in the job [WS-CLEANUP] Deleting project workspace... [WS-CLEANUP] Deferred wipeout is disabled by the job configuration... ERROR: [WS-CLEANUP] Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. ERROR: Cannot delete workspace: Unable to delete 'C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\.git\FETCH_HEAD'. Tried 3 times (of a maximum of 3) waiting 0.1 sec between attempts. sent [C:\Jenkins\workspace\LabD_Build_Automation\Validate_LabD_VCSA\hpc_install20190320.log] to splunk in 1 events Finished: FAILURE
[JIRA] (JENKINS-43183) Can't see pipeline jobs in Global Build Stats
Title: Message Title Peter Carenza commented on JENKINS-43183 Re: Can't see pipeline jobs in Global Build Stats We're doing a KPI analysis on changes in builds over time and this is forcing us to record times manually. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-43183) Can't see pipeline jobs in Global Build Stats
Title: Message Title Peter Carenza updated an issue Jenkins / JENKINS-43183 Can't see pipeline jobs in Global Build Stats Change By: Peter Carenza Priority: Major Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-49567) Automatically support docker networks in pipelines with multiple containers
Title: Message Title
Ryan Desmond edited a comment on JENKINS-49567
Re: Automatically support docker networks in pipelines with multiple containers
This would be great, particularly with the deprecation of the {{--link}} option in docker.An alternative that would be a more purposeful with a sidecar pattern would be to have a function that surrounds any docker calls and switches each from the default network to a local one:{code:java}docker.withNetwork { docker.image('sidecar').withRun() { c-> docker.image('main').inside() { // do something with host "${c. id name }" } }}{code} Currently, I have a function that works around this: {code:java}def withDockerNetwork(Closure inner) {try { network_id networkId = UUID.randomUUID().toString()sh "docker network create ${ network_id networkId }"inner.call( network_id networkId )} finally {sh "docker network rm ${ network_id networkId }"}}{code}{code:java}withDockerNetwork{ n -> docker.image('sidecar').withRun("--network ${n} --name sidecar ") { c-> docker.image('main').inside("--network ${n}") { // do something with host " ${c.id} sidecar " } }} {code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-54676) Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished
Title: Message Title Devin Nusbaum updated JENKINS-54676 Jenkins / JENKINS-54676 Error Creating Flownodes causes Jenkins to not add to queue or mark builds finished Change By: Devin Nusbaum Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55287 Pipeline: Failure to load flow node: FlowNode was not found in storage for head Change By: Devin Nusbaum Summary: Pipeline Groovy plugin issue cause : Failure to jenkins process exit load flow node: FlowNode was not found in storage for head Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56748) Execution Report not triggered
Title: Message Title Fabio Zo created an issue Jenkins / JENKINS-56748 Execution Report not triggered Issue Type: Improvement Assignee: Daniel Gront Attachments: Cattura.PNG Components: hp-application-automation-tools-plugin Created: 2019-03-25 15:56 Environment: Win10, Jenkins 2.60.2.2, Labels: ALM automation Priority: Major Reporter: Fabio Zo Same as JENKINS-26002 , we would like to have the Execution Report triggered when "runFromAlmBuilder" clause is used in a Groovy script. Is it possible to have this working properly? Add Comment
[JIRA] (JENKINS-55170) Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Devin Nusbaum updated JENKINS-55170 Jenkins / JENKINS-55170 Failure to load flow node: FlowNode was not found in storage for head Change By: Devin Nusbaum Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55287) Pipeline Groovy plugin issue cause to jenkins process exit
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55287 Pipeline Groovy plugin issue cause to jenkins process exit Change By: Devin Nusbaum Summary: Pipeline Groovy pipeline plugin issue cause to jenkins process exit Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-55287) Groovy pipeline plugin issue cause to jenkins process exit
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-55287 Groovy pipeline plugin issue cause to jenkins process exit Change By: Devin Nusbaum Component/s: workflow-cps-plugin Component/s: groovy-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56672) Artifacts tab in blue ocean does not have link to view an artifact
Title: Message Title boris ivan commented on JENKINS-56672 Re: Artifacts tab in blue ocean does not have link to view an artifact I've always had mixed results re: that working even in the legacy UI, and found that it was client/chrome related, re: displaying the content vs downloading. I mention this because it's working for me right now with blueocean. If I click "artifacts" I see a list of 3 items: pipeline.log, and two .png files generated as screenshots from UI testing, that I publish with the 'archive the artifacts' functionality. Each of those 3 items is a link itself as far as the "filename" is concerned, To the right of the filename is size, and to the right of that is the icon/link (down arrow) for downloading. Each work as expected for me – clicking on the "filename" displays the object in the browser in a new tab pipeline.log shows all the build text, and the two .png files show the picture. If I click the download icon it will download it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Oleg Nenashev commented on JENKINS-56747 Re: Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Using the embedded Jenkins HTTPs engine is not really advised for Jenkins. Please consider using an external HTTPs endpoint powered by nginx or whatever. CC Olivier Lamy , might be related to the recent Winstone update Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-56747 Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Change By: Oleg Nenashev Component/s: core Component/s: security-inspector-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-40997) Add way to get locked resource name in pipeline
Title: Message Title
Chris Maes updated an issue
Jenkins / JENKINS-40997
Add way to get locked resource name in pipeline
Change By:
Chris Maes
https://issues.jenkins-ci.org/browse/JENKINS-34268 was closed implementing the possibility to lock a resources using a label in pipelines. But there is no syntax for knowing what the actually locked resource name is when using a pipeline and locking on a label. Specifically the proposed syntax from [https://github.com/jenkinsci/lockable-resources-plugin/pull/36] : ", variable: 'MY_VAR'" is missing.Our use case is that we wan't to specify a label containing node names for legacy builders that can't run the slave.jar (java7) anymore. We wan't want to lock a resource (host name) from the label and then ssh to that machine and execute some build steps. This works with the FreestyleJob functionality of "Reserved resources variable name".h4. SolutionIt is now possible to access the locked resource via an configurable environment variable.{code:java}lock(label: 'some_resource', variable: 'MY_VAR') { echo env.MY_VAR}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title dana j commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed Facing the same issue. Using Jenkins 2.167 & GitPlugin, a pipeline job without any webhook/notifiyCommit and Poll SCM (enabled to check for changes only on master every hour). However, a build is triggered nightly logging "Started by an SCM change" even though there are no changes. Mark Waite - tried out the 4 suggested workarounds, but no change in behavior. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56747) Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH
Title: Message Title Gil Br created an issue Jenkins / JENKINS-56747 Error: ERR_SSL_VERSION_OR_CIPHER_MISMATCH Issue Type: Bug Assignee: Gil Br Attachments: Chrome_SSL_HTTPS.jpg, FF_SSL_HTTPS.jpg, IE_SSL_HTTPS.jpg Components: security-inspector-plugin Created: 2019-03-25 13:37 Environment: Jenkins ver. 2.168 Linux, Chrome 73.0.3683.86, IE 11.112.17134.0, Firefox 67.0b4 (64-bit) Labels: security Priority: Major Reporter: Gil Br Jenkins ver. 2.168 Running from shell: java -jar jenkins.war --httpPort=-1 --httpsPort=8443 --httpsKeyStore=jenkin.jks --httpsKeyStorePassword=TopSecret Opening from Browser getting an error: Chrome: ERR_SSL_VERSION_OR_CIPHER_MISMATCH FireFox: Error code: SSL_ERROR_NO_CYPHER_OVERLAP IE: Your TLS security settings aren’t set to the defaults
[JIRA] (JENKINS-47676) Support personal access tokens for Bitbucket Server 5.5+
Title: Message Title Crystal Cox commented on JENKINS-47676 Re: Support personal access tokens for Bitbucket Server 5.5+ This is a problem which causes us it intervene manually, it should be fixed. We have several Jenkins job setup to run nightly automatic builds. Automated Build Issue: Bitbucket tends to lock the Jenkins user out and build fails every few weeks with require CAPTCHA error until Jenkins user logs into Bitbucket dashboard to do CAPTCHA and unlock account. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56746) Temp file GetJUnitTestResultsXXXXXXXXXX.tmp is not removed
Title: Message Title Radi Berkovich closed an issue as Fixed Jenkins / JENKINS-56746 Temp file GetJUnitTestResultsXX.tmp is not removed Change By: Radi Berkovich Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56746) Temp file GetJUnitTestResultsXXXXXXXXXX.tmp is not removed
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-56746 Temp file GetJUnitTestResultsXX.tmp is not removed Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-03-25 12:39 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56744) octane-sonar integration should support multispace configuration
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-56744 octane-sonar integration should support multispace configuration Change By: Radi Berkovich Summary: octane- sonar integration should support multispace configuration Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56745) octane-sonar integration should is not working with freestyle job
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-56745 octane-sonar integration should is not working with freestyle job Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-03-25 12:37 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56745) octane-sonar integration is not working with freestyle job
Title: Message Title Radi Berkovich updated an issue Jenkins / JENKINS-56745 octane-sonar integration is not working with freestyle job Change By: Radi Berkovich Summary: octane-sonar integration should is not working with freestyle job Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56538) Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Title: Message Title
Andrius Semionovas commented on JENKINS-56538
Re: Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Seems like I found a problem. I found failures happen because two parallel builds are using the same folder on slave machine: Success:
Started by upstream project "android-release-by-tag/v8.31.0.0" build number 1
originally caused by:
Push event for tag v8.31.0.0
13:55:46 Connecting to https://api.github.com using jenkins/** (Testing GitHub integration for multibranch pipelines)
Obtained Jenkinsfile from 9a50827efe20bbf7129e4c541f9057f10b0ec0e1
Running in Durability level: MAX_SURVIVABILITY
Loading library xxx-shared-libs@master
Attempting to resolve master from remote references...
> git --version # timeout=10
> git ls-remote -h g...@github.com:xxx/jenkins-shared-libs.git # timeout=10
Found match: refs/heads/master revision e1fb61690198e5d487ac3a56f96cc5bb35ec80cf
No credentials specified
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning repository g...@github.com:xxx/jenkins-shared-libs.git
> git init /var/lib/jenkins/workspace/android-release-by-tag_v8.31.0.0@libs/xxx-shared-libs@10 # timeout=10
Fetching upstream changes from g...@github.com:xxx/jenkins-shared-libs.git
> git --version # timeout=10
> git fetch --no-tags --progress g...@github.com:xxx/jenkins-shared-libs.git +refs/heads/*:refs/remotes/origin/*
> git config remote.origin.url g...@github.com:xxx/jenkins-shared-libs.git # timeout=10
> git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10
> git config remote.origin.url g...@github.com:xxx/jenkins-shared-libs.git # timeout=10
Fetching without tags
Fetching upstream changes from g...@github.com:xxx/jenkins-shared-libs.git
> git fetch --no-tags --progress g...@github.com:xxx/jenkins-shared-libs.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision e1fb61690198e5d487ac3a56f96cc5bb35ec80cf (master)
> git config core.sparsecheckout # timeout=10
> git checkout -f e1fb61690198e5d487ac3a56f96cc5bb35ec80cf
Commit message: "Merge pull request #34 from xxx/fix/mistyped_variable"
[Pipeline] Start of Pipeline
[Pipeline] node
Running on slave in /var/lib/jenkins/workspace/android-release-by-tag_v8.31.0.0@8
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Declarative: Checkout SCM)
[Pipeline] checkout
using credential github-jenkins-user
Fail:
Started by upstream project "android-release-by-tag/v8.31.0.0" build number 1
originally caused by:
Push event for tag v8.31.0.0
13:55:46 Connecting to https://api.github.com using jenkins/** (Testing GitHub integration for multibranch pipelines)
Obtained Jenkinsfile from 9a50827efe20bbf7129e4c541f9057f10b0ec0e1
Running in Durability level: MAX_SURVIVABILITY
Loading library xxx-shared-libs@master
Attempting to resolve master from remote references...
> git --version # timeout=10
> git ls-remote -h g...@github.com:xxx/jenkins-shared-libs.git # timeout=10
Found match: refs/heads/master revision e1fb61690198e5d487ac3a56f96cc5bb35ec80cf
No credentials specified
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
Cloning
[JIRA] (JENKINS-56744) sonar integration should support multispace configuration
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-56744 sonar integration should support multispace configuration Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-03-25 12:34 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56743) Add converter for protractor tests for testing framework
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-56743 Add converter for protractor tests for testing framework Issue Type: Improvement Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-03-25 12:33 Priority: Minor Reporter: Radi Berkovich Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56742) Support plugin Pipeline:Groovy Version 2.64
Title: Message Title Radi Berkovich created an issue Jenkins / JENKINS-56742 Support plugin Pipeline:Groovy Version 2.64 Issue Type: Bug Assignee: Radi Berkovich Components: hp-application-automation-tools-plugin Created: 2019-03-25 12:31 Priority: Minor Reporter: Radi Berkovich pipeline job shows 2 bars for a single pipeline run in Octane need to be fix as 1 bar Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-56538) Jenkins declarative pipelines sometimes is skipping "Checkout SCM"
Title: Message Title Andrius Semionovas updated an issue Jenkins / JENKINS-56538 Jenkins declarative pipelines sometimes is skipping "Checkout SCM" Change By: Andrius Semionovas Labels: docker pipeline race-condition scmworkflow Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title
Brendan Holmes updated an issue
Jenkins / JENKINS-56739
job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Change By:
Brendan Holmes
Hi,The below script works fine on job-dsl-plugin 1.71:{code:java}pipelineJob("restart_jenkins") { steps {systemGroovyScriptFile('import hudson.model.*; Hudson.instance.doSafeRestart(null);') {} }}{code}But fails to create a job on 1.72 with error: { noformat code:java }ERROR: (script, line 4) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types: (script$_run_closure1$_closure3) values: [script$_run_closure1$_closure3@6b5277ea]{ noformat code } Any ideas?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-56733) Add a button to copy the new API token
Title: Message Title Wadeck Follonier updated an issue Jenkins / JENKINS-56733 Add a button to copy the new API token Change By: Wadeck Follonier In the current implementation the API Tokens are proposed as text and the users must copy/paste them "manually". The proposal here is to add a "copy button" to ease/speed up such behavior. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56733) Add a button to copy the new API token
Title: Message Title Wadeck Follonier updated an issue Jenkins / JENKINS-56733 Add a button to copy the new API token Change By: Wadeck Follonier Summary: Add a button to copy the new API token Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56741) Calling CPS function in a script puts command executor in an odd state, making next command within that script fail
Title: Message Title
Jakub Pawlinski updated an issue
Jenkins / JENKINS-56741
Calling CPS function in a script puts command executor in an odd state, making next command within that script fail
Change By:
Jakub Pawlinski
Feel free to adjust the subject if you find better wording, what happens is: {code:java}pipeline {agent anystages {stage ('This will work') {steps {script {def jobs = Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.job.WorkflowJob)println "Found ${jobs.size()} jobs"}}} stage ('This will also work') {steps {script {bat "dir"}}} stage ('This will fail') {steps {script {def jobs = Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.job.WorkflowJob)println "Found ${jobs.size()} jobs"bat "dir"}}}}}{code}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-56741) Calling CPS function in a script puts command executor in an odd state, making next command within that script fail
Title: Message Title
Jakub Pawlinski created an issue
Jenkins / JENKINS-56741
Calling CPS function in a script puts command executor in an odd state, making next command within that script fail
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2019-03-25 11:54
Priority:
Critical
Reporter:
Jakub Pawlinski
Feel free to adjust the subject if you find better wording, what happens is:
pipeline {
agent any
stages {
stage ('This will work') {
steps {
script {
def jobs = Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.job.WorkflowJob)
println "Found ${jobs.size()} jobs"
}
}
}stage ('This will also work') {
steps {
script {
bat "dir"
}
}
}stage ('This will fail') {
steps {
script {
def jobs = Jenkins.instance.getAllItems(org.jenkinsci.plugins.workflow.job.WorkflowJob)
println "Found ${jobs.size()} jobs"
bat "dir"
}
}
}
}
}
[JIRA] (JENKINS-56740) Artifacts bigger than 5GB can't be uploaded to S3
Title: Message Title Artem V. Navrotskiy created an issue Jenkins / JENKINS-56740 Artifacts bigger than 5GB can't be uploaded to S3 Issue Type: Bug Assignee: Unassigned Components: artifact-manager-s3-plugin Created: 2019-03-25 11:53 Priority: Critical Reporter: Artem V. Navrotskiy Unfortunately S3 have 5GB limit for single operation upload object: https://docs.aws.amazon.com/AmazonS3/latest/dev/UploadingObjects.html Upload objects in a single operation—With a single PUT operation, you can upload objects up to 5 GB in size. Upload objects in parts—Using the multipart upload API, you can upload large objects, up to 5 TB. This plugin don't implement multipart upload and can't upload big files to S3. Add Comment
[JIRA] (JENKINS-54250) Disable restarting stages in jenkinsfile optionally
Title: Message Title
Chris Hemp commented on JENKINS-54250
Re: Disable restarting stages in jenkinsfile optionally
Previously I had the legacy UI hiding the "Restart from Stage" button with this css style (using the `simple-theme-plugin`):
/* Hide Restart from Stage */
a[href$="restart"] {display: none;}
This css style hiding solution was not an option in the Blue Ocean UI though. This helps, thanks Jonathan Sokolowski !
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-56739) job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Title: Message Title
Brendan Holmes created an issue
Jenkins / JENKINS-56739
job-dsl 1.72: "No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types..."
Issue Type:
Bug
Assignee:
Daniel Spilker
Components:
job-dsl-plugin
Created:
2019-03-25 11:32
Priority:
Minor
Reporter:
Brendan Holmes
Hi, The below script works fine on job-dsl-plugin 1.71:
pipelineJob("restart_jenkins") {
steps {
systemGroovyScriptFile('import hudson.model.*; Hudson.instance.doSafeRestart(null);') {}
}
}
But fails to create a job on 1.72 with error:
ERROR: (script, line 4) No signature of method: javaposse.jobdsl.dsl.jobs.WorkflowJob.steps() is applicable for argument types: (script$_run_closure1$_closure3) values: [script$_run_closure1$_closure3@6b5277ea]
Any ideas?
[JIRA] (JENKINS-56735) Builds hanging after pod start in version 1.14.9
Title: Message Title
Karol Gil updated an issue
Jenkins / JENKINS-56735
Builds hanging after pod start in version 1.14.9
Change By:
Karol Gil
We updated kubernetes plugin from version 1.14.3 to version 1.14.9. On version 1.14.3 everything was running smoothly and after upgrade to 1.14.9 when Jenkins is under heavy load (starting/running ~100 jobs/pods) we observe that builds are stuck right after pod start or after Git checkout (first step of our test pipelines).We have a step timeout after 30 minutes and those jobs that were stuck could not be killed and was stuck with the following log: {code:java} > git checkout -f 073a008e8e8fdad44c3d637a8b9e5995277724aeCancelling nested steps due to timeoutBody did not finish within grace period; terminating with extreme prejudice{code}Only hard kill with calling {{POST BUILD_URL/kill}} did stop the build.What is interesting, sometimes those builds did fail and asked for changing max connections to k8s API{code:java}Caused: java.io.IOException: Interrupted while waiting for websocket connection, you should increase the Max connections to Kubernetes API{code}We increased the setting gradually to up to 6 (sic!) and it did not solve the issue in any way. On other Jenkins instances running under not so heavy load there is no sign of the issue whatsoever. Can it be somehow related to expiring kubernetes clients introduced in 1.14.5?I'm guessing that may be the case, because everything is working smoothly after Jenkins restart for some time (~24 hours usually, but we had shorter time frames as well) and then everything for stuck. After killing all jobs and restarting Jenkins everything went back to normal - again for finite time. Downgrade to version 1.14.3 solved all the issues.Please let me know if any additional information should be provided.
Add Comment
[JIRA] (JENKINS-55745) Migrate from analysis-core to warnings-ng
Title: Message Title James Howe commented on JENKINS-55745 Re: Migrate from analysis-core to warnings-ng Perhaps you should've linked the conversation here before deciding there weren't enough replies. As far as I can see, of the two responses, one wanted A1 (just the warnings-ng parser) and the other wanted B. I'm in the former camp, and just need the reporting capability, and would favour all reporting being integrated. If there's a parser for warnings-ng, then I probably have no need for a separate dependency-check plugin. Is it possible you could provide the parser for warnings-ng as well as your planned implementation of option B? I'm guessing, given your experience, you'd have the least trouble producing it quickly. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56738) Double quoted string is evaluated as a command during pipeline run
Title: Message Title
Jakub Pawlinski created an issue
Jenkins / JENKINS-56738
Double quoted string is evaluated as a command during pipeline run
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline, pipeline-build-step-plugin
Created:
2019-03-25 10:39
Priority:
Major
Reporter:
Jakub Pawlinski
Configuring new pipeline job with below content:
pipeline {
agent any
stages {
stage ('PrintCommand') {
steps {
script {
def command = "try { println env.BUILD_NUMBER } catch (Exception ex) { println \"Error: ${ex.getMessage()}\" }"
println command
}
}
}
}
}
makes pipeline fail on start due to:
groovy.lang.MissingPropertyException: No such property: any for class: WorkflowScript
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.unwrap(ScriptBytecodeAdapter.java:53)
at org.codehaus.groovy.runtime.ScriptBytecodeAdapter.getProperty(ScriptBytecodeAdapter.java:458)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:290)
at org.kohsuke.groovy.sandbox.GroovyInterceptor.onGetProperty(GroovyInterceptor.java:68)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:348)
at org.kohsuke.groovy.sandbox.impl.Checker$6.call(Checker.java:288)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:292)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:268)
at
[JIRA] (JENKINS-56737) Java compiler warnings parser can't cope with Maven timestamps in log
Title: Message Title cristalp created an issue Jenkins / JENKINS-56737 Java compiler warnings parser can't cope with Maven timestamps in log Issue Type: Bug Assignee: Ulli Hafner Components: analysis-model-api-plugin Created: 2019-03-25 10:04 Priority: Minor Reporter: cristalp We switched on Maven timestamps in our log, since it's a handy way to check build times. In Maven, this is done by editing conf/logging/simplelogger.properties and setting org.slf4j.simpleLogger.showDateTime=true This results in compiler warnings like this: 08:52:34.395 [WARNING] /my/path/to/workspace/src/main/java/my/package/TemporalJsonSeqFiling.java:[86,76] redundant cast to long ( given that the date/time format is org.slf4j.simpleLogger.dateTimeFormat=HH:mm:ss.SSS ) Taking a look at the source code, it seems that JAVAC_WARNING_PATTERN does a full match of the line, which does not accept that something could exist before [WARNING] . We use other parsers for Checkstyle, PMD etc. and they work fine.
[JIRA] (JENKINS-56736) strage behavior of manager.logContains() API in Groovy Post Build plugin
Title: Message Title
Geanina Sz created an issue
Jenkins / JENKINS-56736
strage behavior of manager.logContains() API in Groovy Post Build plugin
Issue Type:
Task
Assignee:
Stefan Wolf
Components:
groovy-postbuild-plugin
Created:
2019-03-25 09:42
Priority:
Major
Reporter:
Geanina Sz
Hi, Trying to use Groovy Post build plugin in order to parse build output log in reverse order. manager.logContains seems not to be suitable for my since it always parse the log from the begging and I am using a variable in my scripted pipeline as a matcher which needs to be updated with latest value found in the console output. This seems not to be happening. The scenario is: in the same build log I have several text lines like: Failed: *. In case I find Failed: 0, I do something, in case of Failed: anything but 0, I do something else. Using: if(manager.logContains(".Failed: 0.")) {if(manager.logContains(".Failed: 0.")) { println "No failure" println "+ ${manager.logContains(".Failed: 0.")}" } else if(matcher?.matches()){ echo 'Matches!!' buildMsg=matcher.group(1).toInteger() if ((buildMsg - failure)> 0) { println 'There are tests failed!' // manager.buildUnstable() throw new RuntimeException("Failed") } } this does not work properly. Can you please help to solve this? Thank you!
[JIRA] (JENKINS-41894) deleteDir() for cwd removes workspace when run in docker.image('builder').inside
Title: Message Title
Zaphod Beeblebrox commented on JENKINS-41894
Re: deleteDir() for cwd removes workspace when run in docker.image('builder').inside
As above, echo Jon B. I had a scripted pipline, converted it to a declarative (is there a good reason to still?) and found that deleteDir() hoses the working folder. I semantically wanted a cleanWorkspace() method, for newbies to groovy ; a better docs description of each method?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] (JENKINS-56735) Builds hanging after pod start in version 1.14.9
Title: Message Title Karol Gil created an issue Jenkins / JENKINS-56735 Builds hanging after pod start in version 1.14.9 Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2019-03-25 09:20 Environment: EKS version 1.11.8 Jenkins version 2.164.1 Kubernetes Plugin version 1.14.9 Java version 8 Jenkins installation from Helm chart Jenkins running with following JVM args: -Dkubernetes.websocket.ping.interval=3 -Dkubernetes.websocket.timeout=1 These were introduced due to reoccurring socket timeouts and did solve the issue. Labels: kuberenetes-plugin kubernetes plugin jenkins Priority: Major Reporter: Karol Gil We updated kubernetes plugin from version 1.14.3 to version 1.14.9. On version 1.14.3 everything was running smoothly and after upgrade to 1.14.9 when Jenkins is under heavy load (starting/running ~100 jobs/pods) we observe that builds are stuck right after pod start or after Git checkout (first step of our test pipelines). We have a step timeout after 30 minutes and those jobs that were stuck could not be killed and was stuck with the following log: > git checkout -f 073a008e8e8fdad44c3d637a8b9e5995277724ae Cancelling nested steps due to timeout Body did not finish within grace period; terminating with extreme prejudice
[JIRA] (JENKINS-55503) Warnings trend graph (type distribution) portlet
Title: Message Title Robin Jansohn commented on JENKINS-55503 Re: Warnings trend graph (type distribution) portlet I'm not sure if I can completely follow what you are asking/suggesting here. What exactly do you mean with dashboard, edit and details view? I guess edit view is where we can select and configure the different portlets, right? Dashboard view is probably where the portlets are actually shown. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-46354) Retry in Declarative options skips retried stages due to earlier failure
Title: Message Title Atharva Inamdar commented on JENKINS-46354 Re: Retry in Declarative options skips retried stages due to earlier failure Andrew, thanks for working on this. Is there a workaround available until this issue is fixed? Currently, we have to manually restart the build which isn't great. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-47375) Separate configurations containing JAR and JPI dependencies
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-47375 Separate configurations containing JAR and JPI dependencies Change By: Daniel Spilker Assignee: Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-33336) Cannot debug with gradlew server while org.gradle.daemon = true
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-6 Cannot debug with gradlew server while org.gradle.daemon = true Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-51620) generateLicenseInfo fails with ivy repositories
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-51620 generateLicenseInfo fails with ivy repositories Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-48812) Developer guide for gradle-jpi-plugin
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-48812 Developer guide for gradle-jpi-plugin Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-47375) Separate configurations containing JAR and JPI dependencies
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-47375 Separate configurations containing JAR and JPI dependencies Change By: Daniel Spilker Assignee: Daniel Spilker Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-35401) Need equivalent to mvn release:prepare
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-35401 Need equivalent to mvn release:prepare Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-42398) Build fails for empty project
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-42398 Build fails for empty project Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-33209) Implement debugging similar to the Gretty plugin
Title: Message Title Daniel Spilker assigned an issue to Steve Hill Jenkins / JENKINS-33209 Implement debugging similar to the Gretty plugin Change By: Daniel Spilker Assignee: Daniel Spilker Steve Hill Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] (JENKINS-56734) After upgrading jenkins from 2.60 to 2.150.3, we are seeing one alignment issue in the console log when we are running 2 stages parallelly in a pipeline job
Title: Message Title Saheta B updated an issue Jenkins / JENKINS-56734 After upgrading jenkins from 2.60 to 2.150.3, we are seeing one alignment issue in the console log when we are running 2 stages parallelly in a pipeline job Change By: Saheta B Summary: Afterupgrading After upgrading jenkins from 2.60 to 2.150.3, we are seeing one alignment issue in the console log when we are running 2 stages parallelly in a pipeline job Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
