[JIRA] (JENKINS-58839) NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent
Title: Message Title Christian Köberl created an issue Jenkins / JENKINS-58839 NPE in GitLabMergeRequestSCMEvent and GitLabPushSCMEvent Issue Type: Bug Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-07 05:55 Environment: Jenkins 2.176.2, Linux, Master + 10+ Slaves gitlab-branch-source 0.0.6-beta.5C Priority: Minor Reporter: Christian Köberl We get a NullPointerException on every hook event with the current version of gitlab-branch-source (0.0.6-beta.5C). 07-Aug-2019 07:39:52.137 WARNING [class io.jenkins.plugins.gitlabbranchsource.GitLabMergeRequestSCMEvent Wed Aug 07 07:39:52 CEST 2019 / SCMEvent [#4]] jenkins.scm.api.SCMHeadEvent$DispatcherImpl.log SCMEventListener.onSCMHeadEvent(SCMHeadEvent) jenkins.branch.OrganizationFolder$SCMEventListenerImpl@6e03b818 propagated an exception java.lang.NullPointerException at io.jenkins.plugins.gitlabbranchsource.GitLabMergeRequestSCMEvent.isMatch(GitLabMergeRequestSCMEvent.java:59) at io.jenkins.plugins.gitlabbranchsource.AbstractGitLabSCMHeadEvent.isMatch(AbstractGitLabSCMHeadEvent.java:22) at jenkins.branch.OrganizationFolder$SCMEventListenerImpl.onSCMHeadEvent(OrganizationFolder.java:1062) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:246) at jenkins.scm.api.SCMHeadEvent$DispatcherImpl.fire(SCMHeadEvent.java:229) at jenkins.scm.api.SCMEvent$Dispatcher.run(SCMEvent.java:505) at
[JIRA] (JENKINS-37862) Extract build symlink handling to a plugin
Title: Message Title Merten Schumann commented on JENKINS-37862 Re: Extract build symlink handling to a plugin ... Copy Artifact plugin, one approach, sure we've got (the same) scripts running in Hud aeh Jenkins + in other environments - Ux shell or Cygwin - and then it's good not to say required to have the same preconditions, I mean, just copy command instead of a plugin available in Jenkins environment "only" ... I've got a question: so when I upgrade Jenkins to a newer release with this behavior for new builds no symlinks will be created (as long as the Build Symlink plugin is not installed/active) - what about existing builds? Will Jenkins remove all the symlinks from existing builds after the upgrade? Hopefully only when the "Manage Old Data" action is invoked ... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174000.1472663694000.9487.1565156760745%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Ahmad Ubaidillah commented on JENKINS-58822 Re: Failed to send out e-mail Hi Alex Earl so what would you suggest for me so that this error does not occur? I am still new use jenkins 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9484.1565154240251%40Atlassian.JIRA.
[JIRA] (JENKINS-58838) Browsers not launching through Jenkins
Title: Message Title
Sharathkumar K G created an issue
Jenkins / JENKINS-58838
Browsers not launching through Jenkins
Issue Type:
Task
Assignee:
Victor Martinez
Components:
jenkinslint-plugin, jenkinswalldisplay
Created:
2019-08-07 05:02
Environment:
Jenkins, python
Labels:
plugin jenkins python trigger browser
Priority:
Major
Reporter:
Sharathkumar K G
We are experiencing an issue when running Python Script via Jenkins, the browsers refuse to open up the URL, however, when we run them manually, then it works. Pre Requirement: Firstly, Need to create a project in Jenkins. Next, In the project configuration-> Build section need to add below details. For example:- cd python .py My Python Sample Script: import webbrowser import subprocess mycmd = r'start chrome /new-tab {}'.format("https://outlook.office.com") n2 = subprocess.Popen(mycmd, shell=True, stdin=subprocess.PIPE, stdout=subprocess.PIPE) post-execution process: Firstly, go to the Jenkins project and click on Build Now option. Expected Result: Default browser should be open along with given URL. Issue: The script is running successfully but browser not opening. Note: If you run python script via cmd prompt or any IDE works perfectly.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Alex Earl commented on JENKINS-58822 Re: Failed to send out e-mail I don't think this is a Mailer issue either though, I think it's a configuration 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9480.1565153160118%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Alex Earl assigned an issue to Adrien Lecharpentier Jenkins / JENKINS-58822 Failed to send out e-mail Change By: Alex Earl Assignee: Alex Earl Adrien Lecharpentier 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9477.1565153100458%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Alex Earl updated an issue Jenkins / JENKINS-58822 Failed to send out e-mail Change By: Alex Earl Component/s: mailer-plugin Component/s: email-ext-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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9474.1565153100386%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Alex Earl commented on JENKINS-58822 Re: Failed to send out e-mail You have the wrong component anyway, you are using the Mailer plugin. hudson.tasks.Mailer$DescriptorImpl.doSendTestMail(Mailer.java:613) 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9472.1565153100356%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Ahmad Ubaidillah edited a comment on JENKINS-58822 Re: Failed to send out e-mail Hi [~slide_o_mix] I have followed instruction.this my setting on Gmail security setting https://www.loom.com/share/22e04823e3e349c18368a743b3363995.and this my setting on Jenkins https://www.loom.com/share/1cae4ae80b0249a6a77ac048b92d5705 before I used Jenkins.war which I always run through the terminal, everything went fine until then I decided to delete Jenkins.war on my laptop, and finally, I install it via homebrew.and this problem ensued 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9470.1565150580104%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Ahmad Ubaidillah commented on JENKINS-58822 Re: Failed to send out e-mail Hi Alex Earl I have followed instruction. this my setting on Gmail security setting https://www.loom.com/share/22e04823e3e349c18368a743b3363995. and this my setting on Jenkins https://www.loom.com/share/1cae4ae80b0249a6a77ac048b92d5705 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.9468.1565150400171%40Atlassian.JIRA.
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title
Paul Clark updated an issue
Jenkins / JENKINS-58837
withDockerRegistry on multiple clusters
Change By:
Paul Clark
Following instructions on [https://github.com/openshift/jenkins-client-plugin#moving-images-cluster-to-cluster], I am unable to promote the image between two openshift clusters as it throws an authentication issue.Adding a sleep after the two withDockerRegistry calls, I can see that two folders are created under the @TMP directory (unique names for each) with a config.json under each of them - these contain the authentication details to the respective registries. Docker-commons-plugin version: 1.15Docker plugin version: 1.1.7Openshift Client plugin version: 1.0.31 (openshift client and docker registry version: 3.7.119)Jenkins: 2.176.2 {code:java} [Pipeline] { (Copy from source to dest) [Pipeline] script [Pipeline] { [Pipeline] withDockerRegistry $ docker login -u openshift/skopeo -p [ https://docker-registry-default. |https://docker-registry-default.infra.ocp-reg.hbs.net.au/] Login Succeeded [Pipeline] { [Pipeline] withDockerRegistry $ docker login -u ci-cd/jenkins -p [ https://docker-registry. |https://docker-registry.apps.ocp-tst.hbs.net.au/] Login Succeeded [Pipeline] { [Pipeline] sh + /bin/oc image mirror --insecure=true docker-registry./appversion/appversion:latest docker-registry-default./appversion/appversion:latesterror: unable to retrieve source image docker-registry./appversion/appversion by tag: unauthorized: authentication required [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // withDockerRegistry [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // node [Pipeline] End of PipelineERROR: script returned exit code 1Finished: FAILURE{code}
Add Comment
[JIRA] (JENKINS-58837) withDockerRegistry on multiple clusters
Title: Message Title
Paul Clark created an issue
Jenkins / JENKINS-58837
withDockerRegistry on multiple clusters
Issue Type:
Bug
Assignee:
Nicolas De Loof
Components:
docker-commons-plugin, docker-plugin, openshift-client-plugin
Created:
2019-08-07 03:31
Priority:
Minor
Reporter:
Paul Clark
Following instructions on https://github.com/openshift/jenkins-client-plugin#moving-images-cluster-to-cluster, I am unable to promote the image between two openshift clusters as it throws an authentication issue. Adding a sleep after the two withDockerRegistry calls, I can see that two folders are created under the @TMP directory (unique names for each) with a config.json under each of them - these contain the authentication details to the respective registries. Docker-commons-plugin version: 1.15 Docker plugin version: 1.1.7 Openshift Client plugin version: 1.0.31 (openshift client and docker registry version: 3.7.119) Jenkins: 2.176.2 [Pipeline] { (Copy from source to dest)[Pipeline] script[Pipeline] {[Pipeline] withDockerRegistry$ docker login -u openshift/skopeo -p https://docker-registry-default.Login Succeeded[Pipeline] {[Pipeline] withDockerRegistry$ docker login -u ci-cd/jenkins -p https://docker-registry.Login Succeeded[Pipeline] {[Pipeline] sh+ /bin/oc image mirror --insecure=true docker-registry./appversion/appversion:latest docker-registry-default./appversion/appversion:latest error: unable to retrieve source image docker-registry./appversion/appversion by tag: unauthorized: authentication required[Pipeline] } [Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // withDockerRegistry[Pipeline] }[Pipeline] // script[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // node
[JIRA] (JENKINS-58479) Failing to retrieve teams
Title: Message Title Paul Clark assigned an issue to Paul Clark Jenkins / JENKINS-58479 Failing to retrieve teams Change By: Paul Clark Assignee: Sam Gleske Paul Clark 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.9462.1565147700399%40Atlassian.JIRA.
[JIRA] (JENKINS-24548) Write a plugin that adds HTTP Strict-Transport-Security header for better security
Title: Message Title Jason Miller commented on JENKINS-24548 Re: Write a plugin that adds HTTP Strict-Transport-Security header for better security Kalle Niemitalo for my use case, no. I am using jenkins:lts on an Amazon Web Services ECS cluster backed by Elastic File System (NFS) for Jenkins' file system. It is fronted by an AWS load balancer. We have a requirement to return the HSTS header. I tried loading the HSTS filter plugin and it crashed the container. I had to get into the file system to remove the plugin manually for it to restart. This is a fairly common requirement in many IT situations. I'm faced with either increasing complexity in the architecture to meet this requirement or modify the container to somehow get the servlet to return this header. A working plugin would be nice, or just an option. I visited the github page for the plugin and it appears that project is no longer maintained. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.154182.1395923468000.9430.1565134560558%40Atlassian.JIRA.
[JIRA] (JENKINS-58836) Wrong spanish argentinian translation for 'logout'
Title: Message Title Gabriel Belingueres created an issue Jenkins / JENKINS-58836 Wrong spanish argentinian translation for 'logout' Issue Type: Improvement Assignee: Unassigned Components: _unsorted Created: 2019-08-06 23:35 Labels: user-experience Priority: Minor Reporter: Gabriel Belingueres The 'logout' action link of Jenkins (top right corner) is wrong in the layout_es_AR.properties file. The current translation is 'Volver al proyecto', meaning 'Back to the project'. It should say 'Desconectar'. Add Comment
[JIRA] (JENKINS-58479) Failing to retrieve teams
Title: Message Title Kote Mushegiani commented on JENKINS-58479 Re: Failing to retrieve teams Sam Gleske so, should I be able to input `ORGNAME*Engineering`? I tried this and it throws the same error. The team is called "Engineering" in Github UI, and is referenced as `@ORGNAME/engineering`. I guess that's the slug? The url for the team is https://github.com/orgs/ORGNAME/teams/engineering 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200615.1562956253000.9424.1565132820122%40Atlassian.JIRA.
[JIRA] (JENKINS-58586) Pipeline "currentBuild" should expose project description
Title: Message Title Stuart Rowe updated JENKINS-58586 Jenkins / JENKINS-58586 Pipeline "currentBuild" should expose project description Change By: Stuart Rowe Status: In Review Closed Resolution: Won't Do 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200742.1563735527000.9422.1565132160208%40Atlassian.JIRA.
[JIRA] (JENKINS-21104) Confluence Publisher Plugin ignores Jenkins proxy settings
Title: Message Title Peter Cummuskey commented on JENKINS-21104 Re: Confluence Publisher Plugin ignores Jenkins proxy settings Currently affecting version 2.0.3 at the moment, though it was working before upgrade. Will downgrade to 2.0.1 and see if the issue persists. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.152666.1387529933000.9416.1565131920546%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Josh McDonald assigned an issue to Unassigned Jenkins / JENKINS-38339 UI for downstream jobs launched with 'build' step Change By: Josh McDonald Assignee: Josh McDonald 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9356.1565131864911%40Atlassian.JIRA.
[JIRA] (JENKINS-58835) recognize file's encodings
Title: Message Title Ilguiz Latypov commented on JENKINS-58835 Re: recognize file's encodings Related to JENKINS-53901. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201150.1565131115000.9354.1565131260050%40Atlassian.JIRA.
[JIRA] (JENKINS-58835) recognize file's encodings
Title: Message Title Ilguiz Latypov created an issue Jenkins / JENKINS-58835 recognize file's encodings Issue Type: Improvement Assignee: Unassigned Components: workflow-basic-steps-plugin Created: 2019-08-06 22:38 Priority: Minor Reporter: Ilguiz Latypov It would be nice if the readFile basic step could recognize the file's encoding. (Writing a file with writeFile can store a BOM at the beginning to help in recognizing the character set later, but this must be only a non-default option to preserve backward compatibility with earlier groovy code reading the created files. This agrees with a rule of thumb "accept liberally, produce conservatively"). There is no need to reinvent the wheel. Using (and white-listing) groovy.util.CharsetToolkit can make this easy. https://github.com/groovy/groovy-core/blob/GROOVY_2_4_X/src/main/groovy/util/CharsetToolkit.java#L388 http://docs.groovy-lang.org/latest/html/api/groovy/util/CharsetToolkit.html#getReader() https://github.com/jenkinsci/workflow-basic-steps-plugin/blob/workflow-basic-steps-2.18/src/main/java/org/jenkinsci/plugins/workflow/steps/ReadFileStep.java Add Comment
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Steve Ims commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page 0.33 working for me too. Thanks Sam Gleske ! 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.9318.1565128741040%40Atlassian.JIRA.
[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version
Title: Message Title Basil Crow commented on JENKINS-58716 Re: Failure to check out specified tag for incremental version I am not so sure. git remote -v in a forked PR build shows https://github.com/jenkinsci/XXX-plugin.git. This is because Jenkins first clones the origin repo at master, then merges in the PR head. Ah, that's unfortunate. However, the information we need is exposed by the CHANGE_FORK environment variable, although today it only consists of the username and not necessarily the repository name. However, JENKINS-58450 seeks to rectify that by setting CHANGE_FORK to $user/$repo when the repository name of the fork differs from the upstream repository name. Given the above, I think we could check CHANGE_FORK from git-changelist-maven-extension. If it's just a username, we can update githubRepo to the username from CHANGE_FORK and the repository name from the original value of githubRepo. If it's a username and a repository (post-JENKINS-58450), we can update gitHubRepo to the value of CHANGE_FORK verbatim. What do you think? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201008.1564430335000.9315.1565127300182%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev edited a comment on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Yeah, Probably you can use CpsThread or CpsGroovyShellFactory without sandbox flag - but we're worrying about the security - and don't allow modules/scripts to be used with the shared library permissions. We preparing pipelines in the shared library (because pipelines are common) and executing their logic (stored in modules) again in the sandbox with help of the CpsGroovyShell.Just `evaluate()` is almost the same - but the reason to use a separated CpsGroovyShell - is to enclave the script and to bind a special variables (`CFG` from the MPLModule.groovy).Yeah, it's low priority, but there is a way to move such messages into the jenkins master log for example? I think it's not a useful message for the ones, who actually want to see the build log... What do you think about the solutions? Maybe I can help with the implementation? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9313.1565127240189%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Yeah, `evaluate()` is almost the same - but the reason to use a separated CpsGroovyShell - is to enclave the script and to bind a special variables (`CFG` from the MPLModule.groovy). Yeah, it's low priority, but there is a way to move such messages into the jenkins master log for example? I think it's not a useful message for the ones, who actually want to see the build log... 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9310.1565126880242%40Atlassian.JIRA.
[JIRA] (JENKINS-58684) Linux max task resource exhaustion after excessive timer thread creation
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-58684 Linux max task resource exhaustion after excessive timer thread creation Change By: Olivier Lamy Assignee: Olivier Lamy 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200967.156416397.9284.1565125560349%40Atlassian.JIRA.
[JIRA] (JENKINS-58834) pipeline multi-agent configure unexpected error
Title: Message Title leslie leslie closed an issue as Not A Defect human mistake Jenkins / JENKINS-58834 pipeline multi-agent configure unexpected error Change By: leslie leslie Status: Open Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201149.1565122766000.9275.1565125320352%40Atlassian.JIRA.
[JIRA] (JENKINS-41045) Support ExtendedChoiceParameterDefinition plugin
Title: Message Title Leandro Garcia updated an issue Jenkins / JENKINS-41045 Support ExtendedChoiceParameterDefinition plugin Change By: Leandro Garcia 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1484248326000.9265.1565124780638%40Atlassian.JIRA.
[JIRA] (JENKINS-41045) Support ExtendedChoiceParameterDefinition plugin
Title: Message Title Leandro Garcia commented on JENKINS-41045 Re: Support ExtendedChoiceParameterDefinition plugin Please fix it, we need 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.19.1484248326000.9254.1565124670528%40Atlassian.JIRA.
[JIRA] (JENKINS-58834) pipeline multi-agent configure unexpected error
Title: Message Title
leslie leslie updated an issue
Jenkins / JENKINS-58834
pipeline multi-agent configure unexpected error
Change By:
leslie leslie
Unexpected error from pipeline configure below{code:java}pipeline {agent none stages {stage('test1') {agent {docker 'centos:centos7'args '-u root'}steps {sh 'pwd'sh 'whoami' sh 'ansible --version' }}stage('test2') {agent {docker 'centos:latest'}steps {echo 'test2'}}}}{code}Error message{code:java}Started by user adminRunning in Durability level: MAX_SURVIVABILITYorg.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:WorkflowScript: 5: Only one agent type is allowed per agent section @ line 5, column 13. agent { ^WorkflowScript: 5: No agent type specified. Must be one of [any, docker, dockerfile, label, none] @ line 5, column 13. agent { ^2 errors at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310) at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085) at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603) at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581) at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558) at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298) at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268) at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688) at groovy.lang.GroovyShell.parse(GroovyShell.java:700) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142) at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:320) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429)Finished: FAILURE{code}
[JIRA] (JENKINS-58834) pipeline multi-agent configure unexpected error
Title: Message Title
leslie leslie created an issue
Jenkins / JENKINS-58834
pipeline multi-agent configure unexpected error
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
docker, groovy-plugin, pipeline
Created:
2019-08-06 20:19
Environment:
OS: Centos 7 Docker ver. 18.09.7 Jenkins ver. 2.176.2
Labels:
jenkins pipline docker agents stage
Priority:
Major
Reporter:
leslie leslie
Unexpected error from pipeline configure below
pipeline {
agent none
stages {
stage('test1') {
agent {
docker 'centos:centos7'
args '-u root'
}
steps {
sh 'pwd'
sh 'whoami'
sh 'ansible --version'
}
}
stage('test2') {
agent {
docker 'centos:latest'
}
steps {
echo 'test2'
}
}
}
}
Error message
Started by user admin
Running in Durability level: MAX_SURVIVABILITY
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
[JIRA] (JENKINS-55582) Convert modules to plugins
Title: Message Title Jesse Glick commented on JENKINS-55582 Re: Convert modules to plugins I have a to-do item to write this up a JEP by the way. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196747.1547487122000.9231.1565122680155%40Atlassian.JIRA.
[JIRA] (JENKINS-58537) Plugin Version Must Be Exact
Title: Message Title Natasha Stopa updated JENKINS-58537 Closing this since tool should throw error if users enter the wrong version. After some discussion, it seemed like the case where there's a mismatch between the version of the dependency listed and the actual plugin probably shouldn't happen that often and is probably an error with the plugin that listed the dependencies that should be addressed. Jenkins / JENKINS-58537 Plugin Version Must Be Exact Change By: Natasha Stopa Status: In Review 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. To view this discussion on the web visit
[JIRA] (JENKINS-58537) Plugin Version Must Be Exact
Title: Message Title Natasha Stopa commented on JENKINS-58537 Re: Plugin Version Must Be Exact See: https://github.com/jenkinsci/plugin-installation-manager-tool/pull/59 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200686.1563406372000.9227.1565122560529%40Atlassian.JIRA.
[JIRA] (JENKINS-58537) Plugin Version Must Be Exact
Title: Message Title Natasha Stopa updated JENKINS-58537 Jenkins / JENKINS-58537 Plugin Version Must Be Exact Change By: Natasha Stopa Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200686.1563406372000.9223.1565122380112%40Atlassian.JIRA.
[JIRA] (JENKINS-58537) Plugin Version Must Be Exact
Title: Message Title Natasha Stopa started work on JENKINS-58537 Change By: Natasha Stopa Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200686.1563406372000.9222.1565122320089%40Atlassian.JIRA.
[JIRA] (JENKINS-55582) Convert modules to plugins
Title: Message Title Basil Crow commented on JENKINS-55582 Re: Convert modules to plugins Or, alternatively, do none of this…? I think this is worth doing. Right now, it's more or less impossible for plugins to depend on modules in a sane way (see the discussion in jenkinsci/git-server-plugin#10 to see what I mean). With this change in place, plugins could explicitly depend on the correct version of the "module" (turned plugin) that they need. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196747.1547487122000.9221.1565121900618%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title
Jesse Glick commented on JENKINS-58620
Re: MPL shared library logic execution caused CPS mismatch warning
I suspect this issue has nothing to do with libraries per se and could be reproduced in a self-contained Jenkinsfile. Maybe
def ex = CpsThread.current().execution
new CpsGroovyShellFactory(ex).withParent(ex.shell).build().evaluate('echo "OK"', 'X.groovy')
or maybe even just
evaluate('echo "OK"', 'X.groovy')
since I think existing tests only cover the overload taking only a single String parameter. If so, it is a bug somewhere in the way evaluate is being handled, and is probably very easy to fix in groovy-cps.
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9217.1565121600753%40Atlassian.JIRA.
[JIRA] (JENKINS-38339) UI for downstream jobs launched with 'build' step
Title: Message Title Ross M commented on JENKINS-38339 Re: UI for downstream jobs launched with 'build' step do we know what version this feature works. because it was working before 1.7.* 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174511.1474269026000.9152.1565121541487%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Jesse Glick commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Normally this sort of thing would be handled with simple closures etc., not evaluate. Since this is a nonstandard usage, I would consider the priority low. There was an effort (since backed out) to offer an SPI by which plugins with exotic workflow-cps usages could suppress the warnings for their special call patterns, but that would be of no use to you anyway. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9148.1565121360153%40Atlassian.JIRA.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Tatu Saloranta edited a comment on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Alas, it is actually not sure version 2.69 fixes this problem for good. Problem came back (we had initially reverted code we deemed that must have triggered retention) , and upgrade of Pipeline Groovy plug-in to 2.70 does not seem to have solved steady increase (although due to time it takes for classes to accumulate, over 1 week, it is difficult to be sure after 2 days since restart). If confirmed, it's back to Ye Olde Drawing Board to solve the problem. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189249.1521223408000.9137.1565119680325%40Atlassian.JIRA.
[JIRA] (JENKINS-50223) Pipeline Jenkins master ran out of Java Metaspace
Title: Message Title Tatu Saloranta commented on JENKINS-50223 Re: Pipeline Jenkins master ran out of Java Metaspace Alas, it is actually not sure version 2.69 fixes this problem for good. Problem came back, and upgrade of Pipeline Groovy plug-in to 2.70 does not seem to have solved steady increase (although due to time it takes for classes to accumulate, over 1 week, it is difficult to be sure after 2 days since restart). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.189249.1521223408000.9125.1565119620429%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning This logic is executing content `src` in sandbox as the original pipeline - MPL purpose is to separate the pipeline logic into modules. So this function is basic for the library - it creates another CPS shell with only variables provided into the 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9122.1565119320153%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title
Ulli Hafner edited a comment on JENKINS-58826
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds
Can you please check if in your build.xml file the following text is present{noformat}{ noformat} /Users/hafner/Development/git/warnings-ng-plugin-devenv/docker/volumes/jenkins-home/jobs/pipeline-analysis-model/lastStable {noformat } }
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.9117.1565119260165%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title
Ulli Hafner edited a comment on JENKINS-58826
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds
Can you please check if in your build.xml file the following text is present{noformat}/Users/hafner/Development/git/warnings-ng-plugin-devenv/docker/volumes/ jenkins-home/jobs/pipeline-analysis-model/lastStable{noformat}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.9119.1565119260194%40Atlassian.JIRA.
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title
Ulli Hafner commented on JENKINS-58826
Re: "Aggregated Analysis Results" does not get updated after a few dozen builds
Can you please check if in your build.xml file the following text is present
You can use grep:
grep io.jenkins.plugins.analysis.core.model build.xml
Then we see the other actions from my plugin as well. The build.xml file is part of the jobs folder of your Jenkins master. E.g. on my machine: {{/Users/hafner/Development/git/warnings-ng-plugin-devenv/docker/volumes/jenkins-home/jobs/pipeline-analysis-model/lastStable }}
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201139.1565095677000.9115.1565119200162%40Atlassian.JIRA.
[JIRA] (JENKINS-58828) Fails to find files checked out to subdirectory when resolving relative paths
Title: Message Title Ulli Hafner commented on JENKINS-58828 Re: Fails to find files checked out to subdirectory when resolving relative paths It will work if the warnings step is invoked within the same dir block. Otherwise see duplicate issues. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201141.1565099664000.9111.1565118120156%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Jesse Glick commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Explicit use of org.jenkinsci.plugins.workflow.cps.* implementation classes cannot be considered supported. What exactly is this code attempting to accomplish? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9109.1565118000355%40Atlassian.JIRA.
[JIRA] (JENKINS-58828) Fails to find files checked out to subdirectory when resolving relative paths
Title: Message Title Ulli Hafner updated JENKINS-58828 Jenkins / JENKINS-58828 Fails to find files checked out to subdirectory when resolving relative paths Change By: Ulli Hafner 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201141.1565099664000.9106.1565118000311%40Atlassian.JIRA.
[JIRA] (JENKINS-58828) Fails to find files checked out to subdirectory when resolving relative paths
Title: Message Title Ulli Hafner updated JENKINS-58828 Jenkins / JENKINS-58828 Fails to find files checked out to subdirectory when resolving relative paths Change By: Ulli Hafner Status: Open Fixed but Unreleased Resolution: Duplicate 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201141.1565099664000.9104.1565117940306%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title
Sergei Parshev commented on JENKINS-58620
Re: MPL shared library logic execution caused CPS mismatch warning
What I've done:
Started 2.176.2 jenkins with the next plugins.txt:
git
workflow-aggregator
Added shared library "test" with the local repo in /var/jenkins_home/test_shared_lib and "master" version by default
Init git repo /var/jenkins_home/test_shared_lib and created commit with the next content:
vars/executeGroovyScript.groovy
import org.jenkinsci.plugins.workflow.cps.CpsGroovyShellFactory
import org.jenkinsci.plugins.workflow.cps.CpsThread
def call(String src, String path, Map vars = [:]) {
getShell(vars).evaluate(src, path)
}
def getShell(Map vars = [:]) {
def ex = CpsThread.current().getExecution()
def shell = new CpsGroovyShellFactory(ex).withParent(ex.getShell()).build()
vars.each { key, val -> shell.setVariable(key, val) }
shell
}
Created test job with pipeline script:
@Library('test') _
executeGroovyScript('echo "hello world"', 'Module.groovy')
And the job execution result is:
Started by user unknown or anonymous
Running in Durability level: MAX_SURVIVABILITY
Loading library test@master
Attempting to resolve master from remote references...
> git --version # timeout=10
> git ls-remote -h /var/jenkins_home/test_shared_lib # timeout=10
Found match: refs/heads/master revision a8aa6eeacb2a84f533d33ca4bd6cb4851aa95dd5
No credentials specified
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url /var/jenkins_home/test_shared_lib # timeout=10
Fetching without tags
Fetching upstream changes from /var/jenkins_home/test_shared_lib
> git --version # timeout=10
> git fetch --no-tags --force --progress /var/jenkins_home/test_shared_lib +refs/heads/*:refs/remotes/origin/*
Checking out Revision a8aa6eeacb2a84f533d33ca4bd6cb4851aa95dd5 (master)
> git config core.sparsecheckout # timeout=10
> git
[JIRA] (JENKINS-58833) NodeLabel Parameter Plugin does not work for concurrent
Title: Message Title John Rocha created an issue Jenkins / JENKINS-58833 NodeLabel Parameter Plugin does not work for concurrent Issue Type: Bug Assignee: Dominik Bartholdi Components: nodelabelparameter-plugin Created: 2019-08-06 18:55 Environment: Jenkins 2.176.2 Windows 10 Internet Explorer, Firefox, Chrome Plugin version 1.72 Priority: Critical Reporter: John Rocha I created a project to run on agents. The project causes the agent's workspace to be updated with the latest from Perforce (SCM software). The project has: Allow multi node selection for concurrent builds configured Execute concurrent builds if necessary configured. Restrict whre this project can be run disabled. Master has 8 executors, slaves have 1 executor If I select master, node1 and node2 - only master runs. All should run. If I select node1 and node - node 1 runs, and once that finishes node2 runs. node1 and node2 should run at the same time on the two agent nodes.
[JIRA] (JENKINS-46962) Github Users Outside Organisation get an authenticated user in Jenkins.
Title: Message Title Mark Stosberg commented on JENKINS-46962 Re: Github Users Outside Organisation get an authenticated user in Jenkins. I'm noting that Google solves this issue by providing "Projects" which are limited to "No Organization" or a single G-Suite organization. Github could solve this on their side by providing OAuth API client credentials which only work for a specific organization. One simple way to implement this feature is to offer a list of "whitelisted domains" as a config option, perhaps just a comma separated list. After Github authentication is successful, check the user's email address against the domain whitelist. That would require that user's have provided their email to Github and for Github to provide the email back to Jenkins. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185334.1505825939000.9085.1565117700293%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Ok, I think I can prepare a simple vars-only shared lib with such call. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9078.1565116200200%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Jesse Glick commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning MPL is a shared library I understand that, but I suspect that the trigger condition for the bug could be narrowed down to something which could be written in a single short script, perhaps using some local function definitions or whatever. Even if it is actually impossible to reproduce without a library, then the minimal self-contained test case would be a minimal library (probably one source file with a few lines) and an accompanying Jenkinsfile. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9071.1565114640175%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title
Sergei Parshev commented on JENKINS-58620
Re: MPL shared library logic execution caused CPS mismatch warning
Hi Jesse Glick, Unfortunately it's impossible to prepare just a Jenkinsfile - MPL is a shared library. We already tracked down the issue - and found, that the message are produced during the module run in Helper.groovy:
static void runModule(String src, String path, Map vars = [:]) {
getShell(vars).evaluate(src, path)
}
If we using the minimal Jeninsfile from the MPL repo, the call tracepath to the first `Checkout` module "expected to call" message looks like this:
MPLPipeline()
MPLModule()
Helper.runModule()
CPSGroovyShell.evaluate()
Message: `expected to call org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.evaluate but wound up catching Checkout.run; see: https://jenkins.io/redirect/pipeline-cps-method-mismatches/`
This issue is not critical, but prints the verbose information that looks weird and not helpful for the end users...
Add Comment
[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-58716 Failure to check out specified tag for incremental version Change By: Jesse Glick Component/s: incrementals-tools 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201008.1564430335000.9057.1565114220239%40Atlassian.JIRA.
[JIRA] (JENKINS-58716) Failure to check out specified tag for incremental version
Title: Message Title
Jesse Glick commented on JENKINS-58716
Re: Failure to check out specified tag for incremental version
we should be able to look up the Git remote
I am not so sure. git remote -v in a forked PR build shows https://github.com/jenkinsci/XXX-plugin.git. This is because Jenkins first clones the origin repo at master, then merges in the PR head. As to the property, I think you want to introduce a property for the entire repository location, so
jenkinsci/${project.artifactId}-plugin
scm:git:git://github.com/${gitHubRepo}.git
scm:git:g...@github.com:${gitHubRepo}.git
https://github.com/${gitHubRepo}
${scmTag}
since a developer’s fork may not have the same name as the origin repository. In particular, if the developer already has some unrelated “sources” repo or fork named foo-plugin, then jenkinsci/foo-plugin will be forked to jqhacker/foo-plugin-1 or similar. You also would likely want to
Make incrementals:incrementalify do this transformation.
Adjust jenkinsci/archetypes to encourage new plugins to do this.
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
[JIRA] (JENKINS-58687) Tomcat deployment fails when using deploy plugin
Title: Message Title Mike Sollanych commented on JENKINS-58687 Re: Tomcat deployment fails when using deploy plugin That worked fine, thank you. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200976.1564286728000.9053.1565113860166%40Atlassian.JIRA.
[JIRA] (JENKINS-57023) Split external library functionality into its own plugin
Title: Message Title Jesse Glick commented on JENKINS-57023 Re: Split external library functionality into its own plugin Great! I would rather suggest inverting this: Keep the workflow-cps-global-lib-plugin repository, which would continue to host a plugin of the same name. Create a new plugin repository, probably with a more intuitive name like pipeline-groovy-libraries-plugin, and a smaller dependency tree. Move the org.jenkinsci.plugins.workflow.libs package and the UserDefinedGlobalVariable and GrapeHack classes to pipeline-groovy-libraries. (Do not forget src/test/ and src/main/resources/!) Make workflow-cps-global-lib depend on pipeline-groovy-libraries. Adjust the pom.xml / index.jelly of both plugins to make it clear that pipeline-groovy-libraries is what most people know and love/hate as Groovy libraries, whereas workflow-cps-global-lib is deprecated and only around for compatibility. Release pipeline-groovy-libraries, then the workflow-cps-global-lib update, mentioning the refactoring in the changelog for the latter and explaining that you can uninstall it if you were not using the Jenkins-hosted Git server feature. Replace mentions of workflow-cps-global-lib with pipeline-groovy-libraries wherever you can find them: workflow-aggregator, in particular, since jenkinsci/jenkins/core/src/main/resources/jenkins/install/platform-plugins.json still “recommends” this (against my advice). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Sergei Parshev assigned an issue to Sergei Parshev Jenkins / JENKINS-58620 MPL shared library logic execution caused CPS mismatch warning Change By: Sergei Parshev Assignee: Sergei Parshev 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.9049.1565113320197%40Atlassian.JIRA.
[JIRA] (JENKINS-57154) Regression in github-oauth-plugin 0.32 breaks /configureSecurity page
Title: Message Title Jon Cormier commented on JENKINS-57154 Re: Regression in github-oauth-plugin 0.32 breaks /configureSecurity page I installed 0.33 and the problem no longer appears for me. Thanks Sam Gleske 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198903.1556022985000.9005.1565112543250%40Atlassian.JIRA.
[JIRA] (JENKINS-57023) Split external library functionality into its own plugin
Title: Message Title Basil Crow commented on JENKINS-57023 Re: Split external library functionality into its own plugin Hey Jesse Glick, I might be interested in taking this on, depending on what is involved. I think this is what would need to be done: Create a new repository with the older and deprecated half of `workflow-cps-global-lib`, get it to compile, make sure tests are passing, etc. Request hosting for the new plugin. File a PR to remove the older and deprecated half of `workflow-cps-global-lib` from `workflow-cps-global-lib` itself. Release new versions of each plugin. What I'm not entirely clear about is how the transition process would work for users. Would we just need to mention in the release notes that users which want the old functionality need to install a new plugin? Is there anything else that I'm missing from the above steps? 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198725.1555423424000.9002.1565112420127%40Atlassian.JIRA.
[JIRA] (JENKINS-58620) MPL shared library logic execution caused CPS mismatch warning
Title: Message Title Jesse Glick commented on JENKINS-58620 Re: MPL shared library logic execution caused CPS mismatch warning Is there a self-contained minimal test case to reproduce the issue? Preferably just a single Jenkinsfile with all inessential lines removed. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200786.1563913328000.8999.1565112300158%40Atlassian.JIRA.
[JIRA] (JENKINS-37862) Extract build symlink handling to a plugin
Title: Message Title Jesse Glick commented on JENKINS-37862 Re: Extract build symlink handling to a plugin refer build results of build jobs from test jobs ... I think we had no wget at time of creating such jobs The usual way of doing this is with the Copy Artifact 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.174000.1472663694000.8986.1565111940317%40Atlassian.JIRA.
[JIRA] (JENKINS-58832) Artifact-promotion plugin is searching for metadata.xml file in a wrong path
Title: Message Title sivanarayana baisani created an issue Jenkins / JENKINS-58832 Artifact-promotion plugin is searching for metadata.xml file in a wrong path Issue Type: Bug Assignee: Unassigned Components: artifact-promotion-plugin Created: 2019-08-06 17:15 Environment: Artifact-promotion plugin 0.5.2, Jenkins 2.176.2 Labels: plugin Priority: Blocker Reporter: sivanarayana baisani The plugin is searching for the metadata.xml file inside the snapshot directory but it should be searching in the application repository. The error seems like Something has gone wrong and the transfer has failed: Could not find metadata com.company:App:1.0-SNAPSHOT/maven-metadata.xml in stagingrepo but it should search at com.company:App/maven-metadata.xml Add Comment
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Parichay Barpanda updated JENKINS-58829 Jenkins / JENKINS-58829 Add symbols to SCM discovery traits to prevent name clashes Change By: Parichay Barpanda Status: In Progress Review 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201142.1565100831000.8978.1565111640549%40Atlassian.JIRA.
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Parichay Barpanda started work on JENKINS-58829 Change By: Parichay Barpanda Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201142.1565100831000.8976.1565111640411%40Atlassian.JIRA.
[JIRA] (JENKINS-58817) Pipeline: Groovy kills remote calls after 5 minutes
Title: Message Title Alex Taylor commented on JENKINS-58817 Re: Pipeline: Groovy kills remote calls after 5 minutes https://github.com/jenkinsci/workflow-cps-plugin/pull/313 for the setting 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201129.1565026708000.8961.1565109540116%40Atlassian.JIRA.
[JIRA] (JENKINS-58831) consistently use periods for help messages
Title: Message Title Josh Soref created an issue Jenkins / JENKINS-58831 consistently use periods for help messages Issue Type: Task Assignee: Adrien Lecharpentier Attachments: image-2019-08-06-12-32-19-637.png Components: diagnostics-plugin Created: 2019-08-06 16:36 Priority: Minor Reporter: Josh Soref Expected results: Include a trailing period for all of these. Actual results: Diagnostic session Description
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Parichay Barpanda commented on JENKINS-58829 Re: Add symbols to SCM discovery traits to prevent name clashes Thanks Peter Leibiger for catching this, I have started working. Will let you know when 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201142.1565100831000.8958.1565109360143%40Atlassian.JIRA.
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Parichay Barpanda updated an issue Jenkins / JENKINS-58829 Add symbols to SCM discovery traits to prevent name clashes Change By: Parichay Barpanda Sprint: GSoC 2019. Coding Phase 3 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201142.1565100831000.8956.1565109300209%40Atlassian.JIRA.
[JIRA] (JENKINS-58809) CLI and API call do not work with SAML Realm
Title: Message Title Guillaume Dupin commented on JENKINS-58809 Re: CLI and API call do not work with SAML Realm Thanks for the help Indeed, the test you indicated is working well. So maybe in my case the problem comes from Keycloak SAML configuration... ? Or from the configuration of my reverse-proxy ? (my jenkins is behind an AWS LB + a NGINX reverse-proxy) Anyway, your test will give me a reference to compare to in my investigation ! Thank you again 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201120.156500429.8954.1565108820226%40Atlassian.JIRA.
[JIRA] (JENKINS-58822) Failed to send out e-mail
Title: Message Title Alex Earl commented on JENKINS-58822 Re: Failed to send out e-mail Did you follow the instructions and go to https://support.google.com/mail/?p=WantAuthError? In order to use SMTP with google, you have to do something things with your 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201134.1565077475000.8943.1565104800190%40Atlassian.JIRA.
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Marky Jackson updated an issue Jenkins / JENKINS-58829 Add symbols to SCM discovery traits to prevent name clashes Change By: Marky Jackson Labels: gsoc-2019 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201142.1565100831000.8941.1565104380293%40Atlassian.JIRA.
[JIRA] (JENKINS-58534) Impossible to access promotion's console output (navigation is broken from links and breadcrumbs)
Title: Message Title sheela vasudevan commented on JENKINS-58534 Re: Impossible to access promotion's console output (navigation is broken from links and breadcrumbs) I am facing same issue. Is there any timeline when the issue gets 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200683.1563381278000.8934.1565103960235%40Atlassian.JIRA.
[JIRA] (JENKINS-35229) Plugin manager Updates never completes
Title: Message Title Alex Nederlof commented on JENKINS-35229 Re: Plugin manager Updates never completes My problem was solved actually. Sorry, I forgot to close the issue. It turned out it was downloading the options via the browser, instead of on the server (this is a setting, but I cannot find it anymore). 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.170922.1464679741000.8931.1565103660549%40Atlassian.JIRA.
[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Title: Message Title Thierry Montalbano commented on JENKINS-58810 Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed Hi, I have the same issue with the same error message. It's intermittent. Often, when we rebuild manually, the notification is sent to bitbucket. It'd be nice if Jenkins could retry sending the notification if it fails. This started happening a about 15 days ago, maybe more. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201122.1565008163000.8920.1565103360145%40Atlassian.JIRA.
[JIRA] (JENKINS-58830) Write release 2.0 and wrap-up blog post
Title: Message Title Long Nguyen created an issue Jenkins / JENKINS-58830 Write release 2.0 and wrap-up blog post Issue Type: Task Assignee: Long Nguyen Components: remoting-kafka-plugin Created: 2019-08-06 14:36 Labels: gsoc-2019 Priority: Major Reporter: Long Nguyen 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.
[JIRA] (JENKINS-58829) Add symbols to SCM discovery traits to prevent name clashes
Title: Message Title Peter Leibiger created an issue Jenkins / JENKINS-58829 Add symbols to SCM discovery traits to prevent name clashes Issue Type: Improvement Assignee: Parichay Barpanda Components: gitlab-branch-source-plugin Created: 2019-08-06 14:13 Priority: Minor Reporter: Peter Leibiger The discovery trait descriptors need `@Symbol` annotations to prevent name clashes when used with JCasC. See same problem for github-branch-source : https://github.com/jenkinsci/configuration-as-code-plugin/issues/657 https://github.com/jenkinsci/github-branch-source-plugin/pull/183/files Add Comment
[JIRA] (JENKINS-12783) Delete workspace before build starts ignores Exlude patterns (for directories)
Title: Message Title Tim Bradt commented on JENKINS-12783 Re: Delete workspace before build starts ignores Exlude patterns (for directories) This bug is unfortunate. We're trying to preserve our IntelliJ project files so we don't have to restore project settings every time we build. This should really be addressed. +1 vote 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.143241.1329315126000.8882.1565100780377%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Alexander Komarov commented on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications Sounds good Jim Klimov. Mattermost already has a plugin that does not depend on instant-messaging and has plugin support: https://jenkins.io/doc/pipeline/steps/mattermost/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.8816.1565100541244%40Atlassian.JIRA.
[JIRA] (JENKINS-36826) Support Jenkins Pipeline for Jabber notifications
Title: Message Title Alexander Komarov edited a comment on JENKINS-36826 Re: Support Jenkins Pipeline for Jabber notifications Sounds good [~jimklimov]. Mattermost already has a plugin that does not depend on instant-messaging and has plugin pipeline support: https://jenkins.io/doc/pipeline/steps/mattermost/ 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172870.1469028488000.8849.1565100541849%40Atlassian.JIRA.
[JIRA] (JENKINS-58690) Add retention strategy for Cloud
Title: Message Title Long Nguyen updated JENKINS-58690 Jenkins / JENKINS-58690 Add retention strategy for Cloud Change By: Long Nguyen Status: In Review Resolved Resolution: Done 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200979.1564304727000.8811.1565100361699%40Atlassian.JIRA.
[JIRA] (JENKINS-58786) Write integration tests for implemented functions
Title: Message Title Long Nguyen started work on JENKINS-58786 Change By: Long Nguyen Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201096.1564755906000.8813.1565100361939%40Atlassian.JIRA.
[JIRA] (JENKINS-58828) Fails to find files checked out to subdirectory when resolving relative paths
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-58828 Fails to find files checked out to subdirectory when resolving relative paths Issue Type: Bug Assignee: Ulli Hafner Components: warnings-ng-plugin Created: 2019-08-06 13:54 Priority: Minor Reporter: Simon Richter I check out a project from git into a subdirectory "src". The compiler generates paths relative to this directory, and the path name resolver cannot create an absolute path for these warnings, so no source code context can be shown. It would be nice if I could configure a search path for resolving relative names. Add Comment
[JIRA] (JENKINS-58827) workflow-scm-step plugin does not find global credentials
Title: Message Title Jose Martin Rozanec created an issue Jenkins / JENKINS-58827 workflow-scm-step plugin does not find global credentials Issue Type: Bug Assignee: Unassigned Components: workflow-scm-step-plugin Created: 2019-08-06 13:50 Environment: Running on Jenkins ver. 2.176.2 Credentials plugin: 2.2.1 Credentials binding plugin: 1.19 workflow-scm-step: 2.9 OS: Ubuntu, 18.04.2 LTS (Bionic Beaver) Priority: Critical Reporter: Jose Martin Rozanec Issue: fails to retrieve global credential and thus fails SCM step Description: When executing the pipeline or using the snippet generator tool, global credentials are not found and thus the SCM steps fail. Credentials can be created from the dropdown provided for the SCM step at the pipeline snippet generator, but are later not listed in the same dropdown, though visible in the global credentials page. We verified that credentials can be accessed in the pipeline using the command withCredentials(id). Code statement: checkout([$class: 'GitSCM', branches: [[name: '*/master']], userRemoteConfigs: [[credentialsId: 'github-secret', url: 'g...@github.com:something/reponame.git']]]) Execution output: 15:15:00 Warning: CredentialId "github-secret" could not be found.15:15:00 Cloning the remote Git repository
[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Title: Message Title
Patrik Schalin edited a comment on JENKINS-58810
Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Also seeing this after Jenkins and Plugins upgrade. Have the same traces in logs. Also seeing sporadic "glitches" in Jenkins picking up push notifications from Bitbucket (Cloud). Enabled request traces in BB but cannot see any errors and 200s are reported. Clicking on "re-send request" kicks off the build as expected. My current env:{code:java}Jenkins : 2.187blueocean-events: 1.18.1azure-ad : 0.3.4azure-vm-agents : 1.1.1pipeline-stage-step : 2.3github-api : 1.95pam-auth : 1.5.1windows-azure-storage : 1.1.0ldap : 1.20Office-365-Connector: 4.11.0timestamper : 1.10azure-container-agents : 1.1.0ivy : 2.1maven-plugin : 3.4ant : 1.9configuration-as-code-support : 1.18configuration-as-code : 1.25junit : 1.28durable-task : 1.30mstest : 1.0.0sonar : 2.9jackson2-api : 2.9.9.1bitbucket : 1.1.10git-parameter : 0.9.11blueocean-pipeline-api-impl : 1.18.1matrix-project : 1.14token-macro : 2.8git : 4.0.0-rcmailer : 1.24workflow-basic-steps: 2.18workflow-job : 2.33blueocean-git-pipeline : 1.18.1blueocean-pipeline-scm-api : 1.18.1pipeline-milestone-step : 1.3.1jquery-detached : 1.2.1workflow-durable-task-step : 2.33pipeline-utility-steps : 2.3.0azure-publishersettings-credentials : 1.5blueocean-rest-impl : 1.18.1windows-slaves : 1.4favorite : 2.3.2xunit : 2.3.5workflow-scm-step : 2.9azure-app-service : 1.0.0docker-commons : 1.15trilead-api : 1.0.5command-launcher: 1.3role-strategy : 2.13htmlpublisher : 1.18jdk-tool : 1.3resource-disposer : 0.13ssh-agent : 1.17blueocean-pipeline-editor : 1.18.1blueocean-bitbucket-pipeline: 1.18.1authentication-tokens : 1.3external-monitor-job: 1.7pipeline-input-step : 2.10scm-api : 2.6.3github-branch-source: 2.5.5script-security : 1.62pipeline-rest-api : 2.12blueocean-commons : 1.18.1bitbucket-filter-project-trait : 1.0variant : 1.3matrix-auth : 2.4.2artifactory : 3.3.2bitbucket-approval-filter : 1.0.2lockable-resources : 2.5ssh-credentials : 1.17.1pipeline-model-definition : 1.3.9mercurial : 2.8azure-commons : 1.0.4git-client : 3.0.0-rcazure-acs : 0.2.4pipeline-build-step : 2.9basic-branch-build-strategies : 1.3.2cloudbees-folder: 6.9azure-cli : 0.9jsch : 0.1.55.1blueocean-rest
[JIRA] (JENKINS-58810) Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed
Title: Message Title Patrik Schalin commented on JENKINS-58810 Re: Failed to notify status of build to bitbucket in Multibranch pipeline and to trigger build from bitbucket when code pushed Also seeing this after Jenkins and Plugins upgrade. My current env: Jenkins : 2.187 blueocean-events: 1.18.1 azure-ad: 0.3.4 azure-vm-agents : 1.1.1 pipeline-stage-step : 2.3 github-api : 1.95 pam-auth: 1.5.1 windows-azure-storage : 1.1.0 ldap: 1.20 Office-365-Connector: 4.11.0 timestamper : 1.10 azure-container-agents : 1.1.0 ivy : 2.1 maven-plugin: 3.4 ant : 1.9 configuration-as-code-support : 1.18 configuration-as-code : 1.25 junit : 1.28 durable-task: 1.30 mstest : 1.0.0 sonar : 2.9 jackson2-api: 2.9.9.1 bitbucket : 1.1.10 git-parameter : 0.9.11 blueocean-pipeline-api-impl : 1.18.1 matrix-project : 1.14 token-macro : 2.8 git : 4.0.0-rc mailer : 1.24 workflow-basic-steps: 2.18 workflow-job: 2.33 blueocean-git-pipeline : 1.18.1 blueocean-pipeline-scm-api : 1.18.1 pipeline-milestone-step : 1.3.1 jquery-detached : 1.2.1 workflow-durable-task-step : 2.33 pipeline-utility-steps : 2.3.0 azure-publishersettings-credentials : 1.5 blueocean-rest-impl : 1.18.1 windows-slaves : 1.4 favorite: 2.3.2 xunit : 2.3.5 workflow-scm-step : 2.9 azure-app-service : 1.0.0 docker-commons : 1.15 trilead-api : 1.0.5 command-launcher: 1.3 role-strategy : 2.13 htmlpublisher : 1.18 jdk-tool: 1.3 resource-disposer : 0.13 ssh-agent : 1.17 blueocean-pipeline-editor : 1.18.1 blueocean-bitbucket-pipeline: 1.18.1 authentication-tokens : 1.3 external-monitor-job: 1.7 pipeline-input-step : 2.10 scm-api : 2.6.3 github-branch-source: 2.5.5 script-security : 1.62 pipeline-rest-api : 2.12 blueocean-commons : 1.18.1 bitbucket-filter-project-trait : 1.0 variant : 1.3 matrix-auth : 2.4.2 artifactory : 3.3.2 bitbucket-approval-filter : 1.0.2 lockable-resources : 2.5 ssh-credentials : 1.17.1 pipeline-model-definition : 1.3.9 mercurial : 2.8 azure-commons : 1.0.4 git-client : 3.0.0-rc azure-acs : 0.2.4 pipeline-build-step
[JIRA] (JENKINS-58826) "Aggregated Analysis Results" does not get updated after a few dozen builds
Title: Message Title Marc Würth created an issue Jenkins / JENKINS-58826 "Aggregated Analysis Results" does not get updated after a few dozen builds Issue Type: Bug Assignee: Ulli Hafner Attachments: grafik.png, grafik2.png Components: warnings-ng-plugin Created: 2019-08-06 12:47 Environment: Jenkins ver. 2.187 Ubuntu 16.04 64-bit os.name Linux os.version 4.4.0-157-generic java.vendor Oracle Corporation java.version 1.8.0_212 java.vm.info mixed mode java.vm.name OpenJDK 64-Bit Server VM java.vm.version 25.212-b03 Plugins: _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Pipeline (workflow-aggregator): 2.6 Jackson 2 API Plugin (jackson2-api): 2.9.9.1 Git plugin (git): 3.10.1 Maven Integration plugin (maven-plugin): 3.3 Ant Plugin (ant): 1.9 Credentials Plugin (credentials): 2.2.0 JSch dependency plugin (jsch): 0.1.55 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 Delivery Pipeline Plugin (delivery-pipeline-plugin): 1.4.0 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 Email Extension Plugin (email-ext): 2.66 Build Keeper Plugin (build-keeper-plugin): 1.3 Lockable Resources plugin (lockable-resources): 2.5 Parameterized Trigger plugin (parameterized-trigger): 2.35.2 DTKit 2 API. (dtkit-api): 2.1.1-1 Token Macro Plugin (token-macro): 2.8 jQuery plugin (jquery): 1.12.4-0 Clover plugin (clover): 4.10.0 Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.10 GIT server Plugin (git-server): 1.7 Violations plugin (violations): 0.7.11 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.5 Pipeline: Step API (workflow-step-api): 2.20 Pipeline: Multibranch (workflow-multibranch): 2.21 Folders Plugin (cloudbees-folder): 6.9 Javadoc Plugin (javadoc): 1.5 Job Configuration History Plugin (jobConfigHistory): 2.22 Warnings Next Generation Plugin (warnings-ng): 5.3.0 JDepend Plugin (jdepend): 1.3.0 Clover PHP plugin (cloverphp): 0.5 Crap4J plugin (crap4j): 0.9 SCM API Plugin (scm-api): 2.6.3 Authentication Tokens API Plugin (authentication-tokens): 1.3 Git client plugin (git-client): 2.8.0 Branch API Plugin (branch-api): 2.5.3 JIRA plugin (jira): 3.0.8 Pipeline: Declarative (pipeline-model-definition): 1.3.9 Mailer Plugin (mailer): 1.23 Plain Credentials Plugin (plain-credentials): 1.5 Build Pipeline Plugin (build-pipeline-plugin): 1.5.8 SSH Credentials Plugin (ssh-credentials): 1.17.1
[JIRA] (JENKINS-58825) Requirements FIle causes exception during config save
Title: Message Title Simon Richter created an issue Jenkins / JENKINS-58825 Requirements FIle causes exception during config save Issue Type: Bug Assignee: Unassigned Components: chroot-plugin Created: 2019-08-06 12:37 Priority: Major Reporter: Simon Richter I'm trying to use the "requirements file" option. Setting it to a non-empty value causes a test to run whether the file already exists and shows a warning if it doesn't (good). The warning is also shown if the file already exists (bad), and trying to save the configuration leads to an exception (very bad). Setting the option through editing the job configuration XML and reloading the Jenkins configuration works, and the job correctly uses the contents of the file as additional packages to install (good), but editing the job from the UI is now impossible as saving the configuration fails. Add Comment
[JIRA] (JENKINS-56547) Pipeline Stage View Plugin: Stage shows as completed even when its not
Title: Message Title Bhamidi Kishore updated an issue Jenkins / JENKINS-56547 Pipeline Stage View Plugin: Stage shows as completed even when its not Change By: Bhamidi Kishore Priority: Minor Major 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198161.1552500758000.8777.1565094360592%40Atlassian.JIRA.
[JIRA] (JENKINS-58823) Improve visualization for large job chains
Title: Message Title Gustaf Lundh commented on JENKINS-58823 Re: Improve visualization for large job chains Hmm.. I'll thinker a bit with the preview idea and we'll see if I can come up with something decent. I just want to be sure that I clearly can convey to the end user that only part of the Build Flow is currently 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201136.1565082556000.8775.1565093340100%40Atlassian.JIRA.
[JIRA] (JENKINS-58823) Improve visualization for large job chains
Title: Message Title Joschua Grube commented on JENKINS-58823 Re: Improve visualization for large job chains Yea this sounds like a good solution. It would be cool if we had something like a "preview" which just shows a few jobs and then the link to the full graph. But it might be difficult to implement. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201136.1565082556000.8753.1565092440440%40Atlassian.JIRA.
[JIRA] (JENKINS-58809) CLI and API call do not work with SAML Realm
Title: Message Title Ivan Fernandez Calvo closed an issue as Not A Defect Jenkins / JENKINS-58809 CLI and API call do not work with SAML Realm Change By: Ivan Fernandez Calvo Status: Reopened Closed 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201120.156500429.8750.1565091840434%40Atlassian.JIRA.
[JIRA] (JENKINS-58809) CLI and API call do not work with SAML Realm
Title: Message Title Ivan Fernandez Calvo commented on JENKINS-58809 Re: CLI and API call do not work with SAML Realm I have tested the issue with the environment at https://github.com/kuisathaverat/jenkins-issues/tree/master/JENKINS-58809/jenkins-2.176.2, I make the following steps: 1 - start docker-compose environment running the up.sh script 2 - add jenkins.example.com and saml host to my_ /etc/hosts_ pointing to 127.0.0.1 3 - Enter on http://jenkins.example.com:8080 and log in with the user tesla and password password 4 - Create an API Token for the user tesla 5 - run in a terminal the command curl -L $JENKINS_URL'/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)' works as expected, it returns the crumb 6 - run in a terminal the command curl -u tesla:11d8ab0b87fff558fd48ebe51f9c43d352 $JENKINS_URL'/crumbIssuer/api/xml?xpath=concat(//crumbRequestField,":",//crumb)' works as expected, it returns the crumb 7 - run the command java -jar jenkins-cli.jar -s $JENKINS_URL -http -auth tesla:11d8ab0b87fff558fd48ebe51f9c43d352 who-am-i works as expected, it returns the user info noted that I added the parameter `-http` to the jenkins-cli and I've used the jenkins-cli that comes with Jenkins core 2.176.2 see https://jenkins.io/blog/2017/04/11/new-cli/ , so there is no issue the two request works as expected 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201120.156500429.8745.1565091840348%40Atlassian.JIRA.
[JIRA] (JENKINS-41635) Allow BITBUCKET_PAYLOAD to work in pipeline jobs
Title: Message Title Félix Belzunce Arcos started work on JENKINS-41635 Change By: Félix Belzunce Arcos Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178459.148597556.8740.1565091360295%40Atlassian.JIRA.
[JIRA] (JENKINS-41635) Allow BITBUCKET_PAYLOAD to work in pipeline jobs
Title: Message Title Félix Belzunce Arcos commented on JENKINS-41635 Re: Allow BITBUCKET_PAYLOAD to work in pipeline jobs https://github.com/jenkinsci/bitbucket-plugin/pull/66 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.178459.148597556.8742.1565091360323%40Atlassian.JIRA.
[JIRA] (JENKINS-58763) Add export/import functionality for excluded dates.
Title: Message Title Jack Shen started work on JENKINS-58763 Change By: Jack Shen Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201067.1564666062000.8736.1565091300381%40Atlassian.JIRA.
[JIRA] (JENKINS-58760) Add more tests for javascript tests.
Title: Message Title Jack Shen started work on JENKINS-58760 Change By: Jack Shen Status: Open In 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201064.1564665627000.8737.1565091300394%40Atlassian.JIRA.
