[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Patrik Boström commented on JENKINS-50178 Re: Unable to manually trigger builds because play button is not visible Have you enabled "Enable manual triggers" in the view configuration? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45700) Template inheritance seems not to work like documented
Title: Message Title M C commented on JENKINS-45700 Re: Template inheritance seems not to work like documented This still does not work. I copied the exact code above, ran it and just get one container. That being maven. This use to work for me as I have a shared library with templates that can be composed together. But a recent update has broken this functionality. Big blocker for me as declarative syntax doesn't support multiple containers (really wish it did) so fell back to scripted to find out it is broken as well. I am running on Jenkins 2.110 with plugin 1.3.1 (I know 1.3.2 is available but I am always hesitant to upgrade plugins with Jenkins as more often than not then end up breaking additional things). Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look updated an issue Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look Attachment: test1_config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look updated an issue Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look Attachment: test2_config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look updated an issue Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look Attachment: view_config.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title R. Tyler Croy commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system Baptiste Mathus, regarding a JEP for determining Jenkins healthiness for Jenkins Essentials, I think that's a good idea and will be a useful design document to discuss with the broader development community. Will you file a ticket for that and drop it into Milestone 1? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia edited a comment on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error{code:java}ERROR: Failed to run ssh-add{code}(Almost) complete log:{code:java}First time build. Skipping changelog. [Pipeline] } [Pipeline] // stage [Pipeline] container [Pipeline] { [Pipeline] withCredentials [Pipeline] { [Pipeline] withEnv [Pipeline] { [Pipeline] timeoutTimeout timeoutTimeout set to expire in 1 hr 0 min [Pipeline] { [Pipeline] stage [Pipeline] { (Test) [Pipeline] container [Pipeline] { [Pipeline] sshagent [ssh-agent] Using credentials git-repos (SSH credential for Git repos) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exit SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK; SSH_AGENT_PID=23; export SSH_AGENT_PID; echo Agent pid 23; EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22 SSH_AGENT_PID=23 Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exit EXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) [Pipeline] // sshagent [Pipeline] } [Pipeline] // containerPost containerPost stage [Pipeline] junitRecording junitRecording test results No test report files were found. Configuration error? [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Doc) Stage 'Doc' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Lint) Stage 'Lint' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (SonarQube) Stage 'SonarQube' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Deploy) Stage 'Deploy' skipped due to earlier failure(s) [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timeout [Pipeline] } [Pipeline] // withEnv [Pipeline] } [Pipeline] // withCredentials [Pipeline] } [Pipeline] // container [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // podTemplate [Pipeline] End of PipelineERROR PipelineERROR : Failed to run ssh-add Finished: FAILURE{code} Can it be a race condition?
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia commented on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error ERROR: Failed to run ssh-add First time build. Skipping changelog.[Pipeline] }[Pipeline] // stage[Pipeline] container[Pipeline] {[Pipeline] withCredentials[Pipeline] {[Pipeline] withEnv[Pipeline] {[Pipeline] timeoutTimeout set to expire in 1 hr 0 min[Pipeline] {[Pipeline] stage[Pipeline] { (Test)[Pipeline] container[Pipeline] {[Pipeline] sshagent[ssh-agent] Using credentials git-repos (SSH credential for Git repos) [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exit SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK; SSH_AGENT_PID=23; export SSH_AGENT_PID; echo Agent pid 23; EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22 SSH_AGENT_PID=23 Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78] Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exit EXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key)[Pipeline] // sshagent[Pipeline] }[Pipeline] // containerPost stage[Pipeline] junitRecording test results No test report files were found. Configuration error?[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Doc)Stage 'Doc' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Lint)Stage 'Lint' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (SonarQube)Stage 'SonarQube' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Deploy)Stage 'Deploy' skipped due to earlier failure(s)[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Declarative: Post Actions)[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // timeout[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // withCredentials[Pipeline] }[Pipeline] // container[Pipeline] }[Pipeline] // node[Pipeline] }[Pipeline] // podTemplate[Pipeline] End of PipelineERROR: Failed to run ssh-add Finished: FAILURE Can it be a race condition?
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look updated an issue Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look When creating an initial job that manually triggers a downstream job in the post-build actions, the downstream job cannot be started using the Delivery Pipeline view because there is no "play" button visible/available after the initial job finishes. However, when using the Build-Pipeline-View, the downstream job is able to be triggered manually. There are no errors showing up in the logs that I see.To recreate, use the versions listed in the environment section, and create two freestyle projects. In the first project add a post-build action to "Build other projects (manual step)" and set the second project as the "Downsteam Project Name." Create a Delivery pipeline view and set the initial job as the first project you created. Build project 1 and view the delivery pipeline. The second job never has a play button to run. To add context to the provided image attachment, you can see there are three jobs test1, test2, and test3. Test1 and Test2 are setup as described above, but Test3 was added via "Build other projects" in Test1's post-build actions. I did this to show automatic build triggering is working but, not manual as you can see with Test2. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-42582) ssh-agent not applied in kubernetes container
Title: Message Title
Fran Garcia edited a comment on JENKINS-42582
Re: ssh-agent not applied in kubernetes container
Using version 1.3.2 most of the times it seems to work but sometimes I get the error {code:java} ERROR: Failed to run ssh-add {code} (Almost) complete log:{code:java} First time build. Skipping changelog. {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] container {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] withCredentials {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] withEnv {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] timeout{color}Timeout timeoutTimeout set to expire in 1 hr 0 min {color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Test) {color}{color:#9a} [Pipeline] container {color}{color:#9a} [Pipeline] \ { {color}{color:#9a} [Pipeline] sshagent {color} [ssh-agent] Using credentials git-repos (SSH credential for Git repos)[ssh-agent] Looking for ssh-agent implementation...[ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine)Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78]Executing command: "ssh-agent" printf "EXITCODE %3d" $?; exitSSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22; export SSH_AUTH_SOCK;SSH_AGENT_PID=23; export SSH_AGENT_PID;echo Agent pid 23;EXITCODE 0SSH_AUTH_SOCK=/tmp/ssh-oYnHo47QlMEc/agent.22SSH_AGENT_PID=23Executing shell script inside container [ubuntu] of pod [bowiepod-47nkj-nld78]Executing command: "ssh-add" "/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key" printf "EXITCODE %3d" $?; exitEXITCODE 0EXITCODE 0Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key)Identity added: /home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key (/home/jenkins/workspace/bowie_feature_doc_upload-2NDL5PPAHMMAWBMRX6CFCZI7VDOLJYNMA6HK2HG3NCDKNGOA6YVA@tmp/private_key_8883554255349387919.key) {color:#9a} [Pipeline] // sshagent {color}{color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // container{color}Post containerPost stage {color:#9a} [Pipeline] junit{color}Recording junitRecording test resultsNo test report files were found. Configuration error? {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Doc) {color} Stage 'Doc' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Lint) {color} Stage 'Lint' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (SonarQube) {color} Stage 'SonarQube' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a} [Pipeline] stage {color}{color:#9a} [Pipeline] \ { (Deploy) {color} Stage 'Deploy' skipped due to earlier failure(s) {color:#9a} [Pipeline] } {color}{color:#9a} [Pipeline] // stage {color}{color:#9a}
[JIRA] (JENKINS-50178) Unable to manually trigger builds because play button is not visible
Title: Message Title Jordan Look updated an issue Jenkins / JENKINS-50178 Unable to manually trigger builds because play button is not visible Change By: Jordan Look When creating an initial job that manually triggers a downstream job in the post-build actions, the downstream job cannot be started using the Delivery Pipeline view because there is no "play" button visible/available after the initial job finishes. However, when using the Build-Pipeline-View, the downstream job is able to be triggered manually. There are no errors showing up in the logs that I see. To recreate, use the versions listed in the environment section, and create two freestyle projects. In the first project add a post-build action to "Build other projects (manual step)" and set the second project as the "Downsteam Project Name." Create a Delivery pipeline view and set the initial job as the first project you created. Build project 1 and view the delivery pipeline. The second job never has a play button to run. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title
Baptiste Mathus edited a comment on JENKINS-49406
Re: Prototype the Evergreen snapshotting data safety system
{quote}I wonder if starting in quiet mode would result in us missing any potential errors? If not, then I say let's do it!{quote}Definitely. And [~jglick] already had a similar comment reviewing [https://github.com/batmat/jep/pull/1] But I think it would still be interesting to triage the potential issue causes, with a slightly more progressive process.Roughly, would/could be: * set to start in quiet mode next time, and restart * check Jenkins is healthy [1] * if yes, cancel quiet [EDIT: or better, write some plugin that would *only* allow our smoke testing job, on the next bullet point, to run] * start some kind of smoke testing build * if success, then \o/, if not, roll back.[1] [~rtyler] about that, I have been starting to think since a few days we probably need a dedicated JIRA/JEP to design what "evergreen-client decides if Jenkins is healthy [enough] or not", aka to trigger a rollback, or not... Do we something like this? WDYT?
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title Baptiste Mathus commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system I wonder if starting in quiet mode would result in us missing any potential errors? If not, then I say let's do it! Definitely. And Jesse Glick already had a similar comment reviewing https://github.com/batmat/jep/pull/1 But I think it would still be interesting to triage the potential issue causes, with a slightly more progressive process. Roughly, would/could be: set to start in quiet mode next time, and restart check Jenkins is healthy [1] if yes, cancel quiet start some kind of smoke testing build if success, then \o/, if not, roll back. [1] R. Tyler Croy about that, I have been starting to think since a few days we probably need a dedicated JIRA/JEP to design what "evergreen-client decides if Jenkins is healthy [enough] or not", aka to trigger a rollback, or not... Do we something like this? WDYT? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed
[JIRA] (JENKINS-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title
Mattia Mascia updated an issue
Jenkins / JENKINS-50196
Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Change By:
Mattia Mascia
h4. Test case A Pipeline script job as follows, The aim of this pipeline is to show the feature of *inheritFrom* : {code:java}podTemplate(cloud: 'openshift', inheritFrom: 'nodejs', name: 'nodejs-p', label: 'nodejs-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.npm', claimName: 'nodejs', readOnly: false)]) { node("nodejs-p") { stage('BuildFrontend') { // some commands } }}podTemplate(cloud: 'openshift', inheritFrom: 'maven', name: 'maven-p', label: 'maven-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.m2', claimName: 'maven', readOnly: false)]) { node("maven-p") { stage('BuildBackend') { // some commands } }{code} h4. Outcome The first podTemplate definition works as expected. The second podTemplate starts, but instead of using the inheritFrom defined ('*maven*') it is using the '*nodejs-p*' as parent. As you guess is wrong and because the *nodejs-p* template is temporary, the plugin starts the default *jenkins-slave* container. If you invert the podTemplate definitions inside the pipeline, so first *maven-p* and second *nodejs-p* you obtain the same behaviour. The first works as expected and the second fails. It looks like a race condition issue. {noformat}Plugin-Version: 1 0 . 2 10 Hudson-Version: 2.7.4Jenkins-Version: 2.7.4{noformat}
Add Comment
This
[JIRA] (JENKINS-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title
Mattia Mascia updated an issue
Jenkins / JENKINS-50196
Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Change By:
Mattia Mascia
h4. Test case A Pipeline script job as follows, The aim of this pipeline is to show the feature of *inheritFrom* : {code:java} podTemplate(cloud: 'openshift', inheritFrom: 'nodejs', name: 'nodejs-p', label: 'nodejs-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.npm', claimName: 'nodejs', readOnly: false)]) { node("nodejs-p") { stage('BuildFrontend') { // some commands } }}podTemplate(cloud: 'openshift', inheritFrom: 'maven', name: 'maven-p', label: 'maven-p', volumes: [ persistentVolumeClaim(mountPath: '/home/jenkins/.m2', claimName: 'maven', readOnly: false)]) { node("maven-p") { stage('BuildBackend') { // some commands } }{code} h4. Outcome The first podTemplate definition works as expected. The second podTemplate starts, but instead of using the inheritFrom defined ('*maven*') it is using the '*nodejs-p*' as parent. As you guess is wrong and because the *nodejs-p* template is temporary, the plugin starts the default *jenkins-slave* container. If you invert the podTemplate definitions inside the pipeline, so first *maven-p* and second *nodejs-p* you obtain the same behaviour. The first works as expected and the second fails. It looks like a race condition issue. {noformat}Plugin-Version: 0 1 . 10 2 Hudson-Version: 2.7.4Jenkins-Version: 2.7.4{noformat}
Add Comment
This message
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts You are combining the 2 problems to solve in 1 single use case Understood, the filtering seem to be the way forward for your problems. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50196) Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Title: Message Title
Mattia Mascia created an issue
Jenkins / JENKINS-50196
Jenkins Kubernetes plugin - Running a sequence of podTemplate with inheritFrom
Issue Type:
Bug
Assignee:
Carlos Sanchez
Components:
kubernetes-plugin
Created:
2018-03-15 16:07
Priority:
Major
Reporter:
Mattia Mascia
Test case A Pipeline script job as follows, The aim of this pipeline is to show the feature of inheritFrom :
podTemplate(cloud: 'openshift', inheritFrom: 'nodejs', name: 'nodejs-p', label: 'nodejs-p', volumes: [
persistentVolumeClaim(mountPath: '/home/jenkins/.npm', claimName: 'nodejs', readOnly: false)
]) {
node("nodejs-p") {
stage('BuildFrontend') {
// some commands
}
}
}
podTemplate(cloud: 'openshift', inheritFrom: 'maven', name: 'maven-p', label: 'maven-p', volumes: [
persistentVolumeClaim(mountPath: '/home/jenkins/.m2', claimName: 'maven', readOnly: false)
]) {
node("maven-p") {
stage('BuildBackend') {
// some commands
}
}
Outcome The first podTemplate definition works as expected. The second podTemplate starts, but instead of using the inheritFrom defined ('maven') it is using the 'nodejs-p' as parent. As you guess is wrong and because the nodejs-p template is temporary, the plugin starts the default jenkins-slave container. If you invert the podTemplate definitions inside the pipeline, so first maven-p and second nodejs-p you obtain the same behaviour. The first works as expected and the second fails. It looks like a race condition issue.
[JIRA] (JENKINS-44109) Enable Remoting work dir by default in Windows Service agents
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44109 Enable Remoting work dir by default in Windows Service agents Change By: Oleg Nenashev See the documentation for "-workDir" in the Remoting repo. The option should be added by default when Windows Agent Installer module generates a new Config File for Windows Service Wrapper Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44115) Enable Remoting work dir by default in Swarm Plugin
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44115 Enable Remoting work dir by default in Swarm Plugin Change By: Oleg Nenashev Labels: newbie-friendly remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44109) Enable Remoting work dir by default in Windows Service agents
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-44109 Enable Remoting work dir by default in Windows Service agents Change By: Oleg Nenashev Labels: newbie-friendly remoting Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title dan tran commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts out of 400+ artifacts showing up in the list, my users only care about 2. Paging does not help and the selected artifacts are burried in list, very hard to look up Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50177) Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Title: Message Title
Daniel Spilker resolved as Fixed
The Mercurial plugin is already supported by the Dynamic DSL:
multibranchPipelineJob(String name) {
branchSources {
branchSource {
source {
mercurialSCMSource {
source(String value)
credentialsId(String value)
id(String value)
}
}
}
}
}
Jenkins / JENKINS-50177
Add Mercurial (hg) to the list of supported branchSources for multibranchPipelineJob
Change By:
Daniel Spilker
Status:
Open Resolved
Resolution:
Fixed
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title R. Tyler Croy commented on JENKINS-50195 Re: Create a non root user for running Jenkins and the evergreen-client I'm assuming the issue here is that the java process is running as root, correct? Or are you concerned about supervisord running as root too? Assuming it's the first one, supervisord supports dropping permissions when it executes processes, so perhaps we should just update the supervisord.conf to run both java and eventually nodejs as the jenkins user? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36753) missing license information in about page
Title: Message Title Daniel Spilker started work on JENKINS-36753 Change By: Daniel Spilker Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50017) The process will pending when license windows prompt in background.
Title: Message Title Wang Robin closed an issue as Done It can be fixed by myself /w registry Jenkins / JENKINS-50017 The process will pending when license windows prompt in background. Change By: Wang Robin Status: Open Closed Resolution: Done Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50017) The process will pending when license windows prompt in background.
Title: Message Title Wang Robin commented on JENKINS-50017 Re: The process will pending when license windows prompt in background. It can be fixed by myself /w registry. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49406) Prototype the Evergreen snapshotting data safety system
Title: Message Title R. Tyler Croy commented on JENKINS-49406 Re: Prototype the Evergreen snapshotting data safety system That's an interesting idea Baptiste Mathus! I wonder if starting in quiet mode would result in us missing any potential errors? If not, then I say let's do it! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27729) Dependency and licence information are not bundled
Title: Message Title Daniel Spilker started work on JENKINS-27729 Change By: Daniel Spilker Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49525) Rare exception sync'ing global pipeline library with new project
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49525 Rare exception sync'ing global pipeline library with new project Change By: Paul Allen Labels: P4_C P4_B P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49916) P4CHARSET Broken
Title: Message Title Paul Allen assigned an issue to Paul Allen Jenkins / JENKINS-49916 P4CHARSET Broken Change By: Paul Allen Assignee: Paul Allen Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49916) P4CHARSET Broken
Title: Message Title Paul Allen commented on JENKINS-49916 Re: P4CHARSET Broken Found the bug in P4Java and verified the fix in Jenkins p4-plugin. Planning to release P4Java next week along with the plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50027) Polling build filters in jenkinsfile broken or need guidance on what code should be
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-50027 Polling build filters in jenkinsfile broken or need guidance on what code should be Change By: Paul Allen Labels: P4_B P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title Jesse Glick commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry To give a little more context to my earlier comment. Generally, we should drop from consideration any architectural change which involves too much Java magic. We had serious problems in the past with weird errors thrown under certain circumstances that were ultimately traceable to the ticks done to support @AdaptField, for example, and core devs had to spend a lot of time wrestling with ASM issues and so on. And of course an enormous amount of effort has been invested dealing with the use of Java serialization and reflection in core Jenkins libraries such as Stapler and Remoting—any productivity benefits from “convention over configuration” are in practice negligible compared to the debugging burden when things go wrong. (Not to mention security vulnerabilities.) Going forward, anything we can do to keep things at the level of plain old “CS 101” Java programming will make everyone sleep better at night. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46755) Approve Swarm review as step
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-46755 Approve Swarm review as step Change By: Paul Allen Labels: P4_B Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title R. Tyler Croy assigned an issue to Carlos Sanchez In the Gitter chat, Jesse Glick suggested implementing code changes and then taking advantage of the existing error telemetry tooling which will be implemented as part of JENKINS-49805. If I'm understanding Jesse Glick's suggestion correctly, we would be making code changes on methods we would want to see call stacks from via some code private static final SetWARNINGS = new ConcurrentSet<>(); public static void warnAboutDeprecatedMethod() { StackTraceElements[] stack = new Throwable().getStackTrace(); String key = stack[2] + " → " + stack[1]; if (WARNINGS.add(key) { LOGGER.warning("deprecated call to " + stack[1] + "\n\tat " + stack[2]); } } Which could then be called in "methods of interest", and use the error telemetry mechanism to transmit the call stack off the Jenkins instance. Carlos Sanchez, since this saves us a boatload of work, I'm perfectly fine with it if you are Jenkins / JENKINS-49892 Evaluate options for collecting "method instrumentation" telemetry Change By: R. Tyler Croy Assignee: R. Tyler Croy Carlos Sanchez Add Comment
[JIRA] (JENKINS-49955) Publish always publishing unchanged utf8+w files on Windows slaves.
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49955 Publish always publishing unchanged utf8+w files on Windows slaves. Change By: Paul Allen Labels: P4_VERIFY P4_B Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49141) P4 plugin removed BOM from utf8 files
Title: Message Title Paul Allen updated an issue Jenkins / JENKINS-49141 P4 plugin removed BOM from utf8 files Change By: Paul Allen Labels: P4_B P4_VERIFY Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Andrew Bayer started work on JENKINS-44924 Change By: Andrew Bayer Status: Reopened In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title Jesse Glick commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry My standing suggested alternative: something in, say, hudson.Util: private static final SetWARNINGS = Collections.synchronizedSet(new HashSet<>()); public static void warnAboutDeprecatedMethod() { StackTraceElements[] stack = new Throwable().getStackTrace(); String key = stack[2] + "|" + stack[1]; if (WARNINGS.add(key) { LOGGER.warning("deprecated call to " + stack[1] + "\n\tat " + stack[2]); } } Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-44924) pipeline groovy script - Sort a list with custom comparator or closure not sorting
Title: Message Title Andrew Bayer assigned an issue to Andrew Bayer Jenkins / JENKINS-44924 pipeline groovy script - Sort a list with custom comparator or closure not sorting Change By: Andrew Bayer Assignee: Andrew Bayer Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title Baptiste Mathus commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry Carlos Sanchez can you please complete the description of this JIRA with your requirements here? It's hard to judge what solution can match your needs currently . Thanks! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49988) "Periodically if not otherwise run" interval dropdown only displays a single value
Title: Message Title Omar Kohl resolved as Duplicate Jenkins / JENKINS-49988 "Periodically if not otherwise run" interval dropdown only displays a single value Change By: Omar Kohl Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49988) "Periodically if not otherwise run" interval dropdown only displays a single value
Title: Message Title Omar Kohl commented on JENKINS-49988 Re: "Periodically if not otherwise run" interval dropdown only displays a single value This has been solved in 2.111 . Probably it was related to Jenkins Core Issue https://issues.jenkins-ci.org/browse/JENKINS-49968 which was fixed by reverting a Prototype.js upgrade. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49746) Regex returns more matches than it should if errors are close together
Title: Message Title Alex Earl commented on JENKINS-49746 Re: Regex returns more matches than it should if errors are close together I was on a business trip and didn't get a chance to look into it yet. I will do so this week. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47783) parallel stages are displayed as passed even when they are not executed
Title: Message Title Idikoro Eradiri commented on JENKINS-47783 Re: parallel stages are displayed as passed even when they are not executed Vivek Pandey James Dumay Is this fixed? I'm currenlty on Jenkins 2.89.4 and running blueocean 1.4.2 and I am still seeing the same issue. The sample pipeline script I posted above still shows parallel stages as passed even though they did not execute. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49892) Evaluate options for collecting "method instrumentation" telemetry
Title: Message Title Jesse Glick commented on JENKINS-49892 Re: Evaluate options for collecting "method instrumentation" telemetry No no no no no. Did I mention no? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46755) Approve Swarm review as step
Title: Message Title Michael Rose commented on JENKINS-46755 Re: Approve Swarm review as step Yes, I want to vote up/down the specific version that we attempted to build based on the build status. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49553) Parametrized publishing can no longer be configured
Title: Message Title Alex Earl commented on JENKINS-49553 Re: Parametrized publishing can no longer be configured I just took over maintaining the publish over plugins recently and reassigned the issues to myself. I am working through them as I can. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title
Baptiste Mathus updated an issue
Jenkins / JENKINS-50195
Create a non root user for running Jenkins and the evergreen-client
Change By:
Baptiste Mathus
h3. IssueCurrently the user for Jenkins is still {{root}}, we need to fix this and be for instance {{jenkins}} before we deliver it to users.h3. ExpectedThe processes should *not* running as root.We must do like the {{jenkins/jenkins}} image in this regard .
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title Baptiste Mathus updated an issue Jenkins / JENKINS-50195 Create a non root user for running Jenkins and the evergreen-client Change By: Baptiste Mathus Labels: essentials Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50195) Create a non root user for running Jenkins and the evergreen-client
Title: Message Title Baptiste Mathus created an issue Jenkins / JENKINS-50195 Create a non root user for running Jenkins and the evergreen-client Issue Type: Bug Assignee: R. Tyler Croy Components: essentials Created: 2018-03-15 14:14 Priority: Major Reporter: Baptiste Mathus Issue Currently the user for Jenkins is still root, we need to fix this and be for instance jenkins before we deliver it to users. Expected The processes should not running as root. We must do like the jenkins/jenkins image. Add Comment
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble edited a comment on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I'm also now seeing build storms from this issue.One can turn off "Periodically if not otherwise run" to prevent the storms, but then you're left with orphaned jobs being left behind when a branch is deleted. Therefore, if one tries to use the branch source plugin, they either have to deal with build storms, or with orphaned jobs. I don't think I saw this issue back when the core functionality existed in the GitHub Organization Folders plugin. Perhaps this is a regression? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37491) Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes
Title: Message Title Joshua Noble commented on JENKINS-37491 Re: Build Origin PRs (merge with base branch) conducts rebuilds when baseline changes I'm also now seeing build storms from this issue. One can turn off "Periodically if not otherwise run" to prevent the storms, but then you're left with orphaned jobs being left behind when a branch is deleted. Therefore, if one tries to use the branch source plugin, they either have to deal with build storms, or with orphaned jobs. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Child Builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}And job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If manually run job 2 (Build now) then in JIRA:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If manually run job1 then:{code:java}Automatically created by: [~anonymous] from Build URL{code}Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code}Jenkins log:{code:java}INFO: While serving http://jenkins.local/job/ansible/job/job2/build: hudson.security.AccessDeniedException2: anonymous is missing the Job/Build permission{code}JIRA log:{code:java}2018-03-14 16:14:16,596 http-8080-11 WARN javabuild 974x2370843x1 zeo05a jenkins.local,127.0.0.1 /rest/api/2/issue/TEST-1 [labs.remoteapps.webhook.WebHookRegistrationManager] Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent{code}Jenkins: 2.73.1Jira Pipeline Steps: 1.3.1Jira: 5.1
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble reopened an issue Jenkins / JENKINS-42519 Closed pull requests, branch jobs are not cleaned up Change By: Joshua Noble Resolution: Not A Defect Status: Resolved Reopened Assignee: Stephen Connolly Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Child Builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code} and And job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If i start job2 manual manually run job 2 (Build now) then in JIRA issue :{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If job1 -> job2 then :{code:java}Automatically created by: [~anonymous] from Build URL{code}Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code}Jenkins log:{code:java}INFO: While serving http://jenkins.local/job/ansible/job/job2/build: hudson.security.AccessDeniedException2: anonymous is missing the Job/Build permission{code}JIRA log:{code:java}2018-03-14 16:14:16,596 http-8080-11 WARN javabuild 974x2370843x1 zeo05a jenkins.local,127.0.0.1 /rest/api/2/issue/TEST-1 [labs.remoteapps.webhook.WebHookRegistrationManager] Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent{code}Jenkins: 2.73.1Jira Pipeline Steps: 1.3.1Jira: 5.1
[JIRA] (JENKINS-50179) parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out.
Title: Message Title
Aravinder Bandi commented on JENKINS-50179
Re: parallel step with failFast set to false, parallel branch 'foo' kills other parallel branch 'bar' when foo times-out.
I tried having parallel in steps and not inside script block. None the less I see same error.
pipeline {
agent any
options {
timestamps()
timeout(time: 30, unit: 'MINUTES')
}
stages {
stage('Setup'){
steps{
parallel(
'foo': {
timeout(time: 60, unit: 'SECONDS'){
sh "sleep 90"
}
echo "Done with foo"
},
'bar': {
sh "sleep 200"
echo "Done with bar"
},
failFast: false
)
}
}
}
}
snippet for console output:
[Pipeline] node
Running on Jenkins in /Users/Shared/Jenkins/Home/workspace/test_scripts
[Pipeline] {
[Pipeline] timestamps
[Pipeline] {
[Pipeline] timeout
08:53:06 Timeout set to expire in 30 min
[Pipeline] {
[Pipeline] stage
[Pipeline] { (Setup)
[Pipeline] parallel
[Pipeline] [foo] { (Branch: foo)
[Pipeline] [bar] { (Branch: bar)
[Pipeline] [foo] timeout
08:53:06 [foo] Timeout set to expire in 1 min 0 sec
[Pipeline] [foo] {
[Pipeline] [bar] sh
08:53:06 [bar] [test_scripts] Running shell script
[Pipeline] [foo] sh
08:53:06 [bar] + sleep 200
08:53:06 [foo] [test_scripts] Running shell script
08:53:06 [foo] + sleep 90
08:54:06 [foo] Cancelling nested steps due to timeout
08:54:06 [bar] sh: line 1: 11698 Terminated: 15 JENKINS_SERVER_COOKIE=$jsc '/Users/Shared/Jenkins/Home/workspace/test_scripts@tmp/durable-0a2c2946/script.sh' > '/Users/Shared/Jenkins/Home/workspace/test_scripts@tmp/durable-0a2c2946/jenkins-log.txt' 2>&1
08:54:06 [foo] Sending interrupt signal to process
08:54:06 [foo] sh: line 1: 11704 Terminated: 15 JENKINS_SERVER_COOKIE=$jsc '/Users/Shared/Jenkins/Home/workspace/test_scripts@tmp/durable-cd67dc01/script.sh' > '/Users/Shared/Jenkins/Home/workspace/test_scripts@tmp/durable-cd67dc01/jenkins-log.txt' 2>&1
[Pipeline] [bar] }
08:54:15 [bar] Failed in branch bar
[Pipeline] [foo] }
[Pipeline] [foo] // timeout
[Pipeline] [foo] }
08:54:15 [foo] Failed in branch foo
[Pipeline] // parallel
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // timeout
[Pipeline] }
[Pipeline] // timestamps
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 143
Finished: FAILURE
[JIRA] (JENKINS-42519) Closed pull requests, branch jobs are not cleaned up
Title: Message Title Joshua Noble commented on JENKINS-42519 Re: Closed pull requests, branch jobs are not cleaned up I would like to bump this back up. Orphaned jobs should be deleted when an incoming webhook is received if the item strategy is set to 0. I also agree with Stephen Ash about JENKINS-37491. If a user wants to use GitHub Organization folders via the branch source plugin and build "merged" PR's, they either have to deal with build storms (by having "Periodically if not otherwise run" turned on) or deal with orphaned jobs. (By having "Periodically if not otherwise run" turned off, to prevent build storms) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Oliver Lockwood updated an issue Jenkins / JENKINS-50189 Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 Change By: Oliver Lockwood Attachment: pod-templates.xml Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Oliver Lockwood commented on JENKINS-50189 Re: Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 `pod-templates.xml` now attached, containing the relevant section from `config.xml` Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Child Builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If job1-> job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code}Jenkins log:{code:java}INFO: While serving http:// localhost jenkins.local /job/ansible/job/job2/build: hudson.security.AccessDeniedException2: anonymous is missing the Job/Build permission{code}JIRA log:{code:java}2018-03-14 16:14:16,596 http-8080-11 WARN javabuild 974x2370843x1 zeo05a 192 jenkins . 168.67.4 local ,127.0.0.1 /rest/api/2/issue/TEST-1 [labs.remoteapps.webhook.WebHookRegistrationManager] Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent{code}Jenkins: 2.73.1Jira Pipeline Steps: 1.3.1Jira: 5.1
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-50181
Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Thanks for reporting the issue!{quote} Adding multiple newlines didn't seem have any adverse effect so Jenkins should probably just add a newline when it writes the keyfile.{quote}Sounds reasonable to me, although probably a newline should only be added if there isn't one already so that resaving the credentials doesn't keep adding newlines . Feel free to submit a pull request to the [repository|https://github.com/jenkinsci/ssh-credentials-plugin] (ideally with a regression test); [here|https://github.com/jenkinsci/ssh-credentials-plugin/blob/822ece754b1e4c209b6ce47190302bf17f1c/src/main/java/com/cloudbees/jenkins/plugins/sshcredentials/impl/BasicSSHUserPrivateKey.java#L309] is the class that I think would need to be modified.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-27396) Elastic timeout in pipeline
Title: Message Title Adir Atias commented on JENKINS-27396 Re: Elastic timeout in pipeline we're looking for a solution exactly for this case, is there any update ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Child Builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If job1-> job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code}Jenkins log:{code:java}INFO: While serving http://localhost/job/ansible/job/job2/build: hudson.security.AccessDeniedException2: anonymous is missing the Job/Build permission{code}JIRA log:{code:java}2018-03-14 16:14:16,596 http-8080-11 WARN javabuild 974x2370843x1 zeo05a 192.168.67.4,127.0.0.1 /rest/api/2/issue/TEST-1 [labs.remoteapps.webhook.WebHookRegistrationManager] Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent{code} Jenkins: 2.73.1 Jira Pipeline Steps: 1.3.1Jira: 5.1
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title
Patrick Ruckstuhl edited a comment on JENKINS-43894
Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
As none of those variables provide us with something that can be configure on a slave level, this is what we did as an (ugly) workaround. We define an environment variable called REFERENCE_REPO on each slave and the master.Inside our jenkins pipeline library we create a step called checkoutCurrent{code}import java.util.regex.Pattern import java.lang.reflect.Field import java.lang.reflect.Modifier // checkout current scm and resolve the REFERENCE_REPO environment variable, workaround for JENKINS-43894def call(originalScm) { Field field = null def originalExtension updatedExtension = null def originalMetaClass originalReference = null ; try { if (originalScm.hasProperty('extensions') && originalScm.extensions) { print('has extensions') def extensions = originalScm.extensions for (int i = 0; i < extensions.size(); i++) {def extension = extensions[i]if (extension.hasProperty('reference') && extension.reference instanceof String) { def reference updatedExtension = extension originalReference = extension .reference print('replacing reference: ' + reference originalReference ) def reference = reference originalReference .replaceAll(Pattern.quote('${REFERENCE_REPO}'), env.REFERENCE_REPO) print('with: ' + reference) originalExtension // https://gist.github.com/pditommaso/263721865d84dee6ebaf field = extension .class.getDeclaredField("reference") originalMetaClass Field modifiersField = extension Field . metaClass class.getDeclaredField("modifiers") extension modifiersField . metaClass setAccessible(true) modifiersField . invokeMethod = { String name setInt(field , args -> field.getModifiers() & ~Modifier.FINAL) if field.setAccessible ( 'getReference' == name true ) { return reference } else { return this field . invokeMethod set ( name extension , args reference ) } }} } } checkout changelog: false, poll: false, scm: originalScm } finally { if ( originalExtension field ) { originalExtension print('reset reference to: ' + originalReference) field . metaClass = originalMetaClass set(updatedExtension, originalReference) } } } {code}and then in the pipeline instead of{code}checkout changelog: false, poll: false, scm: scm{code}we do{code}checkoutCurrent(scm){code}
Add Comment
[JIRA] (JENKINS-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Oliver Lockwood commented on JENKINS-50189 Re: Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 We have left the "Command to run" empty as the helptext says: Override the image entrypoint with a different one and we see no need to override. I can copy-paste the full XML definition (from each different version of the Kubernetes plugin) if that would help? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49592) Add ability to filter out Maven Deploy Artifacts
Title: Message Title Cyrille Le Clerc commented on JENKINS-49592 Re: Add ability to filter out Maven Deploy Artifacts To rephrase your RFE. You ask to filter the listed artifacts to only show the artifacts that matter to the users who browse this page (eg. Don't show pom files and intermediate artifacts). Your goal is not related to the number of generated artifacts that would be too big and that would impact the rendering of the page. For this reason, a pagination mechanism would not solve your problem. Correct? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Child Builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If job1-> job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code} Jenkins log:{code:java}INFO: While serving http://localhost/job/ansible/job/job2/build: hudson.security.AccessDeniedException2: anonymous is missing the Job/Build permission{code}JIRA log:{code:java}2018-03-14 16:14:16,596 http-8080-11 WARN javabuild 974x2370843x1 zeo05a 192.168.67.4,127.0.0.1 /rest/api/2/issue/TEST-1 [labs.remoteapps.webhook.WebHookRegistrationManager] Failed to publish web-hooks for event com.atlassian.jira.event.issue.IssueEvent{code}
[JIRA] (JENKINS-50181) ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile
Title: Message Title Devin Nusbaum commented on JENKINS-50181 Re: ssh-agent/ssh-credentials-plugin failing because ssh-add expects a newline in the keyfile Thanks for reporting the issue! Adding multiple newlines didn't seem have any adverse effect so Jenkins should probably just add a newline when it writes the keyfile. Sounds reasonable to me, although probably a newline should only be added if there isn't one already. Feel free to submit a pull request to the repository (ideally with a regression test); here is the class that I think would need to be modified. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Child Builds
Title: Message Title Matvey Kondratev updated an issue Jenkins / JENKINS-50194 Child Builds Change By: Matvey Kondratev Summary: Children build jobs Child Builds Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Children build jobs
Title: Message Title Matvey Kondratev updated an issue Jenkins / JENKINS-50194 Children build jobs Change By: Matvey Kondratev Summary: Anonymous and child builds Children build jobs Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}If i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}If job1-> job2:{code:java}Automatically created by: [~anonymous] from Build URL{code} Maybe bug?{code:java}/*** Return the current build user.** @param causes build causes.* @return user name.*/protected static String prepareBuildUser(List causes) {String buildUser = "anonymous";if (causes != null && causes.size() > 0) {if (causes.get(0) instanceof UserIdCause) {buildUser = ((UserIdCause) causes.get(0)).getUserId();} else if (causes.get(0) instanceof UpstreamCause) {List upstreamCauses = ((UpstreamCause) causes.get(0)).getUpstreamCauses();prepareBuildUser(upstreamCauses);}}return Util.fixEmpty(buildUser) == null ? "anonymous" : buildUser;}{code}
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code} When If i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code} When If job1 start -> job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}
Add Comment
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}#!groovynode('master') {...stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"...}{code}When job2 i start job2 manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}When job1 start job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}
Add Comment
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: ' regress job2 ', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"{code}When job2 start manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}When job1 start job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}
Add Comment
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'job2', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java} #!groovynode('master') {... stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err" ...} {code}When job2 start manual (Build now) in JIRA issue:{code:java}Automatically created by: Matvey Kondratev from Build URL{code}When job1 start job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}
Add Comment
[JIRA] (JENKINS-49697) Single quote in credentials password causing job crash
Title: Message Title Ovidiu-Florin Bogdan closed an issue as Fixed Jenkins / JENKINS-49697 Single quote in credentials password causing job crash Change By: Ovidiu-Florin Bogdan Status: Open Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'regress', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"{code}When job2 start manual (Build now) in JIRA issue: {code:java}Automatically created by: Matvey Kondratev from Build URL{code}When job1 start job2:{code:java}Automatically created by: [~anonymous] from Build URL{code}
Add Comment
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev updated an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Change By:
Matvey Kondratev
i have job1 with Jenkinsfile (example):{code:java}#!groovynode('master') {try {stage('prepare') {}stage('check playbook') {}stage('deploy') {}stage('cleanup') {currentBuild.result = 'SUCCESS'deleteDir()build job: 'regress', wait: false}} catch(exc) {currentBuild.result = 'FAILURE'deleteDir()throw(exc)} finally {}}{code}and job2 with Jenkinsfile:{code:java}stage('jira update') {withEnv(['JIRA_SITE=LOCAL']) {version = [:]lastComment.eachMatch("(TEST)-[0-9]+") {a -> version[a[1]] = '';}version.each {projectKey, y -> println "project - $projectKey"def testVersion = [ name: nextTag, released: false, description: "${nextTag}", project: projectKey ]def result = jiraNewVersion version: testVersionversion[projectKey] = result.data}lastComment.eachMatch("(TEST)-[0-9]+") {a -> issueKey=a[0]; projectKey=a[1];try {def newVersion = version[projectKey]def testIssue = [fields: [fixVersions: [newVersion] ]]def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssueprintln "version - $editRes"} catch(err) {echo "version error - $err"}try {def transitionInput = [transition: [id: 751]]def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInputprintln "transition - $transRes"} catch(err) {echo "transition error - $err"}try {jiraAddComment idOrKey: issueKey, comment: "Success"} catch(err) {echo "comment error - $err"{code} When job2 start manual (Build now) in JIRA issue:
Add Comment
[JIRA] (JENKINS-50194) Anonymous and child builds
Title: Message Title
Matvey Kondratev created an issue
Jenkins / JENKINS-50194
Anonymous and child builds
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
jira-steps-plugin
Created:
2018-03-15 13:19
Priority:
Minor
Reporter:
Matvey Kondratev
i have job1 with Jenkinsfile (example):
#!groovy
node('master') {
try {
stage('prepare') {
}
stage('check playbook') {
}
stage('deploy') {
}
stage('cleanup') {
currentBuild.result = 'SUCCESS'
deleteDir()
build job: 'regress', wait: false
}
} catch(exc) {
currentBuild.result = 'FAILURE'
deleteDir()
throw(exc)
} finally {
}
}
and job2 with Jenkinsfile:
stage('jira update') {
withEnv(['JIRA_SITE=LOCAL']) {
version = [:]
lastComment.eachMatch("(TEST)-[0-9]+") {
a -> version[a[1]] = '';
}
version.each {
projectKey, y -> println "project - $projectKey"
def testVersion = [ name: nextTag,
released: false,
description: "${nextTag}",
project: projectKey ]
def result = jiraNewVersion version: testVersion
version[projectKey] = result.data
}
lastComment.eachMatch("(TEST)-[0-9]+") {
a -> issueKey=a[0]; projectKey=a[1];
try {
def newVersion = version[projectKey]
def testIssue = [fields: [fixVersions: [newVersion] ]]
def editRes = jiraEditIssue idOrKey: issueKey, issue: testIssue
println "version - $editRes"
} catch(err) {
echo "version error - $err"
}
try {
def transitionInput = [transition: [id: 751]]
def transRes = jiraTransitionIssue idOrKey: issueKey, input: transitionInput
println "transition - $transRes"
} catch(err) {
echo "transition error - $err"
}
[JIRA] (JENKINS-50189) Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2
Title: Message Title Carlos Sanchez commented on JENKINS-50189 Re: Regression: Pipeline 'sh' step broken by Kubernetes plugin 1.3.2 what is your pod definition? do you have the command sh instead of /bin/sh -c ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50193) Add Gitea support in blueocean plugin
Title: Message Title Lauris BH created an issue Jenkins / JENKINS-50193 Add Gitea support in blueocean plugin Issue Type: New Feature Assignee: Unassigned Components: blueocean-plugin Created: 2018-03-15 13:12 Labels: gitea blueocean Priority: Minor Reporter: Lauris BH Would be great if it was possible to choose Gitea in pipeline editor wizard. But at least function for Jenkinsfile for setting status on commit is needed Add Comment
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title Patrick Ruckstuhl commented on JENKINS-43894 Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo Updated my code a little bit, now it will revert the changes after doing the checkout (as otherwise this modified the general config I had in the job). Would be really nice to get your PR merged. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-38219) Restrict Job.CONFIGURE permissions by plugins
Title: Message Title Jesse Glick commented on JENKINS-38219 Re: Restrict Job.CONFIGURE permissions by plugins Sounds like you need JENKINS-32596 but I am not sure I follow the use case here. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43894) Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
Title: Message Title
Patrick Ruckstuhl edited a comment on JENKINS-43894
Re: Environment variables not resolved in Pipeline SCM -> Advanced clone behaviours -> Path of the reference repo
As none of those variables provide us with something that can be configure on a slave level, this is what we did as an (ugly) workaround. We define an environment variable called REFERENCE_REPO on each slave and the master.Inside our jenkins pipeline library we create a step called checkoutCurrent{code}import java.util.regex.Pattern import hudson.plugins.git.extensions.impl.CloneOption // checkout current scm and resolve the REFERENCE_REPO environment variable, workaround for JENKINS-43894def call(originalScm) { def originalExtension = null def originalMetaClass = null try { if (originalScm.hasProperty('extensions') && originalScm.extensions) { print('has extensions') def extensions = originalScm.extensions def updatedExtension = null for (int i = 0; i < extensions.size(); i++) { def extension = extensions[i] if (extension instanceof CloneOption && extension .hasProperty('reference') && extension.reference instanceof String ) {def reference = extension.referenceprint('replacing reference: ' + reference)reference = reference.replaceAll(Pattern.quote('${REFERENCE_REPO}'), env.REFERENCE_REPO)print('with: ' + reference) updatedExtension originalExtension = new CloneOption( extension .shallow, originalMetaClass = extension. noTags, reference, metaClass extension. timeout) metaClass.invokeMethod = { String name, args -> } } if ( updatedExtension 'getReference' == name ) { extensions return reference } else { return this . replace invokeMethod ( updatedExtension name, args ) } } } } } checkout changelog: false, poll: false, scm: originalScm} finally { if (originalExtension) { originalExtension.metaClass = originalMetaClass } }}{ code}and then in the pipeline instead of{code}checkout changelog: false, poll: false, scm: scm{code}we do{code}checkoutCurrent(scm){code}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-50102) Support for Snippet Generator
Title: Message Title Jesse Glick resolved as Not A Defect Nothing is needed beyond JENKINS-26670. Jenkins / JENKINS-50102 Support for Snippet Generator Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49349) git scm plugin attempts to checkout stale SHAs
Title: Message Title Mark Waite commented on JENKINS-49349 Re: git scm plugin attempts to checkout stale SHAs Please provide a list of steps which will show the problem consistently for someone trying to investigate the problem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50191) Multibranch Pipeline tends to keep rebuilding same commits
Title: Message Title Mark Waite updated an issue Jenkins / JENKINS-50191 Multibranch Pipeline tends to keep rebuilding same commits Change By: Mark Waite Component/s: git-plugin Component/s: scm-api-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50184) Error in code fetching using git-plugin
Title: Message Title Vatsal Harde commented on JENKINS-50184 Re: Error in code fetching using git-plugin Thanks will check. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50184) Error in code fetching using git-plugin
Title: Message Title Mark Waite commented on JENKINS-50184 Re: Error in code fetching using git-plugin If the problem is intermittent, you should check the logs of your git provider to see if they are failing due to resource overload. I had a case of random failures in my environment during high volume downloads because my git server was configured to limit the number of concurrent ssh connections. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45506) Failed to serialize LockableResource with JobConfigHistory
Title: Message Title Michal Niwinski commented on JENKINS-45506 Re: Failed to serialize LockableResource with JobConfigHistory Unfortunately, fix provided by Daniel Geißler is not working for us. I added LockableResourcesManager, so now my "System configuration exclude file pattern" looks like: queue|nodeMonitors|UpdateCenter|global-build-stats|MilestoneStep|LockableResourcesManager and from time to time we still have this error: java.nio.channels.ClosedByInterruptException at java.nio.channels.spi.AbstractInterruptibleChannel.end(AbstractInterruptibleChannel.java:202) at sun.nio.ch.FileChannelImpl.write(FileChannelImpl.java:216) at java.nio.channels.Channels.writeFullyImpl(Channels.java:78) at java.nio.channels.Channels.writeFully(Channels.java:101) at java.nio.channels.Channels.access$000(Channels.java:61) at java.nio.channels.Channels$1.write(Channels.java:174) at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221) at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:291) at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:295) at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:141) at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:229) at java.io.BufferedWriter.flush(BufferedWriter.java:254) at hudson.util.AtomicFileWriter.flush(AtomicFileWriter.java:97) at com.thoughtworks.xstream.core.util.QuickWriter.flush(QuickWriter.java:75) Caused: com.thoughtworks.xstream.io.StreamException: : null at com.thoughtworks.xstream.core.util.QuickWriter.flush(QuickWriter.java:77) at com.thoughtworks.xstream.core.util.QuickWriter.write(QuickWriter.java:37) at com.thoughtworks.xstream.io.xml.PrettyPrintWriter.startNode(PrettyPrintWriter.java:197) at com.thoughtworks.xstream.io.xml.PrettyPrintWriter.startNode(PrettyPrintWriter.java:206) at com.thoughtworks.xstream.io.WriterWrapper.startNode(WriterWrapper.java:33) at com.thoughtworks.xstream.io.path.PathTrackingWriter.startNode(PathTrackingWriter.java:44) at com.thoughtworks.xstream.io.ExtendedHierarchicalStreamWriterHelper.startNode(ExtendedHierarchicalStreamWriterHelper.java:17) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:235) Caused: java.lang.RuntimeException: Failed to serialize org.jenkins.plugins.lockableresources.LockableResource#queuingStarted for class org.jenkins.plugins.lockableresources.LockableResource at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:256) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:224) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:209) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:150) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at
[JIRA] (JENKINS-50186) Deploy war/ear to a container Failed
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-50186 Deploy war/ear to a container Failed Change By: Oleg Nenashev Summary: Deploy war/ear to a container Faild Failed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50184) Error in code fetching using git-plugin
Title: Message Title Vatsal Harde edited a comment on JENKINS-50184 Re: Error in code fetching using git-plugin Hi, Thanks for your response.This issue is not occurring regularly , but it is occurring randomly. The same configuration and credentials may work for one time , but it may not work next time. Moreover,We have made sure from our side that , this is not a an authentication issue.So we don't think it is configuration or authentication related issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50184) Error in code fetching using git-plugin
Title: Message Title Vatsal Harde commented on JENKINS-50184 Re: Error in code fetching using git-plugin Hi, Thanks for your response.This issue is not occurring regularly but it is occurring randomly. The same configuration and credentials may work for one time but it may not work next time. Moreover,We have made sure from our side that this is not a authentication issue.So we don't think it is configuration or authentication related issue. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50192) Password is stored in clear
Title: Message Title Pavel Dobes created an issue Jenkins / JENKINS-50192 Password is stored in clear Issue Type: Improvement Assignee: Unassigned Components: mashup-portlets-plugin Created: 2018-03-15 12:30 Priority: Critical Reporter: Pavel Dobes The SonararQube dashboard is storing the user & password in clear in the config.xml file. It will be nice if tis plugin will be able to use with the Jenkins credentials, where password is encrypted. Other option is to allow use only access token instead of username & password. Add Comment
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title Mark Waite commented on JENKINS-50019 Re: java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer What version of Java is running on the agents which report that failure? JENKINS-49402 hints that a similar stack trace is seen when running a Java 1.8.0_111 on macOS. Since that version was released in late 2016, I assume there may be fixes in the newer Java versions which are not available in Java 1.8.0_111. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50005) WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information
Title: Message Title Mark Waite resolved as Cannot Reproduce Jenkins / JENKINS-50005 WARNING: Process leaked file descriptors. See https://jenkins.io/redirect/troubleshooting/process-leaked-file-descriptors for more information Change By: Mark Waite Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-50019
java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Change By:
Mark Waite
We intermittently see nodes fail during Git checkout with a traceback that looks like this:{noformat} *09:45:25* java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer*09:45:25* at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29)*09:45:25* at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:71)*09:45:25* at jdk.internal.reflect.GeneratedMethodAccessor51.invoke(Unknown Source)*09:45:25* at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)*09:45:25* at java.lang.reflect.Method.invoke(Method.java:564)*09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:922)*09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:896)*09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:853)*09:45:25* at hudson.remoting.UserRequest.perform(UserRequest.java:207)*09:45:25* at hudson.remoting.UserRequest.perform(UserRequest.java:53)*09:45:25* at hudson.remoting.Request$2.run(Request.java:358)*09:45:25* at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)*09:45:25* at java.util.concurrent.FutureTask.run(FutureTask.java:264)*09:45:25* at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)*09:45:25* at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)*09:45:25* at hudson.remoting.Engine$1$1.run(Engine.java:98)*09:45:25* at java.lang.Thread.run(Thread.java:844)Full log: [https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-macos-10.13-py3-build-test/2797//console]{noformat}Retrying does not resolve the problem, however, subsequent builds on the same node often do succeed (for the case above, three hours later another build succeeded.)The error is highly reminiscent of https://issues.jenkins-ci.org/browse/JENKINS-19453 but that issue was fixed in the Jenkins 1.x series, and this is a much more modern version of Jenkins. Additionally, the error doesn't seem to be persistent (in that it's not necessary to restart the worker to resolve the problem.)BTW, this is not just an OS X slave problem; we've had it happen to Linux workers too (although the missing class is different): [https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-trusty-py2.7.9-build/3214/console]I'm not really sure how to go about making a reproducing test case. Let me know if you have any ideas. The other case stack trace looks like this:{noformat}23:28:29 Also: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-172-31-82-71.ec2.internal/172.31.82.71:4246423:28:29 at
[JIRA] (JENKINS-50019) java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Title: Message Title
Mark Waite updated an issue
Jenkins / JENKINS-50019
java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer
Change By:
Mark Waite
We intermittently see nodes fail during Git checkout with a traceback that looks like this: {noformat} *09:45:25* java.lang.NoClassDefFoundError: Could not initialize class jenkins.model.Jenkins$MasterComputer *09:45:25* at org.jenkinsci.plugins.gitclient.AbstractGitAPIImpl.withRepository(AbstractGitAPIImpl.java:29) *09:45:25* at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.withRepository(CliGitAPIImpl.java:71) *09:45:25* at jdk.internal.reflect.GeneratedMethodAccessor51.invoke(Unknown Source) *09:45:25* at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) *09:45:25* at java.lang.reflect.Method.invoke(Method.java:564) *09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:922) *09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:896) *09:45:25* at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:853) *09:45:25* at hudson.remoting.UserRequest.perform(UserRequest.java:207) *09:45:25* at hudson.remoting.UserRequest.perform(UserRequest.java:53) *09:45:25* at hudson.remoting.Request$2.run(Request.java:358) *09:45:25* at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) *09:45:25* at java.util.concurrent.FutureTask.run(FutureTask.java:264) *09:45:25* at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) *09:45:25* at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) *09:45:25* at hudson.remoting.Engine$1$1.run(Engine.java:98) *09:45:25* at java.lang.Thread.run(Thread.java:844)Full log: [https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-macos-10.13-py3-build-test/2797//console] {noformat} Retrying does not resolve the problem, however, subsequent builds on the same node often do succeed (for the case above, three hours later another build succeeded.)The error is highly reminiscent of https://issues.jenkins-ci.org/browse/JENKINS-19453 but that issue was fixed in the Jenkins 1.x series, and this is a much more modern version of Jenkins. Additionally, the error doesn't seem to be persistent (in that it's not necessary to restart the worker to resolve the problem.)BTW, this is not just an OS X slave problem; we've had it happen to Linux workers too (although the missing class is different): [https://ci.pytorch.org/jenkins/job/pytorch-builds/job/pytorch-linux-trusty-py2.7.9-build/3214/console]I'm not really sure how to go about making a reproducing test case. Let me know if you have any ideas.
[JIRA] (JENKINS-50158) Git plugin class LocalBranch needs to be serializable
Title: Message Title Mark Waite resolved as Not A Defect Jenkins / JENKINS-50158 Git plugin class LocalBranch needs to be serializable Change By: Mark Waite Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
