[JIRA] (JENKINS-59797) AvatarCache does not support authenticated scm access
Title: Message Title Michael Lasevich commented on JENKINS-59797 Re: AvatarCache does not support authenticated scm access Any thought as to when it may be released? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.202527.1571192077000.3694.1583812500160%40Atlassian.JIRA.
[JIRA] (JENKINS-61400) Release 2.224: SCM specification is removed after editing a job's configuration
Title: Message Title Christopher Tubbs resolved as Duplicate Jenkins / JENKINS-61400 Release 2.224: SCM specification is removed after editing a job's configuration Change By: Christopher Tubbs Status: Open Resolved Resolution: Duplicate Released As: https://jenkins.io/changelog/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205054.1583764753000.3689.1583812380361%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz edited a comment on JENKINS-54748 Re: Memory leak in test-results-analyzer causes Jenkins to crash fwiw, our workplace was having similar out-of-memory issues with our Jenkins server recently.I tracked it down to this "test-results-analyzer" plugin also, as it was chewing up 2.9GB with just string-data.Initially, I +wrongly assumed+ that this plugin was responsible for the "*Test Result*" page of the interface, hence assumed this was a plugin that we needed. these were the web-ui pages affected: !image-2020-03-10-14-14-23-905.png! !image-2020-03-10-14-14-28-949.png! However, I finally realised that this plugin is responsible for entirely different output. It provides a link called "*Test Results Analyzer*" which collates a large table of all your test results across *all* your builds. More info [at this link|https://plugins.jenkins.io/test-results-analyzer/].!image-2020-03-10-14-14-38-818.png! So I now understood why it was chewing up so much string data, some of our projects have build histories consisting of up to 2000 builds, with hundreds of tests in them. So this would have resulted in an +absolutely enormous+ table! :)So with that understanding under my belt, I felt safe to delete this plugin, as our team has no need for it.Just wanted to share this experience, in-case others are experiencing this same confusion between these two things. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz commented on JENKINS-54748 Re: Memory leak in test-results-analyzer causes Jenkins to crash fwiw, our workplace was having similar out-of-memory issues with our Jenkins server recently. I tracked it down to this "test-results-analyzer" plugin also, as it was chewing up 2.9GB with just string-data. Initially, I wrongly assumed that this plugin was responsible for the "Test Result" page of the interface, hence assumed this was a plugin that we needed. However, I finally realised that this plugin is responsible for entirely different output. It provides a link called "Test Results Analyzer" which collates a large table of all your test results across all your builds. More info at this link. So I now understood why it was chewing up so much string data, some of our projects have build histories consisting of up to 2000 builds, with hundreds of tests in them. So this would have resulted in an absolutely enormous table! So with that understanding under my belt, I felt safe to delete this plugin, as our team has no need for it. Just wanted to share this experience, in-case others are experiencing this same confusion between these two things. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-14-28-949.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3657.1583810101695%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-14-04-213.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3630.1583810101140%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-14-38-818.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3660.1583810101729%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-14-23-905.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3647.1583810101566%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-13-23-056.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3610.1583810040879%40Atlassian.JIRA.
[JIRA] (JENKINS-54748) Memory leak in test-results-analyzer causes Jenkins to crash
Title: Message Title Gurce Isikyildiz updated an issue Jenkins / JENKINS-54748 Memory leak in test-results-analyzer causes Jenkins to crash Change By: Gurce Isikyildiz Attachment: image-2020-03-10-14-13-46-347.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195552.1542794187000.3620.1583810041067%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error hi [~andrewsumner], just forget previous comments , below is my final requirement and what I need now regarding this issue: * I had use upack cli command line tool for package my artifacts as a universal package .upack file. But when I'm uploading upack file into proget site by using the upack "push" command its still giving the 504 error and stopping the Jenkinspipeline. Any idea how to skip this 504 error from the Jenkinsfile? * When I'm using upack "push" command in my powershell scripts its skipping the 504 error and keep building the project. But when I'm using upack "push" command in-side Jenkinsfile only it's stopping the build. So now I want to know is how to continue building the job with this 504 error in Jenkinsfile? because I prefer to use upack "push" command inside my Jenkinsfile rather than inside powershell script.Any ideas [~andrewsumner]?Thanks, Jenkins Customer South AsiaAmila Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3607.1583804220226%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake edited a comment on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error hi [~andrewsumner], this just forget previous comments below is my final conclusion requirement and what I need now regarding this issue: * I had use upack cli command line tool for package my artifacts as a universal package .upack file. But when I'm uploading upack file into proget site by using the upack "push" command its still giving the 504 error and stopping the Jenkinspipeline. Any idea how to skip this 504 error from the Jenkinsfile? * When I'm using upack "push" command in my powershell scripts its skipping the 504 error and keep building the project. But when I'm using upack "push" command in-side Jenkinsfile only it's stopping the build. So now I want to know is how to continue building the job with this 504 error in Jenkinsfile? because I prefer to use upack "push" command inside my Jenkinsfile rather than inside powershell script.Any ideas [~andrewsumner]?Thanks,Jenkins Customer South AsiaAmila Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204701.1582203816000.3605.1583804220197%40Atlassian.JIRA.
[JIRA] (JENKINS-61167) Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error
Title: Message Title Amila Gunathilake commented on JENKINS-61167 Re: Inedo ProGet plugin when uploading Package file to proget I'm getting 504 Gateway Time-out Error hi Andrew Sumner, this is my final conclusion regarding this issue: I had use upack cli command line tool for package my artifacts as a universal package .upack file. But when I'm uploading upack file into proget site by using the upack "push" command its still giving the 504 error and stopping the Jenkinspipeline. Any idea how to skip this 504 error from the Jenkinsfile? When I'm using upack "push" command in my powershell scripts its skipping the 504 error and keep building the project. But when I'm using upack "push" command in-side Jenkinsfile only it's stopping the build. So now I want to know is how to continue building the job with this 504 error in Jenkinsfile? because I prefer to use upack "push" command inside my Jenkinsfile rather than inside powershell script. Any ideas Andrew Sumner? Thanks, Jenkins Customer South Asia Amila Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-61409) Websocket connections crash if message size is greater than 64Kb
Title: Message Title
Karthik Jayaraman created an issue
Jenkins / JENKINS-61409
Websocket connections crash if message size is greater than 64Kb
Issue Type:
Bug
Assignee:
Jeff Thompson
Components:
core, remoting
Created:
2020-03-10 00:59
Environment:
Jenkins version 2.223 - Built from docker container jenkins/jenkins:centos
Labels:
websocket
Priority:
Critical
Reporter:
Karthik Jayaraman
Websocket connections fail if the response from a pipeline step is greater than 64kb. Steps to recreate the problem:
Run a jenkins server using the docker container jenkins/jenkins:centos
Create a New Node with webSocket enabled
On another Linux VM/slave machine, run the agent.jar with -webSocket option to connect to the Jenkins Master
Create a pipeline with a step that would output text >64kb. For example, create a text file with size > 64Kb. 'cat' the file as a pipeline step.
pipeline {
agent {
label 'test-channelclose'
}
stages {
stage ('Debug Issue') {
steps {
sh 'cat build_output.log'
[JIRA] (JENKINS-60423) Powershell fails when the script starts with 'CmdletBinding' attribut
Title: Message Title Owen Mehegan assigned an issue to Filipe Roque Jenkins / JENKINS-60423 Powershell fails when the script starts with 'CmdletBinding' attribut Change By: Owen Mehegan Assignee: Filipe Roque Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203495.1575993533000.3599.1583799300229%40Atlassian.JIRA.
[JIRA] (JENKINS-59563) Jenkins jobs disappear after Windows slave restart
Title: Message Title Owen Mehegan closed an issue as Incomplete Reopen if you can provide more information. Jenkins / JENKINS-59563 Jenkins jobs disappear after Windows slave restart Change By: Owen Mehegan Status: Open Closed Resolution: Incomplete Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Mark Waite updated JENKINS-61398 Merged for Jenkins 2.225 Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Mark Waite Status: In Review Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-60343) java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax
Title: Message Title davidkarlsen commented on JENKINS-60343 Re: java.nio.file.AccessDeniedException: /home/jenkins for specific workingDir during NodeProvision by kubernetes yaml syntax I'm seeing this as well in: JENKINS-61339 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203357.1575290252000.3586.1583796660183%40Atlassian.JIRA.
[JIRA] (JENKINS-61363) Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances'
Title: Message Title Oleg Anufriev updated an issue Jenkins / JENKINS-61363 Missbehavior on 'Minimum number of instances' and 'Minimum number of spare instances' Change By: Oleg Anufriev I have configured 2 AWS clouds, for example (prodVpc and devVpc) in different regions with 1 AMI in each (with different names)It said that 'Minimum number of spare instances' and 'Minimum number of instances' act on per AMI basis. I observe behavior like these settings are global for the whole plugin and mean total of ec2 slaves independently of cloud and AMI.Configuring: > Minimum number of instances=1 > Minimum number of spare instances=1 for each ami/cloud i've expected to get 2 ec2 slaves in total: 1 for prodVpc and 1 for devVpc. I get only one ec2 slave instead. When Changing these parameters values up and down and running jobs i run pipeline 've made a conclusion , that requires absent slaves plugin fires them takes in account the total number of fired up successfully by plugin instances, regardless to Cloud name or AMI id . Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-56231) Suppress automatic SCM triggering is deprecated
Title: Message Title Chaitanya Bapat commented on JENKINS-56231 Re: Suppress automatic SCM triggering is deprecated Even I am facing similar issue. I have disabled GitHub WebHook that points to Jenkins Server because I want GitHub WebHook to point to a Lambda function. My lambda function filters Webhooks events and only when a specific comment is made on a PR I want to trigger a build on Jenkins. Unfortunately, after disabling the Webhook that points to jenkins directly, PR branches aren't being discovered and hence I am unable to trigger build on PR branches. I can resolve this problem by re-enabling the GitHub WebHook that points to Jenkins Server but disabling "Suppress automatic SCM triggering". Unfortunately I can't find that anymore on Jenkins Configure due to updates. How should I go about? I want Jenkins to discover branches but not trigger builds on its own. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197793.1550743475000.3572.1583795160286%40Atlassian.JIRA.
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title Mark Waite commented on JENKINS-61408 Re: Git executable is randomly set to empty string Steps to duplicate the problem? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205062.1583793463000.3569.1583794270136%40Atlassian.JIRA.
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-61408 Git executable is randomly set to empty string Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205062.1583793463000.3567.1583794200133%40Atlassian.JIRA.
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title
Stephane Odul updated an issue
Jenkins / JENKINS-61408
Git executable is randomly set to empty string
Change By:
Stephane Odul
Once in a while, at least several times a week, the name of the Git executable ends up being unset and the Git plugin calls ` init` (whitespace) instead of `git init`.We use a custom installer for git and it works and install just fine and even with jobs with multiple parallel stages, only one stage hits the bug, randomly. So configuration on our side is just fine but we suspect that there is a bug in the codebase where the variable holding the git executable name can get invalidated, at the stage level. {noformat} [2020-03-04T19:28:38.877Z] Failed to get git executable [2020-03-04T19:28: 38.877Z] Failed to get git executable[2020-03-04T19:28: 42.682Z] using credential x-github-rw [2020-03-04T19:28:42.691Z] Cloning the remote Git repository [2020-03-04T19:28:42.691Z] Using shallow clone with depth 500 [2020-03-04T19:28:42.691Z] Avoid fetching tags [2020-03-04T19:28:42.691Z] Honoring refspec on initial clone [2020-03-04T19:28:42.933Z] ERROR: Error cloning remote repo 'origin' [2020-03-04T19:28:42.933Z] hudson.plugins.git.GitException: Could not init /home/jenkins/agent/workspace/GitHub__master [2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:989) [2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:747) [2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161) [2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154) [2020-03-04T19:28:42.933Z] at hudson.remoting.UserRequest.perform(UserRequest.java:211) [2020-03-04T19:28:42.934Z] at hudson.remoting.UserRequest.perform(UserRequest.java:54) [2020-03-04T19:28:42.934Z] at hudson.remoting.Request$2.run(Request.java:369) [2020-03-04T19:28:42.934Z] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) [2020-03-04T19:28:42.934Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266) [2020-03-04T19:28:42.934Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [2020-03-04T19:28:42.934Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [2020-03-04T19:28:42.934Z] at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97) [2020-03-04T19:28:42.934Z] at java.lang.Thread.run(Thread.java:748) [2020-03-04T19:28:42.934Z] Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-xx-xx-xx-xx.us-west-2.compute.internal/xx.xx.xx.xx:40980 [2020-03-04T19:28:42.934Z] at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741) [2020-03-04T19:28:42.934Z] at
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title
Stephane Odul updated an issue
Jenkins / JENKINS-61408
Git executable is randomly set to empty string
Change By:
Stephane Odul
Once in a while, at least several times a week, the name of the Git executable ends up being unset and the Git plugin calls ` init` (whitespace) instead of `git init`.We use a custom installer for git and it works and install just fine and even with jobs with multiple parallel stages, only one stage hits the bug, randomly. So configuration on our side is just fine but we suspect that there is a bug in the codebase where the variable holding the git executable name can get invalidated, at the stage level. {noformat} [2020-03-04T19:28:38.877Z] Failed to get git executable[2020-03-04T19:28:38.877Z] Failed to get git executable[2020-03-04T19:28:42.682Z] using credential x-github-rw[2020-03-04T19:28:42.691Z] Cloning the remote Git repository[2020-03-04T19:28:42.691Z] Using shallow clone with depth 500[2020-03-04T19:28:42.691Z] Avoid fetching tags[2020-03-04T19:28:42.691Z] Honoring refspec on initial clone[2020-03-04T19:28:42.933Z] ERROR: Error cloning remote repo 'origin'[2020-03-04T19:28:42.933Z] hudson.plugins.git.GitException: Could not init /home/jenkins/agent/workspace/GitHub__master[2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$5.execute(CliGitAPIImpl.java:989)[2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:747)[2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:161)[2020-03-04T19:28:42.933Z] at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:154)[2020-03-04T19:28:42.933Z] at hudson.remoting.UserRequest.perform(UserRequest.java:211)[2020-03-04T19:28:42.934Z] at hudson.remoting.UserRequest.perform(UserRequest.java:54)[2020-03-04T19:28:42.934Z] at hudson.remoting.Request$2.run(Request.java:369)[2020-03-04T19:28:42.934Z] at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)[2020-03-04T19:28:42.934Z] at java.util.concurrent.FutureTask.run(FutureTask.java:266)[2020-03-04T19:28:42.934Z] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)[2020-03-04T19:28:42.934Z] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)[2020-03-04T19:28:42.934Z] at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:97)[2020-03-04T19:28:42.934Z] at java.lang.Thread.run(Thread.java:748)[2020-03-04T19:28:42.934Z] Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ip-xx-xx-xx-xx.us-west-2.compute.internal/xx.xx.xx.xx:40980[2020-03-04T19:28:42.934Z] at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1741)[2020-03-04T19:28:42.934Z] at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356)[2020-03-04T19:28:42.934Z] at
[JIRA] (JENKINS-61408) Git executable is randomly set to empty string
Title: Message Title Stephane Odul created an issue Jenkins / JENKINS-61408 Git executable is randomly set to empty string Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2020-03-09 22:37 Environment: Jenkins 2.204.5 Git Plugin 4.1.1 Priority: Major Reporter: Stephane Odul Once in a while, at least several times a week, the name of the Git executable ends up being unset and the Git plugin calls ` init` (whitespace) instead of `git init`. We use a custom installer for git and it works and install just fine and even with jobs with multiple parallel stages, only one stage hits the bug, randomly. So configuration on our side is just fine but we suspect that there is a bug in the codebase where the variable holding the git executable name can get invalidated, at the stage level. [2020-03-04T19:28:38.877Z] Failed to get git executable[2020-03-04T19:28:38.877Z] Failed to get git executable[2020-03-04T19:28:42.682Z] using credential x-github-rw[2020-03-04T19:28:42.691Z] Cloning the remote Git repository[2020-03-04T19:28:42.691Z] Using shallow clone with depth 500[2020-03-04T19:28:42.691Z] Avoid fetching tags[2020-03-04T19:28:42.691Z] Honoring refspec on initial clone[2020-03-04T19:28:42.933Z] ERROR: Error cloning remote repo 'origin'[2020-03-04T19:28:42.933Z] hudson.plugins.git.GitException: Could not init /home/jenkins/agent/workspace/GitHub__master[2020-03-04T19:28:42.933Z] at
[JIRA] (JENKINS-56987) Atlassian Jira API Changes for GDPR
Title: Message Title Josh Brozen commented on JENKINS-56987 Re: Atlassian Jira API Changes for GDPR Craig Rodrigues - Installedand it works...for some reason our Jira Build Steps were removed from our existing Jenkins job but whatever Thanks again Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198679.155502593.3541.1583791260451%40Atlassian.JIRA.
[JIRA] (JENKINS-58732) Invert pipeline-model-definition → docker-workflow dependency
Title: Message Title Devin Nusbaum commented on JENKINS-58732 Re: Invert pipeline-model-definition → docker-workflow dependency Docker-related functionality has been removed from Pipeline: Declarative Plugin as of version 1.6.0, which was just released, and resides in Docker Pipeline Plugin as of version 1.22. Pipeline: Declarative Plugin still has a dependency on Docker Pipeline Plugin for now to guide users to the latest version of Docker Pipeline Plugin so that the dependency can be safely removed in a few weeks or so. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201031.1564500516000.3537.1583791020218%40Atlassian.JIRA.
[JIRA] (JENKINS-40292) More Control of p4 task logging
Title: Message Title William Brode commented on JENKINS-40292 Re: More Control of p4 task logging Paul Allen yes I think that sounds great. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.176946.1481141079000.3533.1583790900194%40Atlassian.JIRA.
[JIRA] (JENKINS-58732) Invert pipeline-model-definition → docker-workflow dependency
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-58732 Invert pipeline-model-definition → docker-workflow dependency Change By: Devin Nusbaum Released As: docker-workflow 1.22; pipeline-model-definition 1. 5 6 . 2 (?) 0 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201031.1564500516000.3529.1583790660252%40Atlassian.JIRA.
[JIRA] (JENKINS-61156) Regression: P4 Plugin 1.10.10 trigger doesn't run jobs
Title: Message Title William Brode commented on JENKINS-61156 Re: Regression: P4 Plugin 1.10.10 trigger doesn't run jobs Matthew Smeeth Sorry for the delay I missed the notification for this. We do allow anonymous read but not Build. Maybe Karl Wirth can verify if anonymous read access is necessary for p4 plugin triggering starting at 1.10.10. Then again if you updated jenkins core or security plugins around the same time it could be one of them exposing/causing the issue. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204686.158215634.3523.1583790600194%40Atlassian.JIRA.
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner edited a comment on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Thanks for helping to improve that algorithm! I'm not sure if I miss something but for most analysis tools I think we can assume that if the file has not been changed then the warnings properties are still the same. This is already perfectly handled by the current algorithm. I marks all warnings as outstanding that share the same properties. So the interesting part are the remaining ones: the file changed somehow and some warning properties are different: the typical cases are new line numbers due to inserted or removed lines. Or, renamed content due to a refactoring (method name change, etc.). For these cases we need to find a better algorithm. I see the following ways:# Current behavior: match the source code text below and before the warning and try to find the same text in the reference file.# Rather than using a string match we are trying to match the AST of the file. This gives some better results (see https://github.com/jenkinsci/analysis-model/pull/305).# Rather than using a string match we are using the techniques behind MOSS (https://theory.stanford.edu/~aiken/moss/) to fingerprint the files (see https://github.com/jenkinsci/analysis-model/tree/moss).# Additionally use the version history to improve 1, 2 or 3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner edited a comment on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Thanks for helping to improve that algorithm! I'm not sure if I miss something but for most analysis tools I think we can assume that if the file has not been changed then the warnings properties are still the same. This is already perfectly handled by the current algorithm. I marks all warnings as outstanding that share the same properties. So the interesting part are the remaining ones: the file changed somehow and some warning properties are different: the typical cases are new line numbers due to inserted or removed lines. Or, renamed content due to a refactoring (method name change, etc.). For these cases we need to find a better algorithm. I see the following ways: 1. # Current behavior: match the source code text below and before the warning and try to find the same text in the reference file. 2. # Rather than using a string match we are trying to match the AST of the file. This gives some better results (see https://github.com/jenkinsci/analysis-model/pull/305). 3. # Rather than using a string match we are using the MOSS (https://theory.stanford.edu/~aiken/moss/) to fingerprint the files (see https://github.com/jenkinsci/analysis-model/tree/moss). 4. # Additionally use the version history to improve 1, 2 or 3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner edited a comment on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Thanks for helping to improve that algorithm! I'm not sure if I miss something but for most analysis tools I think we can assume that if the file has not been changed then the warnings properties are still the same. This is already perfectly handled by the current algorithm. I marks all warnings as outstanding that share the same properties. So the interesting part are the remaining ones: the file changed somehow and some warning properties are different: the typical cases are new line numbers due to inserted or removed lines. Or, renamed content due to a refactoring (method name change, etc.). For these cases we need to find a better algorithm. I see the following ways:# Current behavior: match the source code text below and before the warning and try to find the same text in the reference file.# Rather than using a string match we are trying to match the AST of the file. This gives some better results (see https://github.com/jenkinsci/analysis-model/pull/305).# Rather than using a string match we are using the MOSS (https://theory.stanford.edu/~aiken/moss/) to fingerprint the files (see https://github.com/jenkinsci/analysis-model/tree/moss).# Additionally use the version history to improve 1, 2 or 3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-61383) Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning
Title: Message Title Ulli Hafner commented on JENKINS-61383 Re: Current new messages detection mechanism is not working for simple line insertion in case of many similar adjacent warning Thanks for helping to improve that algorithm! I'm not sure if I miss something but for most analysis tools I think we can assume that if the file has not been changed then the warnings properties are still the same. This is already perfectly handled by the current algorithm. I marks all warnings as outstanding that share the same properties. So the interesting part are the remaining ones: the file changed somehow and some warning properties are different: the typical cases are new line numbers due to inserted or removed lines. Or, renamed content due to a refactoring (method name change, etc.). For these cases we need to find a better algorithm. I see the following ways: 1. Current behavior: match the source code text below and before the warning and try to find the same text in the reference file. 2. Rather than using a string match we are trying to match the AST of the file. This gives some better results (see https://github.com/jenkinsci/analysis-model/pull/305). 3. Rather than using a string match we are using the MOSS (https://theory.stanford.edu/~aiken/moss/) to fingerprint the files (see https://github.com/jenkinsci/analysis-model/tree/moss). 4. Additionally use the version history to improve 1, 2 or 3. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-61407) Provide boolean response of copyArtifacts
Title: Message Title
thomas winderweedle created an issue
Jenkins / JENKINS-61407
Provide boolean response of copyArtifacts
Issue Type:
Improvement
Assignee:
Unassigned
Components:
copyartifact-plugin
Created:
2020-03-09 21:20
Labels:
plugin jenkins
Priority:
Minor
Reporter:
thomas winderweedle
Hello, I have a use case in which I attempt to pull artifacts, which may or may not exist, from many different jobs. If an artifact does not exist that's OK and my pipeline can continue, but only if I know which of my copyArtifacts calls failed so I can avoid trying to use those artifacts later on. I would like to be able to do something like this in my pipeline: artifactsFound = copyArtifacts. if (!artifactsFound) { make note of the details of this call }
Add Comment
[JIRA] (JENKINS-61405) Stage post conditions doomed by build result becoming unstable
Title: Message Title
Jim D updated an issue
Jenkins / JENKINS-61405
Stage post conditions doomed by build result becoming unstable
Change By:
Jim D
In a pipeline with multiple sequential stages that typically have either an unstable or a success result, stage post conditions can't be used to take any meaningful action, because one unstable stage dooms the subsequent stages to fire the unsuccessful post condition instead of the success post condition.Pipeline: {noformat}pipeline {agent anystages {stage('First') {steps {echo 'Before step with error'catchError(message: 'Step had error.', stageResult: 'UNSTABLE') {sh 'nonexistentcommand'}echo 'After step with error'}post {success {echo 'First stage post success'}unsuccessful {echo 'First stage post unsuccessful'}}}stage('Second') {steps {echo 'Stage after unstable stage'}post {success {echo 'Second stage post success'}unsuccessful {echo 'Second stage post unsuccessful'}}}}}{noformat}Console Output: {noformat}Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] nodeRunning on Jenkins in ...[Pipeline] {[Pipeline] stage[Pipeline] { (First)[Pipeline] echoBefore step with error[Pipeline] catchError[Pipeline] {[Pipeline] sh+ nonexistentcommand.../script.sh: line 1: nonexistentcommand: command not found[Pipeline] }ERROR: Step had error.ERROR: script returned exit code 127[Pipeline] // catchError[Pipeline] echoAfter step with errorPost stage[Pipeline] echoFirst stage post unsuccessful[Pipeline] }[Pipeline] // stage[Pipeline] stage[Pipeline] { (Second)[Pipeline] echoStage after unstable stagePost stage[Pipeline] echoSecond stage post unsuccessful[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of PipelineFinished: FAILURE{noformat}Resolved issue https://issues.jenkins-ci.org/browse/JENKINS-52114 references making the post conditions "more stage specific", but from this test, the conditions don't seem stage-specific at all. It's really unclear what the current behavior for the stage post conditions is supposed to be. Unresolved issue https://issues.jenkins-ci.org/browse/JENKINS-59469 is a little bit similar, in that it asks for a variable with the stage result that can be used in the post section. That would address our overall use case here too (which is sending per-stage notifications). But just having post conditions that referred to the stage would be helpful. This behavior I think is also described in the commentary on JENKINS-39203:
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title
Mez Pahlan commented on JENKINS-58054
Re: Support release notes
Hi Jose Salgado! This should already be available to use. I use the following syntax for environment variables although in a pipeline project. However the same should work for Freestyle too. Try this: ${RELEASENOTES} If that doesn't work can you raise a new issue and we can discuss it there.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.3510.1583787360265%40Atlassian.JIRA.
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Mark Waite commented on JENKINS-61357 Re: every time I click the Save button in Configure System Jenkins Crashes Is the issue still visible when you use git plugin 4.1.1? What about 4.0.0? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204942.1583438464000.3507.1583786520127%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche commented on JENKINS-36544 Re: Allow setting environment variables for dynamic ec2 slaves Turns out the original PR did resolve this, but only for Jenkins versions up to and including v2.204. As of 2.205, the Configure Clouds block moved to a new page, and that broke the Node Properties block. New PR has been opened to address this, which should now work on versions before and after 2.205: https://github.com/jenkinsci/ec2-plugin/pull/440 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3495.1583784900282%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche assigned an issue to Joe Hansche Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Assignee: Francis Upton Joe Hansche Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3471.1583784722079%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche updated JENKINS-36544 Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3483.1583784722294%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche started work on JENKINS-36544 Change By: Joe Hansche Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3458.1583784721624%40Atlassian.JIRA.
[JIRA] (JENKINS-61406) Allow for use of password-based encryption of confidential store
Title: Message Title Matt Sicker created an issue Jenkins / JENKINS-61406 Allow for use of password-based encryption of confidential store Issue Type: Improvement Assignee: Unassigned Components: core Created: 2020-03-09 20:05 Priority: Minor Reporter: Matt Sicker Related to JENKINS-58743, the confidential store could potentially be hardened by requiring a password to unlock it such as via PBEWithHmacSHA256AndAES_256 or potentially PBKDF2WithHmacSHA256 (not sure on the latter). Use of some form of authenticated encryption is preferred over plain encryption, and in this case, we can use EtM as mentioned in the OWASP guide. In order for the password to be entered initially to unlock Jenkins, based on some exploratory testing, I've found that there is very little Jenkins functionality that can be relied upon at this point in the initialization process, so I have two initial suggested implementation ideas: Create a separate servlet and filter to prevent Jenkins from loading until the initial unlock password is submitted. This form could also potentially be used for implementing JENKINS-58743. Use System.console() to read a password. This is fairly low tech and doesn't require much more than a lock to initialize on demand. I'm still working on a PoC for this and will link in the comments.
[JIRA] (JENKINS-61405) Stage post conditions doomed by build result becoming unstable
Title: Message Title
Jim D created an issue
Jenkins / JENKINS-61405
Stage post conditions doomed by build result becoming unstable
Issue Type:
Bug
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2020-03-09 20:02
Environment:
Jenkins ver. 2.176.3 Pipeline: Declarative 1.3.9
Priority:
Major
Reporter:
Jim D
In a pipeline with multiple sequential stages that typically have either an unstable or a success result, stage post conditions can't be used to take any meaningful action, because one unstable stage dooms the subsequent stages to fire the unsuccessful post condition instead of the success post condition. Pipeline:
pipeline {
agent any
stages {
stage('First') {
steps {
echo 'Before step with error'
catchError(message: 'Step had error.', stageResult: 'UNSTABLE') {
sh 'nonexistentcommand'
}
echo 'After step with error'
}
post {
success {
echo 'First stage post success'
}
unsuccessful {
echo 'First stage post unsuccessful'
}
}
}
stage('Second') {
steps {
echo 'Stage after unstable stage'
}
post {
success {
echo 'Second stage post success'
}
unsuccessful {
echo 'Second stage post unsuccessful'
}
}
}
}
}
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL The 2.2.3 snapshot works. However, using Plugin v 2.1 and 2.2.2 I'm not able to reproduce the Jira issue as reported . In each case I get the correct default value selected. (see screenshot below)Nonetheless, I'm using an older version of [Jenkins ver. 2.121.3 and |https://jenkins.io/] [Jenkins ver. 2.187|https://jenkins.io/] Is it possible that this could be the difference causing the issue?!image-2020-03-09-15-50-25-634.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204555.1581528008000.3452.1583783940173%40Atlassian.JIRA.
[JIRA] (JENKINS-61357) every time I click the Save button in Configure System Jenkins Crashes
Title: Message Title Steven Fransen commented on JENKINS-61357 Re: every time I click the Save button in Configure System Jenkins Crashes just updated to 4.2.1 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204942.1583438464000.3449.1583783880117%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos edited a comment on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL It is not clear what issue this PR is resolving The 2 . Using 2.3 snapshot works. However, using Plugin v 2.1 and 2.2.2 I'm not able to reproduce the Jira issue as reported . In each case I get the correct default value selected. (see screenshot below) Nonetheless, I'm using an older version of [Jenkins ver. 2.121.3|https://jenkins.io/]Is it possible that this could be the difference causing the issue? !image-2020-03-09-15-50-25-634.png! Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204555.1581528008000.3447.1583783700228%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos updated an issue Jenkins / JENKINS-61068 Active Choices radio parameter has incorrect default value on parambuild URL Change By: Ioannis Moutsatsos Attachment: image-2020-03-09-15-50-25-634.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204555.1581528008000.3441.1583783460363%40Atlassian.JIRA.
[JIRA] (JENKINS-61068) Active Choices radio parameter has incorrect default value on parambuild URL
Title: Message Title Ioannis Moutsatsos commented on JENKINS-61068 Re: Active Choices radio parameter has incorrect default value on parambuild URL It is not clear what issue this PR is resolving. Using Plugin v 2.1 and 2.2.2 I'm not able to reproduce Jira issue as reported In each case I get the correct default value selected. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204555.1581528008000.3444.1583783460441%40Atlassian.JIRA.
[JIRA] (JENKINS-36954) RobotFramework Plugin is not available in the "Add Post Build action"
Title: Message Title Ian Williams updated an issue Jenkins / JENKINS-36954 RobotFramework Plugin is not available in the "Add Post Build action" Change By: Ian Williams Comment: We were using v-1.6.4, which was the latest at the time. We have not tested w/higher. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173011.146953983.3437.1583783100156%40Atlassian.JIRA.
[JIRA] (JENKINS-36954) RobotFramework Plugin is not available in the "Add Post Build action"
Title: Message Title Ian Williams commented on JENKINS-36954 Re: RobotFramework Plugin is not available in the "Add Post Build action" We were using v-1.6.4, which was the latest at the time. We have not tested w/higher. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173011.146953983.3434.1583782980164%40Atlassian.JIRA.
[JIRA] (JENKINS-61404) Create README.md in Veracode Scan Plugin repo
Title: Message Title Dennis Gu created an issue Jenkins / JENKINS-61404 Create README.md in Veracode Scan Plugin repo Issue Type: Story Assignee: Dennis Gu Components: veracode-scan-plugin Created: 2020-03-09 18:55 Priority: Minor Reporter: Dennis Gu Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins
[JIRA] (JENKINS-61404) Create README.md in Veracode Scan Plugin repo
Title: Message Title Dennis Gu updated an issue Jenkins / JENKINS-61404 Create README.md in Veracode Scan Plugin repo Change By: Dennis Gu Create README.md file in veracode-scan-plugin repo. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205058.158378010.3429.1583780160341%40Atlassian.JIRA.
[JIRA] (JENKINS-61353) UnresolvedAddressException in JNLP client running in Docker container
Title: Message Title Mark Waite commented on JENKINS-61353 Re: UnresolvedAddressException in JNLP client running in Docker container I should have been more clear. The DNS resolver that I suspect is failing is inside the docker swarm, not in your corporate infrastructure. I'm not a Docker swarm expert by any stretch, but I suspect there is a DNS resolver inside it which provides DNS resolution as docker images are executed on various nodes in the swarm. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204046.157909594.3427.1583779380141%40Atlassian.JIRA.
[JIRA] (JENKINS-61403) Update Version Number Library to 1.7
Title: Message Title Esther Álvarez Feijoo updated an issue Jenkins / JENKINS-61403 Update Version Number Library to 1.7 Change By: Esther Álvarez Feijoo Acceptance-test-harness is using version-number:1.1, while the latest version is 1.7 1.1 has several bugs (for example VersionNumber#digit is not working as expected), which were solved in the next versions. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205057.1583777053000.3425.1583777220062%40Atlassian.JIRA.
[JIRA] (JENKINS-61403) Update Version Number Library to 1.7
Title: Message Title Esther Álvarez Feijoo created an issue Jenkins / JENKINS-61403 Update Version Number Library to 1.7 Issue Type: Improvement Assignee: Unassigned Components: acceptance-test-harness Created: 2020-03-09 18:04 Priority: Minor Reporter: Esther Álvarez Feijoo Acceptance-test-harness is using version-number:1.1, while the latest version is 1.7 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Jose Salgado edited a comment on JENKINS-58054 Re: Support release notes Hi Team! I'm just wondering if the interpolation for the filed "Release Notes" will work, I'm trying to the the following in my job: RELEASENOTES=$(git log --pretty=oneline --abbrev-commit | head -5)and then doing the following in my plugin: Screen Shot 2020 !screenshot - 03-09 at 11 1 . 38.17 AM png|thumbnail! but I end getting $RELEASENOTES in my plugin release notes information. Any clue about when is this will be available? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.3422.1583775660153%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Jose Salgado commented on JENKINS-58054 Re: Support release notes Hi Team! I'm just wondering if the interpolation for the filed "Release Notes" will work, I'm trying to the the following in my job: RELEASENOTES=$(git log --pretty=oneline --abbrev-commit | head -5) and then doing the following in my plugin: Screen Shot 2020-03-09 at 11.38.17 AM but I end getting $RELEASENOTES in my plugin release notes information. Any clue about when is this will be available? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.3419.1583775600138%40Atlassian.JIRA.
[JIRA] (JENKINS-58054) Support release notes
Title: Message Title Jose Salgado updated an issue Jenkins / JENKINS-58054 Support release notes Change By: Jose Salgado Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.200075.1560793667000.3416.1583775540239%40Atlassian.JIRA.
[JIRA] (JENKINS-61356) Unable to connect to slave via Launch Agent mode(SSH)
Title: Message Title Charles Smith commented on JENKINS-61356 Re: Unable to connect to slave via Launch Agent mode(SSH) Matt Sicker Hi Matt, This is the first build agent that has been added to our Jenkins instance. We are running the latest plugins and Jenkins version. As far as a test, all you have to do is create a new build agent and attempt to launch it and it produces the PEM error. Please let me know if you need anymore information apart from what has already been provided. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204941.158343741.3414.1583775480220%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-51495 descriptorRadioList does not honor DescriptorVisibilityFilter Change By: Tim Jacomb Labels: 2.222.1-rejected lts-candidate newbie-friendly regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190856.1527063169000.3410.1583774580270%40Atlassian.JIRA.
[JIRA] (JENKINS-61284) Grey bar below textarea in read only mode looks weird
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61284 Grey bar below textarea in read only mode looks weird Change By: Tim Jacomb Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204859.1583051635000.3407.1583774520189%40Atlassian.JIRA.
[JIRA] (JENKINS-61279) Update version number dependency to 1.7
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61279 Update version number dependency to 1.7 Change By: Tim Jacomb Labels: lts-candidate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204854.1582987621000.3406.1583774520104%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick commented on JENKINS-61007 Re: pipeline-model-definition is using findbugs without providing / depending on it JENKINS-41827 would be helpful here. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3404.1583773800144%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick commented on JENKINS-61007 Re: pipeline-model-definition is using findbugs without providing / depending on it Filed a fix. BTW I came across this because it was mentioned twice in the 2.224 changelog, though I see no reason to believe that it is specific to a given version of core. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3399.1583773320387%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick updated JENKINS-61007 Jenkins / JENKINS-61007 pipeline-model-definition is using findbugs without providing / depending on it Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3401.1583773320422%40Atlassian.JIRA.
[JIRA] (JENKINS-61401) NSEE for files that are in the console log
Title: Message Title Andreas Pabst updated JENKINS-61401 Jenkins / JENKINS-61401 NSEE for files that are in the console log Change By: Andreas Pabst Status: In Progress Fixed but Unreleased Resolution: Fixed Released As: https://github.com/jenkinsci/metrics-aggregation-plugin/releases/tag/metrics-aggregation-0.1.2 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205055.1583765548000.3394.1583773020504%40Atlassian.JIRA.
[JIRA] (JENKINS-61401) NSEE for files that are in the console log
Title: Message Title Andreas Pabst updated JENKINS-61401 Jenkins / JENKINS-61401 NSEE for files that are in the console log Change By: Andreas Pabst Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205055.1583765548000.3396.1583773020533%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Tim Jacomb commented on JENKINS-61398 Re: Source Code Management for build job is forgotten on save PR submitted: https://github.com/jenkinsci/jenkins/pull/4560 I had a look in core and couldn't see any other issues with this. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3385.1583772840193%40Atlassian.JIRA.
[JIRA] (JENKINS-61164) Configure Clouds - no credentials visible for vSphere Cloud
Title: Message Title pjdarton commented on JENKINS-61164 Re: Configure Clouds - no credentials visible for vSphere Cloud FAO anyone watching: this will be fixed in the next release. In the meantime, anyone affected by this issue can grab an as-yet-unreleased build from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204698.1582196162000.3380.1583772660729%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-61007 pipeline-model-definition is using findbugs without providing / depending on it Change By: Jesse Glick Assignee: Andrew Bayer Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3374.1583772600714%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick started work on JENKINS-61007 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3377.1583772600758%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-61007 pipeline-model-definition is using findbugs without providing / depending on it Change By: Jesse Glick Priority: Minor Critical Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3370.1583772600621%40Atlassian.JIRA.
[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title pjdarton updated JENKINS-61131 Jenkins / JENKINS-61131 vsphere-cloud: Credentials selection is broken in UI since 2.22 Change By: pjdarton Status: In Progress Fixed but Unreleased Assignee: pjdarton Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204653.1582040133000.3358.1583772540750%40Atlassian.JIRA.
[JIRA] (JENKINS-61401) NSEE for files that are in the console log
Title: Message Title Andreas Pabst started work on JENKINS-61401 Change By: Andreas Pabst Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205055.1583765548000.3356.1583772480218%40Atlassian.JIRA.
[JIRA] (JENKINS-61131) vsphere-cloud: Credentials selection is broken in UI since 2.22
Title: Message Title pjdarton commented on JENKINS-61131 Re: vsphere-cloud: Credentials selection is broken in UI since 2.22 PR merged; it'll be fixed in the next release. In the meantime, anyone affected by this issue can grab an as-yet-unreleased build from https://ci.jenkins.io/job/Plugins/job/vsphere-cloud-plugin/job/master/lastSuccessfulBuild/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204653.1582040133000.3345.1583772420295%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Tim Jacomb commented on JENKINS-51495 Re: descriptorRadioList does not honor DescriptorVisibilityFilter This seems to have caused: https://issues.jenkins-ci.org/browse/JENKINS-61398?focusedCommentId=386921=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-386921 Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190856.1527063169000.3337.1583772300302%40Atlassian.JIRA.
[JIRA] (JENKINS-61007) pipeline-model-definition is using findbugs without providing / depending on it
Title: Message Title Jesse Glick commented on JENKINS-61007 Re: pipeline-model-definition is using findbugs without providing / depending on it Able to reproduce simply by Running 2.224 on a new home dir. Selecting just Pipeline from setup wizard. Creating a Pipeline job using the hello world sample. Running it. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204477.1581032748000.3342.1583772300364%40Atlassian.JIRA.
[JIRA] (JENKINS-51495) descriptorRadioList does not honor DescriptorVisibilityFilter
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-51495 descriptorRadioList does not honor DescriptorVisibilityFilter Change By: Tim Jacomb Labels: 2.222.1-rejected lts-candidate newbie-friendly regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.190856.1527063169000.3332.1583772240702%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title
Tim Jacomb edited a comment on JENKINS-61398
Re: Source Code Management for build job is forgotten on save
Looking at it in a debugger: !screenshot-1.png|thumbnail! String descriptorId = config.getString("value");is equal to 1 !this.png|thumbnail! 'this' returns a list with a null scm and a git scm !screenshot-2.png|thumbnail! getting the id on the git scm returns the class name and1 is not equal to hudson.plugins.git.GitSCMso the check fails and it defaults to the first item in the list (nullscm)
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3326.1583772240570%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title
Tim Jacomb commented on JENKINS-61398
Re: Source Code Management for build job is forgotten on save
Looking at it in a debugger:String descriptorId = config.getString("value"); is equal to 1'this' returns a list with a null scm and a git scmgetting the id on the git scm returns the class name
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3323.1583772181133%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Tim Jacomb Attachment: screenshot-2.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3312.1583772180971%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Tim Jacomb Attachment: this.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3306.1583772180853%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Tim Jacomb updated an issue Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Tim Jacomb Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3300.1583772120427%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Jesse Glick started work on JENKINS-61398 Change By: Jesse Glick Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3284.1583771641080%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Jesse Glick updated JENKINS-61398 Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3289.1583771641181%40Atlassian.JIRA.
[JIRA] (JENKINS-61402) Jenkins Docker Start Up Very Slow
Title: Message Title Brian Pham created an issue Jenkins / JENKINS-61402 Jenkins Docker Start Up Very Slow Issue Type: Bug Assignee: Unassigned Components: core Created: 2020-03-09 16:30 Environment: Docker (jenkins/jenkins:lts-slim)Jenkins 2.204.5 Operation System: CoreOS 2247.7.0 Plugins All Running Latest antisamy-markup-formatter build-timeout cloudbees-folder credentials-binding email-ext git github-branch-source gradle ldap mailer matrix-auth pam-auth pipeline-github-lib pipeline-stage-view ssh-slaves timestamper workflow-aggregator ws-cleanup ansible ansicolor artifactory blueocean build-flow-plugin:0.20 build-flow-test-aggregator:1.2 build-name-setter build-user-vars-plugin build-with-parameters buildgraph-view console-column-plugin cygpath date-parameter description-column-plugin downstream-buildview ec2-fleet elastic-axis embeddable-build-status ghprb github google-login jobConfigHistory kpp-management-plugin performance phabricator-plugin rebuild role-strategy s3 scala-junit-name-decoder simple-parameterized-builds-report simple-theme-plugin slack test-stability thinBackup throttle-concurrents view-job-filters xvfb Priority: Major Reporter: Brian Pham We have 3 separate Jenkins master machines running on the same version for different environments and all configured the same exact way. We are noticing that one of the Jenkins master node is starting up very slowly up to 30+ before it fully starts up. The other 2 machines start up fairly quickly. I am trying to look in the logs, but not seeing anything that stands out. CPU / mem usage seems very low. This is what I am seeing in the logs. Is there anything else I can look to see why after Jenkins initialized it takes so long? In the logs, I can
[JIRA] (JENKINS-60779) Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter
Title: Message Title Paul Thevenot edited a comment on JENKINS-60779 Re: Pipeline Build Step: Remove Message converting string Parameter to Extensible Choice Parameter I think the same warning is shown while using the [Active Choice Plugin|[https://github.com/jenkinsci/active-choices-plugin]] and it would make sense to add the following class classes org.biouno.unochoice.CascadeChoiceParameter, org.biouno.unochoice. AbstractUnoChoiceParameter ChoiceParameter to the codition condition you added in your pull request (l180). I don't see how we could pass a parameter to this plugin whitout using a string parameter. What do you think? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204042.1579085441000.3280.1583770020262%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Mark Waite commented on JENKINS-61398 Re: Source Code Management for build job is forgotten on save Thanks Oleg Nenashev. I've confirmed that I can duplicate the problem with the tip of the master branch and it is no longer visible if I revert the JENKINS-51495 change. Should I submit a pull request to revert the change or would you prefer to approach it differently? Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3268.1583768160169%40Atlassian.JIRA.
[JIRA] (JENKINS-36544) Allow setting environment variables for dynamic ec2 slaves
Title: Message Title Joe Hansche updated an issue Jenkins / JENKINS-36544 Allow setting environment variables for dynamic ec2 slaves Change By: Joe Hansche Attachment: Screen Shot 2020-03-09 at 11.29.38 AM.png Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.172564.1468000478000.3233.1583767920819%40Atlassian.JIRA.
[JIRA] (JENKINS-45871) Failed test sets all steps to unstable
Title: Message Title
Devin Nusbaum edited a comment on JENKINS-45871
Re: Failed test sets all steps to unstable
{quote} The implementation for this is awkward. The junit step does indeed set the stage status to UNSTABLE, but it also quickly sets the whole build status to UNSTABLE.{quote} Indeed, there is not really any easy way to truly fix the issue, so the reality is that there are multiple kinds of "results" in Pipelines: {{Run.getResult}}, {{ErrorAction}}, and now {{WarningAction}}. {quote} Can the junit plugin only change the status for the stage it is called in?{quote} The main reason why we couldn't do something like that is that it would be a breaking change for everyone that currently checks things like {{currentBuild.currentResult}} inside of the Pipeline. Step-level "results" handled via {{WarningAction}} have no relation to that result, and there is no easy way to fix that, because we need a {{FlowNode}} context to get a {{WarningAction}}, which cannot be provided by {{currentBuild.currentResult}}. {quote} When changing the whole build status to UNSTABLE, the fact that it also changed the stage status is not visible anyway.{quote} As far as I know, in Blue Ocean and the Pipeline Steps view, the overall build result no longer changes the displayed result for individual steps and stages.If you are talking about Pipeline Stage View, then yes, that plugin needs to be updated to use {{WarningAction}} correctly, that is tracked as JENKINS-58783.
Add Comment
This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
[JIRA] (JENKINS-45871) Failed test sets all steps to unstable
Title: Message Title Devin Nusbaum commented on JENKINS-45871 Re: Failed test sets all steps to unstable The implementation for this is awkward. The junit step does indeed set the stage status to UNSTABLE, but it also quickly sets the whole build status to UNSTABLE. Indeed, there is not really any easy to truly fix the issue, so the reality is that there are multiple kinds of "results" in Pipelines: Run.getResult, ErrorAction, and now WarningAction. Can the junit plugin only change the status for the stage it is called in? The main reason why we couldn't do something like that is that it would be a breaking change for everyone that currently checks things like currentBuild.currentResult inside of the Pipeline. Step-level "results" handled via WarningAction have no relation to that result, and there is no easy way to fix that, because we need a FlowNode context to get a WarningAction, which cannot be provided by currentBuild.currentResult. When changing the whole build status to UNSTABLE, the fact that it also changed the stage status is not visible anyway. As far as I know, in Blue Ocean and the Pipeline Steps view, the overall build result no longer changes the displayed result for individual steps and stages. If you are talking about Pipeline Stage View, then yes, that plugin needs to be updated to use WarningAction correctly, that is tracked as JENKINS-58783. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)
[JIRA] (JENKINS-45871) Failed test sets all steps to unstable
Title: Message Title Devin Nusbaum closed an issue as Duplicate Jenkins / JENKINS-45871 Failed test sets all steps to unstable Change By: Devin Nusbaum Status: Reopened Closed Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.184084.1501484815000.3225.1583767860989%40Atlassian.JIRA.
[JIRA] (JENKINS-61300) Search field size wrong after screen resize and for long texts
Title: Message Title Zbynek Konecny resolved as Fixed Jenkins / JENKINS-61300 Search field size wrong after screen resize and for long texts Change By: Zbynek Konecny Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.204880.1583187672000.3216.1583767800108%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Oleg Nenashev commented on JENKINS-61398 Re: Source Code Management for build job is forgotten on save JENKINS-51495 is suspected to be the root cause, because it modifies descriptorRadioList being used in SCM configuration sections Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3206.1583767140195%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Mark Waite assigned an issue to Mark Waite Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Mark Waite Assignee: Tim Jacomb Mark Waite Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3203.1583766600486%40Atlassian.JIRA.
[JIRA] (JENKINS-61398) Source Code Management for build job is forgotten on save
Title: Message Title Daniel Beck updated an issue Jenkins / JENKINS-61398 Source Code Management for build job is forgotten on save Change By: Daniel Beck Labels: Git-plugin SCM regression Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205052.1583762717000.3200.1583766600317%40Atlassian.JIRA.
[JIRA] (JENKINS-61375) Cannot disable CSRF
Title: Message Title Daniel Beck commented on JENKINS-61375 Re: Cannot disable CSRF Jenkins on master uses trigger remote paramaterized job Your client in that case is https://plugins.jenkins.io/Parameterized-Remote-Trigger/ Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205028.1583530066000.3196.1583766420120%40Atlassian.JIRA.
[JIRA] (JENKINS-61401) NSEE for files that are in the console log
Title: Message Title Ulli Hafner commented on JENKINS-61401 Re: NSEE for files that are in the console log You can guard it with RepositoryStatistics#contains() Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.205055.1583765548000.3136.1583765760085%40Atlassian.JIRA.
[JIRA] (JENKINS-61399) Improve How to use RefSpecsSCMSourceTrait
Title: Message Title
Mateus Miranda updated an issue
Jenkins / JENKINS-61399
Improve How to use RefSpecsSCMSourceTrait
Change By:
Mateus Miranda
I've been trying to populate the RefSpec template on the GitSCM source, but I cannot seem to get it to work. I've failed to find any examples of how to do it.Does anyone have an idea how to use it?{code:java}package utilsimport groovy.transform.builder.Builderimport groovy.transform.builder.SimpleStrategyimport javaposse.jobdsl.dsl.DslFactoryimport javaposse.jobdsl.dsl.Jobimport javaposse.jobdsl.dsl.jobs.MultibranchWorkflowJob// Created to make it easy to creade new jobs without duplicating the code@Builder(builderStrategy = SimpleStrategy, prefix = '')class GithubPipeline {String viewPrefixString repositoryString jobSuffix = ""String includes = "*"String jenkinsfileLocation = "Jenkinsfile"Boolean discoverBranches = trueBoolean discoverTags = trueBoolean includeMasterRef = falseMultibranchWorkflowJob build(DslFactory dslFactory) {def cleanedRepoString = this.repository.toLowerCase().replaceAll(/_/, '-');def jobId = "${this.viewPrefix.toLowerCase()}-${cleanedRepoString}"if (this.jobSuffix) jobId += "-${jobSuffix}"dslFactory.multibranchPipelineJob(jobId) {branchSources {github {id(jobId)includes(this.includes)repoOwner('comp')repository(this.repository)scanCredentialsId('github-appscicomp-dev-token')checkoutCredentialsId('github-appscicomp-dev-token')}}factory {workflowBranchProjectFactory {scriptPath(this.jenkinsfileLocation)}}configure {def traits = it / sources / data / 'jenkins.branch.BranchSource' / source / traitsif (this.discoverBranches) {traits << 'org.jenkinsci.plugins.github_branch_source.BranchDiscoveryTrait' { strategyId(3) // detect all branches -refer the plugin source code for various options}}if (this.discoverTags) {traits << 'org.jenkinsci.plugins.github_branch_source.TagDiscoveryTrait' { }}if (this.includeMasterRef) {traits << 'jenkins.plugins.git.traits.RefSpecsSCMSourceTrait' { tempates << 'jenkins.plugins.git.traits.RefSpecsSCMSourceTrait$RefSpecTemplate' { value('+refs/heads/master:refs/remotes/@{remote}/master') }}}}orphanedItemStrategy {discardOldItems {daysToKeep(20)numToKeep(25)}}}}}{code} The part which I'm struggling is: {code:java} traits <<
