[JIRA] (JENKINS-60707) option to configure Default Checkout
Title: Message Title Viachaslau Kabak created an issue Jenkins / JENKINS-60707 option to configure Default Checkout Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2020-01-09 07:58 Priority: Major Reporter: Viachaslau Kabak In pipelines we need to add some options to modify default checkout: Path of the reference repo to use during clone: to use baregit repo path Sparse checkout path these options are available for checkout in default and in pipeline step. It would be nice to have them in Declarative pipeline in options for pipeline. Add Comment
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref".h4. ExamplePipeline job created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{g...@git.serv.d.net:ts-source.git}} * Refspec: {{+refs/heads/\*:refs/remotes/origin/\* +refs/changes/\*:refs/remotes/origin/\*}} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code:groovy}println readTrusted(".jenkins/test.groovy"){code}h4. Build log{code:none}Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test.groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] readTrusted[Pipeline] End of Pipelinehudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128:fatal: Couldn't find remote ref refs/heads/4eedb3bfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at
[JIRA] (JENKINS-60706) TeamConcert plugin 1.3.0 "RTC-PostBuildDeliver"
Title: Message Title SenthilVP kumar created an issue Jenkins / JENKINS-60706 TeamConcert plugin 1.3.0 "RTC-PostBuildDeliver" Issue Type: Bug Assignee: Unassigned Components: teamconcert-plugin Created: 2020-01-09 07:05 Priority: Blocker Reporter: SenthilVP kumar We are facing issues in the Jenkins RTC post build deliver. Jenkins version - 2.176.2 Team Concert plugin version - 1.3.0 RTC Server Version: 6.0.6.1 Error Message: RTC Server https://xxx:9443/ccm is not compatible for post build deliver. Expected server version is 6.0.4. Error Message: The Team Concert server does not have the support required to avoid using the toolkit: Your server is version 6.0.6.1. Note: we have set the minimum client version to 6.0.5 While checking the plugin source code, it was checking for the version Compatibility as "6.0.4 client version" Add Comment
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref".h4. ExamplePipeline job created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{g...@git.serv.d.net:ts-source.git}} * Refspec: {{+refs/heads/\*:refs/remotes/origin/\* +refs/changes/\*:refs/remotes/origin/\*}} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code:groovy}println readTrusted(".jenkins/test.groovy"){code}h4. Build log{code:none}Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test.groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] readTrusted[Pipeline] End of Pipelinehudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128:fatal: Couldn't find remote ref refs/heads/4eedb3bfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref".h4. ExamplePipeline job created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{g...@git.serv.d.net:ts-source.git}} * Refspec: {{+refs/heads/\*:refs/remotes/origin/\* +refs/changes/\*:refs/remotes/origin/\*}} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code:groovy}println readTrusted(".jenkins/test.groovy"){code}h4. Build log{code:none}Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test.groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] readTrusted[Pipeline] End of Pipelinehudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128:fatal: Couldn't find remote ref refs/heads/4eedb3bfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Aleksi Simell commented on JENKINS-60687 Re: Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB You mean from https://plugins.jenkins.io/serenity? Currently, you could write custom data to InfluxDB, but then you would need to do the data parsing yourself in your job. However, that might be a bit too troublesome to do in a pipeline, and most probably something the pipeline isn't intended to do anyway. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203931.1578474488000.5428.1578550320152%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title Aleksi Simell commented on JENKINS-54445 Re: Publishing data to influxDb Hi _peedus, I had completely forgotten this one. I made a note for myself to have this in my own "backlog". I will try to make this ASAP, but might not make it for the next release (I try to make releases ~once a month or so). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195207.1541406402000.5424.1578550141001%40Atlassian.JIRA.
[JIRA] (JENKINS-60311) contentReplace does not appear in the Snippet Generator
Title: Message Title mo xun started work on JENKINS-60311 Change By: mo xun Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203307.1574923665000.5414.1578541380309%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick updated JENKINS-55017 Jenkins / JENKINS-55017 Allow advanced configuration for other s3 providers Change By: Jesse Glick Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.196055.1543946313000.5403.1578535810416%40Atlassian.JIRA.
[JIRA] (JENKINS-60705) Add support for SCRAM-SHA-1(-PLUS), SCRAM-SHA-256(-PLUS)
Title: Message Title Neustradamus * created an issue Jenkins / JENKINS-60705 Add support for SCRAM-SHA-1(-PLUS), SCRAM-SHA-256(-PLUS) Issue Type: Improvement Assignee: Florian Schmaus Components: jabber-plugin, jabber-server-plugin Created: 2020-01-09 00:59 Priority: Blocker Reporter: Neustradamus * "When using the SASL SCRAM mechanism, the SCRAM-SHA-256-PLUS variant SHOULD be preferred over the SCRAM-SHA-256 variant, and SHA-256 variants [RFC7677] SHOULD be preferred over SHA-1 variants [RFC5802]". There is only SCRAM-SHA-1, there is not SCRAM-SHA-1-PLUS: RFC5802: Salted Challenge Response Authentication Mechanism (SCRAM) SASL and GSS-API Mechanisms: https://tools.ietf.org/html/rfc5802 RFC6120: Extensible Messaging and Presence Protocol (XMPP): Core: https://tools.ietf.org/html/rfc6120 There is not SCRAM-SHA-256(-PLUS): RFC7677: SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms: https://tools.ietf.org/html/rfc7677 - since 2015-11-02 RFC8600: Using Extensible Messaging and Presence Protocol (XMPP) for Security Information Exchange: https://tools.ietf.org/html/rfc8600 - since 2019-06-21: https://mailarchive.ietf.org/arch/msg/ietf-announce/suJMmeMhuAOmGn_PJYgX5Vm8lNA I add SCRAM-SHA-512(-PLUS): https://xmpp.org/extensions/inbox/hash-recommendations.html -PLUS variants: RFC5056: On the Use of Channel Bindings to Secure Channels:
[JIRA] (JENKINS-60704) Can you change Jabber to XMPP?
Title: Message Title Neustradamus * created an issue Jenkins / JENKINS-60704 Can you change Jabber to XMPP? Issue Type: Improvement Assignee: Florian Schmaus Components: jabber-plugin, jabber-server-plugin Created: 2020-01-09 00:55 Priority: Blocker Reporter: Neustradamus * Can you change Jabber to XMPP? https://github.com/jenkinsci/jabber-plugin https://github.com/jenkinsci/jabber-server-plugin It is XMPP since 2004. Add Comment
[JIRA] (JENKINS-60309) NPE when using with gitlab-plugin's statuses.
Title: Message Title Peter Leibiger commented on JENKINS-60309 Re: NPE when using with gitlab-plugin's statuses. I am seeing the same stack without the nullpointer, only the second part. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203304.1574879165000.5387.1578529260202%40Atlassian.JIRA.
[JIRA] (JENKINS-60702) Two calls to the build function can trigger the same run
Title: Message Title Michael Mrozek closed an issue as Not A Defect Never mind! After pawing through the code I discovered this is intentional behavior. I thought it had to be a bug because in my real job (not the simple test I posted in the description) I'm passing in different build parameters for the two calls, but due to an unrelated problem the target job wasn't actually declaring those parameters, so they got filtered out. This no longer affects me now that I've fixed the parameterization problem, but I will add that I'm not 100% sure this behavior makes sense. I assume there's a good reason for the build action folding mechanism, but if job A tells Jenkins to build downstream job B twice, I would expect Jenkins to build it twice. Jenkins / JENKINS-60702 Two calls to the build function can trigger the same run Change By: Michael Mrozek Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60096) Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script
Title: Message Title robert arles commented on JENKINS-60096 Re: Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script Daniel Vergil Thank you for the update! Very much appreciated. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202941.1573156459000.5380.1578525060131%40Atlassian.JIRA.
[JIRA] (JENKINS-60703) Question marks in pipeline stage names break parameterized input steps
Title: Message Title
Barrett Lewis updated an issue
Jenkins / JENKINS-60703
Question marks in pipeline stage names break parameterized input steps
Change By:
Barrett Lewis
Pipelines can have stages named with a question mark inside, but if that stage has an input step (with 'parameters' so that it brings up the input in a hyperlinked page) the question mark breaks the input return URI. You get a 404 when you click the hyperlink in the console to bring up the input dialog. To repro:Put this stage into a pipeline{code:java} stage('Approve?') {input {message "Should we continue?"ok "Yes, we should."parameters {string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')}}steps {echo "Hello, ${PERSON}, nice to meet you."} }{code}During pipeline execution, when coming to input step, it blocks in the console on a hyperlink "Input requested". Clicking the hyperlink takes you to the input dialog. Trying to click Ok gives a 404 since the stage name is in the URI.
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60703) Question marks in pipeline stage names break parameterized input steps
Title: Message Title
Barrett Lewis created an issue
Jenkins / JENKINS-60703
Question marks in pipeline stage names break parameterized input steps
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline
Created:
2020-01-08 23:01
Environment:
Jenkins 2.204.1 Pipeline 2.6 Pipeline: Declarative 1.5.0 Pipeline: Input Step 2.11
Priority:
Minor
Reporter:
Barrett Lewis
Pipelines can have stages named with a question mark inside, but if that stage has an input step (with 'parameters' so that it brings up the input in a hyperlinked page) the question mark breaks the input return URI. You get a 404 when you click the hyperlink in the console to bring up the input dialog. To repro: Put this stage into a pipeline
stage('Approve?')
{
input {
message "Should we continue?"
ok "Yes, we should."
parameters {
string(name: 'PERSON', defaultValue: 'Mr Jenkins', description: 'Who should I say hello to?')
}
}
steps {
echo "Hello, ${PERSON}, nice to meet you."
}
}
During pipeline execution, when coming to input step, it blocks in the console on a hyperlink "Input requested". Clicking the hyperlink takes you to the input dialog. Trying to click Ok gives a 404 since the stage name is in the URI.
[JIRA] (JENKINS-58941) Missing Overall/Read permission when authenticating with LDAP user with a long UID
Title: Message Title Paul Clark commented on JENKINS-58941 Re: Missing Overall/Read permission when authenticating with LDAP user with a long UID Francis Labrie, do you think that this is related to the 20 character AD limit (for "legacy" systems)? Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201285.1565806846000.5373.1578524400392%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Alan Champion edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Just adding weight in the hope that this may be addressed sooner rather than later.My objective has been to breakdown the legacy Jenkins jobs to run various steps as parallel stages for efficiency, with minimal change to the core scripts (which I have parameterised to accommodate either serial/parallel execution) * DSL pipeline held in SCM (Git) consists of 632 lines * builds five legacy nested Jenkins jobs as "explicitly numbered" _Primary Stages:_ ## *Prepare Environment* called 6 7 times (8 stages: 1 serial + 5 parallel + 1 serial to merge report) ## *Generate Tests* (based on historical samples) with a conditional alternative stage on to accommodate a re-run that required recycling processed data (i.e. 2 stages) ## {color:#505f79}*Verify Clean Environment*{color} (optional) in parallel with stage 2 (5 stages: 1 serial + 2 parallel + 1 serial to merge report) ## *Exec Generated Tests* (3 stages: 2 parallel same tests on +two+ baselines) ## *Compare Results* (7 stages : 1 serial + 4 parallel + 1 serial to merge report)Currently, this amounts to 25 stages including the five overhead stages to handle the parallelisation. I have evolved to this state gradually, and only after I parallelised the 1st stage, did the "too big" problem appear. Also, I had expected to improve performance and visibility further by splitting _Primary Stage_ 4 into 10+ parallel stages. I am thinking that the best way forward may involve breaking the jobs into +three+ levels (instead of two) by promoting the five _Primary Stages_ as nested pipelines.I accept that this regression testing exercise may not be the norm for most but any advice/help would be appreciated on a pragmatic way forward.Thanks, Alan
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60685) Kubernetes plugin crashes from v1.22.4
Title: Message Title MARY Olivier commented on JENKINS-60685 Re: Kubernetes plugin crashes from v1.22.4 Same for me since kubernetes 1.15.X -> 1.16.3 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203929.1578472634000.5275.1578523321899%40Atlassian.JIRA.
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title
Alan Champion edited a comment on JENKINS-37984
Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Just adding weight in the hope that this may be addressed sooner rather than later.My objective has been to breakdown the legacy Jenkins jobs to run various steps as parallel stages for efficiency, with minimal change to the core scripts (which I have parameterised to accommodate either serial/parallel execution) * DSL pipeline held in SCM (Git) consists of 632 lines * builds five legacy nested Jenkins jobs as "explicitly numbered" _Primary Stages:_ ## *Prepare Environment* called 6 times (8 stages: 1 serial + 5 parallel + 1 serial to merge report) ## *Generate Tests* (based on historical samples) with a conditional alternative stage on a re-run (i.e. 2 stages) ## {color:#505f79}*Verify Clean Environment*{color} (optional) in parallel with stage 2 (5 stages: 1 serial + 2 parallel + 1 serial to merge report) ## *Exec Generated Tests* (3 stages: 2 parallel same tests on +two+ baselines) ## *Compare Results* ( 7 stages 1 serial + 4 parallel + 1 serial to merge report) Furthermore Currently , this amounts to 25 stages including the five overhead stages to handle the parallelisation. Also, I had expected to improve performance and visibility further by splitting _Primary Stag_e Stage_ 4 into 10+ parallel stages.I am thinking that the best way forward may involve breaking the jobs into +three+ levels (instead of two) by promoting the five _Primary Stages_ as nested pipelines.I accept that this regression testing exercise may not be the norm for most but any advice/help would be appreciated on a pragmatic way forward.Thanks, Alan
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-37984) org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script
Title: Message Title Alan Champion commented on JENKINS-37984 Re: org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: General error during class generation: Method code too large! error in pipeline Script Just adding weight in the hope that this may be addressed sooner rather than later. My objective has been to breakdown the legacy Jenkins jobs to run various steps as parallel stages for efficiency, with minimal change to the core scripts (which I have parameterised to accommodate either serial/parallel execution) DSL pipeline held in SCM (Git) consists of 632 lines builds five legacy nested Jenkins jobs as "explicitly numbered" Primary Stages: Prepare Environment called 6 times (8 stages: 1 serial + 5 parallel + 1 serial to merge report) Generate Tests (based on historical samples) with a conditional alternative stage on a re-run (i.e. 2 stages) Verify Clean Environment (optional) in parallel with stage 2 (5 stages: 1 serial + 2 parallel + 1 serial to merge report) Exec Generated Tests (3 stages: 2 parallel same tests on two baselines) Compare Results (1 serial + 4 parallel + 1 serial to merge report) Furthermore, I had expected to improve performance and visibility further by splitting _Primary Stag_e 4 into 10+ parallel stages. I am thinking that the best way forward may involve breaking the jobs into three levels (instead of two) by promoting the five Primary Stages as nested pipelines. I accept that this regression testing exercise may not be the norm for most but any advice/help would be appreciated on a pragmatic way forward. Thanks, Alan Add Comment
[JIRA] (JENKINS-60702) Two calls to the build function can trigger the same run
Title: Message Title
Michael Mrozek created an issue
Jenkins / JENKINS-60702
Two calls to the build function can trigger the same run
Issue Type:
Bug
Assignee:
Unassigned
Components:
pipeline-build-step-plugin
Created:
2020-01-08 22:14
Environment:
Jenkins 2.211 Pipeline: API 2.38 Pipeline: Build Step 2.11
Priority:
Minor
Reporter:
Michael Mrozek
I'm not certain which component is responsible for this, so I went with the Pipeline Build Step plugin. When using build to trigger another job, there seems to be a race condition where two calls to the function at approximately the same time with the same target job can both "start" the exact same run. For example, this code (the target job is irrelevant, I just happened to have an empty Freestyle job hanging around to test with):
parallel (
First : { build job: "Test/Freestyle", wait: true },
Second: { build job: "Test/Freestyle", wait: true },
)
causes the following:
Branch event
Obtained Jenkinsfile from 9c8963507d90d9cc4c8acb030efa07ca8a7d8d25
Running in Durability level: MAX_SURVIVABILITY
[Pipeline] Start of Pipeline
[Pipeline] parallel
[Pipeline] { (Branch: First)
[Pipeline] { (Branch: Second)
[Pipeline] build
Scheduling project: Test » Freestyle
[Pipeline] build
Scheduling project: Test » Freestyle
Starting building: Test »
[JIRA] (JENKINS-50864) kubernetes-cli-plugin is not working.
Title: Message Title
Ed Thorne commented on JENKINS-50864
Re: kubernetes-cli-plugin is not working.
For others that may be experiencing this issue, here's some information that may be useful. By default, the Jenkins environment on an RPM installed (Linux) system will look like the following:
SHELL=/bin/bash
USER=jenkins
PATH=/sbin:/usr/sbin:/bin:/usr/bin
PWD=/
LANG=en_US.UTF-8
HOME=/opt/jenkins
SHLVL=2
LOGNAME=jenkins
_=/etc/alternatives/java
The recommended installation instructions for kubectl on Linux have the binary installed in /usr/local/bin (not in the default path of Jenkins). Even though /usr/local/bin is in the path in bash shells, it's not in the daemon's path with the default settings. Using the PATH+WHATEVER pattern you can get /usr/local/bin in the path for shells, but not the Jenkins process. This allowed me to work around the issue in this way:
withKubeConfig([
credentialsId: '7a1146c7-1791-4197-a8fd-f6a97abec862'
// , contextName: contextName
]) {
// switch context from default to target environment
sh "kubectl config use-context ${contextName}"
// deploy the resources (without pushing)
sh 'kubectl apply -k .'
// wait for deployment to complete
sh "kubectl rollout status deployment/${projectName} --timeout=2m"
}
If I tried to set the context name in the parameter, I got the exception observed in this ticket. This likely stems from the launcher not understanding the PATH+WHATEVER modifications that add /usr/local/bin to the path for pipeline shell commands that you can see above. This feels like a shortcoming of the plugin documentation in that the kubectl binary must be in the path visible to the Jenkins process(es) which can be considerably different from traditional login shell paths or even pipeline shell paths. With the documented installation location as /usr/local/bin, I'm surprised more instances of this haven't occurred.
Add Comment
[JIRA] (JENKINS-60096) Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script
Title: Message Title Daniel Vergil commented on JENKINS-60096 Re: Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script robert arles I figured out that the issue was with the 'credentialId' in the 'sauceOnDemandBuildWrapper'. The scope of the credentialId I used was incorrect. It's working fine now after I fixed the 'credentialId'. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202941.1573156459000.5110.1578518460203%40Atlassian.JIRA.
[JIRA] (JENKINS-60096) Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script
Title: Message Title robert arles commented on JENKINS-60096 Re: Jenkins is throwing a NullPointerException at SauceOnDemandBuildWrapper when the jobs are created using a DSL script I'm seeing the same issue and the same workaround (open the config, save, then the job runs properly) I'm only just starting to troubleshoot this, I'm suspecting an issue originating in the groovy DSL, but it is isolated to specific jobs, not affected all jobs created by the script. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202941.1573156459000.5108.1578517500182%40Atlassian.JIRA.
[JIRA] (JENKINS-59836) HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects
Title: Message Title Lance Reed commented on JENKINS-59836 Re: HashiCorp Vault plugin configuration cannot be enabled for Freestyle projects Have this issue also. However it was working a few weeks ago. We update versions regularly. A few weeks ago I was able to use the Hashicorp Vault Plugin fine. Today if I attempt to simply save a preexisting job I get the stated error. I confirm that we are currently running Jenkins 2.207 with HashiCorp Vault Plugin 3.0.0 Happy to help assist with debugging and testing. Thanks. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202571.1571380365000.5079.1578515760383%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick updated JENKINS-55017 Jenkins / JENKINS-55017 Allow advanced configuration for other s3 providers Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.196055.1543946313000.5031.1578511740481%40Atlassian.JIRA.
[JIRA] (JENKINS-55017) Allow advanced configuration for other s3 providers
Title: Message Title Jesse Glick assigned an issue to Jesse Glick Jenkins / JENKINS-55017 Allow advanced configuration for other s3 providers Change By: Jesse Glick Assignee: Chris Tapley Jesse Glick Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.196055.1543946313000.5029.1578511740404%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe updated an issue Jenkins / JENKINS-45504 Add @Symbol annotations to traits Change By: René Scheibe Released As: git-plugin 4.0.0, bitbucket-branch-source-plugin TODO, github-branch-source-plugin TODO Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.183680.1499933648000.4995.1578510720999%40Atlassian.JIRA.
[JIRA] (JENKINS-45504) Add @Symbol annotations to traits
Title: Message Title René Scheibe commented on JENKINS-45504 Re: Add @Symbol annotations to traits The former status was correct (fixed but unreleased). I am still waiting for releases of the two plugins. I would then add the version numbers here for reference and close the ticket afterwards. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.183680.1499933648000.4962.1578510480948%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Jon Starbird commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Great. I'll keep an eye out for it. Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203842.1577724088000.4960.1578509280126%40Atlassian.JIRA.
[JIRA] (JENKINS-60701) reuseNode should default to true / docker agent stage: Waiting for next available executor
Title: Message Title
frankie fisher created an issue
Jenkins / JENKINS-60701
reuseNode should default to true / docker agent stage: Waiting for next available executor
Issue Type:
Bug
Assignee:
Carlos Sanchez
Attachments:
jenkins docker agent reproduction.txt
Components:
core, docker
Created:
2020-01-08 18:40
Environment:
Jenkins 2.190.3 docker pipeline 1.21 docker commons 1.16
Priority:
Minor
Reporter:
frankie fisher
If you have a multi-stage pipeline with an outer "agent any" specification, and then a particular stage runs inside a docker container, so you use an "agent {docker{}}" section, you will deadlock all your executors if you set off more jobs of this type, than you have executors. This happens because the outer agent attempts to find a new executor to run the docker agent, but as you have set off as many jobs of this type as you have executors, all executors are currently in use, so the outer agent never finds a new executor, thus never frees itself. Deadlock. I suspect this problem is not exclusive to docker agents. You can solve this problem by setting "reuseNode true" inside the docker agent specification. Solution Because of the simplicity of deadlocking all executors, I think reuseNode=true should be the default value for agents. I don't know enough about Jenkins to understand the possible downsides to doing this, so there may be good reasons to reject this Issue. But it would be a good idea for someone who understands the implications of reuseNode to look at this Issue and make the decision. Reproduction To reproduce this issue, create a
[JIRA] (JENKINS-60687) Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB
Title: Message Title Paul Ireland updated an issue Jenkins / JENKINS-60687 Extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB Change By: Paul Ireland Please extend the InfluxDB plugin to send metrics from Serenity reports to InfluxDB. Example metrics: * Counts of passing/pending/ignored/skipped/failed/broken/compromised tests * Execution time / clock time / fastest test / slowest test / average execution tim timeIf there is an existing way to send metrics from Serenity reports then please let me know! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203931.1578474488000.4956.1578508440251%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title _peedus edited a comment on JENKINS-54445 Re: Publishing data to influxDb Hi [~aleksisimell],> the current configuration the _*jenkinsEnvParameterTag*_ adds the tags only to the measurement "_*jenkins_data*_", as documented. I will try to add those tags to all measurements once I find time.Is there any tentative time when this will be available? Hope the same could be also done for _*jenkinsEnvParameterField*_ ? Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195207.1541406402000.4953.1578508260194%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title _peedus edited a comment on JENKINS-54445 Re: Publishing data to influxDb Hi [~aleksisimell],> the current configuration the _*jenkinsEnvParameterTag*_ adds the tags only to the measurement "_*jenkins_data*_", as documented. I will try to add those tags to all measurements once I find time.Is there any tentative time when this will be available? Hope the same could be also done for _*jenkinsEnvParameterField*_ ? Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195207.1541406402000.4949.1578508200203%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title _peedus edited a comment on JENKINS-54445 Re: Publishing data to influxDb Hi [~aleksisimell],> the current configuration the _* jenkinsEnvParameterTag *_ adds the tags only to the measurement " _* jenkins_data *_ ", as documented. I will try to add those tags to all measurements once I find time.Is there any tentative time when this will be available?Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195207.1541406402000.4945.1578507960193%40Atlassian.JIRA.
[JIRA] (JENKINS-54445) Publishing data to influxDb
Title: Message Title _peedus commented on JENKINS-54445 Re: Publishing data to influxDb Hi Aleksi Simell, > the current configuration the jenkinsEnvParameterTag adds the tags only to the measurement "jenkins_data", as documented. I will try to add those tags to all measurements once I find time. Is there any tentative time when this will be available? Thanks! Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.195207.1541406402000.4941.1578507900202%40Atlassian.JIRA.
[JIRA] (JENKINS-60700) Credentials Binding Plugin binds to partial string matches
Title: Message Title
Tim Merkt created an issue
Jenkins / JENKINS-60700
Credentials Binding Plugin binds to partial string matches
Issue Type:
Bug
Assignee:
Unassigned
Components:
credentials-binding-plugin
Created:
2020-01-08 18:08
Environment:
credentials-binding-plugin 1.20 Jenkins 2.190.1
Priority:
Minor
Reporter:
Tim Merkt
Same as JENKINS-43032, except the value I bound to a username in withCredentials is being bound to a string not related to the binding. ex. CHART_NAME=ingestion-tracking value of DATASOURCE_USERNAME = ingestion withCredentials([usernamePassword(credentialsId: "${DATASOURCE_CREDS}", passwordVariable: 'DATASOURCE_PASSWORD', usernameVariable: 'DATASOURCE_USERNAME') ]) { sh "echo ${DATASOURCE_USERNAME}" sh "echo ${CHART_NAME}" } will yield: -tracking I expect: ingestion-tracking
Add Comment
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Jesse Glick updated JENKINS-50772 Jenkins / JENKINS-50772 Content type not set reasonably Change By: Jesse Glick Status: In Review Fixed but Unreleased Resolution: Fixed Released As: 4 1 . 5.10-2.0 8 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.189876.1523552257000.4937.1578506642703%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title Frederic Leroux commented on JENKINS-60352 Re: Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Hi, This patch cause a NullPointerException (with AWX) because towerVersion attribute is apparently not properly filled. Cheers java.lang.NullPointerException at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.processCredentials(TowerConnector.java:518) at org.jenkinsci.plugins.ansible_tower.util.TowerConnector.submitTemplate(TowerConnector.java:564) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerRunner.runJobTemplate(AnsibleTowerRunner.java:184) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:266) at org.jenkinsci.plugins.ansible_tower.AnsibleTowerStep$AnsibleTowerStepExecution.run(AnsibleTowerStep.java:202) Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203369.1575384648000.4926.1578505500231%40Atlassian.JIRA.
[JIRA] (JENKINS-60623) Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes
Title: Message Title
Steve Berube commented on JENKINS-60623
Re: Failed to count the # of live instances on Kubernetes after upgrade to 1.22.3 for slaves with multiple labes
Can confirm the same issue 2020-01-08 16:54:02.768+ [id=59] WARNING o.c.j.p.k.KubernetesCloud#provision: Failed to count the # of live instances on Kubernetes2020-01-08 16:54:02.768+ [id=59] WARNING o.c.j.p.k.KubernetesCloud#provision: Failed to count the # of live instances on Kubernetesio.fabric8.kubernetes.client.KubernetesClientException: Failure executing: GET at: https://hcm-cicd.hpeswlab.net:8443/api/v1/namespaces/cicd/pods?labelSelector=jenkins%3Dslave%2Cjenkins%2Flabel%3Ddeployment%20maven%20nodejs%20python%20aujas%20seleniumgrid. Message: found 'maven', expected: ',' or 'end of string'. Received status: Status(apiVersion=v1, code=400, details=null, kind=Status, message=found 'maven', expected: ',' or 'end of string', metadata=ListMeta(_continue=null, remainingItemCount=null, resourceVersion=null, selfLink=null, additionalProperties={}), reason=BadRequest, status=Failure, additionalProperties={}).
Add Comment
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
--
You received this message because you are subscribed to the Google 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.203855.1577961309000.4923.1578502740219%40Atlassian.JIRA.
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Davis Ford updated an issue Jenkins / JENKINS-60699 Cannot add bitbucket server Change By: Davis Ford Environment: Jenskins Jenkins Version 2.213OS: Mac OS 10.14java version "1.8.0_202"Java(TM) SE Runtime Environment (build 1.8.0_202-b08)Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode)Plugins:jsch JSch dependency plugin 0.1.55.1ws-cleanup Workspace Cleanup Plugin 0.38blueocean-commons Common API for Blue Ocean 1.21.0mercurial Mercurial plugin 2.8structs Structs Plugin 1.20kubernetes-pipeline-devops-steps Kubernetes :: Pipeline :: DevOps Steps 1.6custom-view-tabs Custom View Tabs Plugin 1.3jira JIRA plugin 3.0.11sse-gateway Server Sent Events (SSE) Gateway Plugin 1.20groovy Groovy 2.2apache-httpcomponents-client-4-api Apache HttpComponents Client 4.x API Plugin 4.5.10-2.0sloccount SLOCCount Plug-in 1.24cobertura Cobertura Plugin 1.15pipeline-model-extensions Pipeline: Declarative Extension Points API 1.5.0external-monitor-job External Monitor Job Type Plugin 1.7kubernetes Kubernetes plugin 1.22.4workflow-aggregatorPipeline 2.6mailer Mailer Plugin 1.29git Git plugin 4.0.0handy-uri-templates-2-api Handy Uri Templates 2.x API Plugin 2.1.8-1.0blueocean-jira JIRA Integration for Blue Ocean 1.21.0promoted-builds-simple Promoted Builds (Simple) 1.9kubernetes-pipeline-steps Kubernetes :: Pipeline :: Kubernetes Steps 1.6command-launcher Command Agent Launcher Plugin 1.4workflow-api Pipeline: API 2.38workflow-job Pipeline: Job 2.36ssh-credentials SSH Credentials Plugin 1.18authentication-tokens Authentication Tokens API Plugin 1.3docker-compose-build-step Docker Compose Build Step Plugin 1.0blueocean-rest-implREST Implementation for Blue Ocean 1.21.0github-branch-source GitHub Branch Source Plugin 2.5.8htmlpublisher HTML Publisher plugin 1.21javadoc Javadoc Plugin 1.5cocoapods-integration CocoaPods Jenkins Integration 0.2.0workflow-cps-global-libPipeline: Shared Groovy Libraries
[JIRA] (JENKINS-60699) Cannot add bitbucket server
Title: Message Title Davis Ford created an issue Jenkins / JENKINS-60699 Cannot add bitbucket server Issue Type: Bug Assignee: Kristy Hughes Attachments: Screen Shot 2020-01-08 at 11.37.42 AM.png, Screen Shot 2020-01-08 at 11.39.30 AM.png Components: atlassian-bitbucket-server-integration-plugin Created: 2020-01-08 16:42 Environment: Jenskins Version 2.213 OS: Mac OS 10.14 java version "1.8.0_202" Java(TM) SE Runtime Environment (build 1.8.0_202-b08) Java HotSpot(TM) 64-Bit Server VM (build 25.202-b08, mixed mode) Plugins: jsch JSch dependency plugin 0.1.55.1 ws-cleanup Workspace Cleanup Plugin 0.38 blueocean-commons Common API for Blue Ocean 1.21.0 mercurial Mercurial plugin 2.8 structs Structs Plugin 1.20 kubernetes-pipeline-devops-steps Kubernetes :: Pipeline :: DevOps Steps 1.6 custom-view-tabs Custom View Tabs Plugin 1.3 jira JIRA plugin 3.0.11 sse-gateway Server Sent Events (SSE) Gateway Plugin 1.20 groovy Groovy 2.2 apache-httpcomponents-client-4-api Apache HttpComponents Client 4.x API Plugin 4.5.10-2.0 sloccount SLOCCount Plug-in 1.24 cobertura Cobertura Plugin 1.15 pipeline-model-extensions Pipeline: Declarative Extension Points API 1.5.0 external-monitor-job External Monitor Job Type Plugin 1.7 kubernetes Kubernetes plugin 1.22.4 workflow-aggregator Pipeline 2.6 mailer Mailer Plugin 1.29 git Git plugin 4.0.0 handy-uri-templates-2-api Handy Uri Templates 2.x API Plugin 2.1.8-1.0 blueocean-jira JIRA Integration for Blue Ocean 1.21.0 promoted-builds-simple Promoted Builds (Simple) 1.9 kubernetes-pipeline-steps Kubernetes :: Pipeline :: Kubernetes Steps 1.6 command-launcher Command Agent Launcher Plugin 1.4 workflow-api Pipeline: API 2.38 workflow-job Pipeline: Job 2.36 ssh-credentials SSH Credentials Plugin 1.18 authentication-tokens Authentication Tokens API Plugin 1.3 docker-compose-build-step Docker Compose Build Step Plugin 1.0 blueocean-rest-impl REST Implementation for Blue Ocean 1.21.0 github-branch-source GitHub Branch Source Plugin 2.5.8 htmlpublisher HTML Publisher plugin 1.21 javadoc Javadoc Plugin 1.5 cocoapods-integration CocoaPods Jenkins Integration 0.2.0 workflow-cps-global-lib Pipeline: Shared Groovy Libraries 2.15 blueocean-web Web for Blue Ocean 1.21.0 sidebar-update-notification Sidebar Update Notification Plugin 1.1.0 jackson2-api Jackson 2 API Plugin 2.10.2 ssh-slaves SSH Slaves plugin 1.31.0 slack-uploader Slack Upload
[JIRA] (JENKINS-58637) .jenkinsignore
Title: Message Title Kyle Leinen commented on JENKINS-58637 Re: .jenkinsignore Igal Gluh this feature got be really excited as it would solve the same problem for my team that Jesse Glick has. I've found that while the "Cancel build excluded regions strategy" works without issue, I am unable to get the new "Cancel ci by ignore file strategy" working using a .jenkinsignore file that has the same contents. I think these are valid ANT pattern files, so I'm not sure what I am doing wrong. Here is the contents if my .jenkinsignore: *.md LICENSE .gitignore .jenkinsignore review.conf I have also tried the following with no success: *.md /LICENSE /.gitignore /.jenkinsignore /review.conf Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Charusheela Bopardikar updated JENKINS-59484 Released in 1.10.9 Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Charusheela Bopardikar Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202099.1569244102000.4903.1578499200796%40Atlassian.JIRA.
[JIRA] (JENKINS-59484) EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory
Title: Message Title Charusheela Bopardikar updated JENKINS-59484 Jenkins / JENKINS-59484 EXECUTOR_NUMBER is always expanded to '0' in workspace name when checking out with Perforce to a subdirectory Change By: Charusheela Bopardikar Status: Closed Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202099.1569244102000.4900.1578499200732%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Charusheela Bopardikar updated JENKINS-60321 Released in 1.10.9 Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Change By: Charusheela Bopardikar Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203319.157495971.4889.1578499141108%40Atlassian.JIRA.
[JIRA] (JENKINS-60144) Cant delete Jenkins job if the perforce template client has been deleted
Title: Message Title Charusheela Bopardikar updated JENKINS-60144 Released in 1.10.9 Jenkins / JENKINS-60144 Cant delete Jenkins job if the perforce template client has been deleted Change By: Charusheela Bopardikar Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203005.1573570536000.4894.1578499141201%40Atlassian.JIRA.
[JIRA] (JENKINS-60321) Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams
Title: Message Title Charusheela Bopardikar updated JENKINS-60321 Jenkins / JENKINS-60321 Multibranch pipeline with default Jenkinsfile fails when scanning p4 streams Change By: Charusheela Bopardikar Status: Resolved Fixed but Unreleased Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203319.157495971.4883.1578499080569%40Atlassian.JIRA.
[JIRA] (JENKINS-56290) Impossible to Add Streams with Exact Names to Multibranch Pipeline
Title: Message Title Charusheela Bopardikar updated JENKINS-56290 Released in 1.10.9 Jenkins / JENKINS-56290 Impossible to Add Streams with Exact Names to Multibranch Pipeline Change By: Charusheela Bopardikar Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197869.155119216.4874.1578499021775%40Atlassian.JIRA.
[JIRA] (JENKINS-60141) Excessive number of "login -s" requests
Title: Message Title Charusheela Bopardikar updated JENKINS-60141 Released in 1.10.9 Jenkins / JENKINS-60141 Excessive number of "login -s" requests Change By: Charusheela Bopardikar Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203002.157355793.4878.1578499021840%40Atlassian.JIRA.
[JIRA] (JENKINS-60670) StackOverflowError due to the HP ALM implementation of GraphListener
Title: Message Title Paul-Adrian Tofan assigned an issue to Roy Lu Jenkins / JENKINS-60670 StackOverflowError due to the HP ALM implementation of GraphListener Change By: Paul-Adrian Tofan Assignee: Maria Narcisa Galan Roy Lu Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203913.1578384494000.4871.1578498960343%40Atlassian.JIRA.
[JIRA] (JENKINS-60698) sshCommand with sudo: true waits forever
Title: Message Title
Nick Hardy created an issue
Jenkins / JENKINS-60698
sshCommand with sudo: true waits forever
Issue Type:
Bug
Assignee:
Naresh Rayapati
Components:
ssh-steps-plugin
Created:
2020-01-08 15:51
Environment:
Jenkins 2.204.1 Ubuntu 16.04.5 LTS
Priority:
Minor
Reporter:
Nick Hardy
I have an issue using an sshCommand with sudo set to true from within a pipeline.
withCredentials([sshUserPrivateKey(credentialsId: credentials_id, keyFileVariable: 'JenkinsIdentity')]) {
script {
def remote = [name: server_name, host: host_name, knownHosts: remote_knownHosts, user: remote_user, timeoutSec: 1200, identityFile: JenkinsIdentity]
// install application
sshCommand remote: remote, command: '/home/user/install.sh', sudo: true
}
}
The command executes on the remote server, but it's waiting forever. Probably waiting for user input. On the remote server i see this in processes: root 62610 62609 0 16:35 ? 00:00:00 sudo -S -p 4b0b21d6-23ab-4e47-b21e-8362bdf2c4d0 sh /home/user/install.sh It will only stop when i abort the jenkins job. Any ideas on what i can try?
[JIRA] (JENKINS-60698) sshCommand with sudo: true waits forever
Title: Message Title Nick Hardy updated an issue Jenkins / JENKINS-60698 sshCommand with sudo: true waits forever Change By: Nick Hardy Priority: Minor Major Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203943.1578498666000.4867.1578498720348%40Atlassian.JIRA.
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref".h4. ExamplePipeline job created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{g...@git.serv.d.net:ts-source.git}} * Refspec: {{+refs/heads/\*:refs/remotes/origin/\* +refs/changes/\*:refs/remotes/origin/\*}} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code:groovy}println readTrusted(".jenkins/test.groovy"){code}h4. Build log{code:none}Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test.groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] readTrusted[Pipeline] End of Pipelinehudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128:fatal: Couldn't find remote ref refs/heads/4eedb3bfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref".h4. ExamplePipeline job created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{g...@git.serv.d.net:ts-source.git}} * Refspec: {{+refs/heads/ \ *:refs/remotes/origin/ \ * +refs/changes/ \ *:refs/remotes/origin/ \ *}} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code:groovy}println readTrusted(".jenkins/test.groovy") {code}h4. Build log{code: text none }Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test.groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout=10Running in Durability level: MAX_SURVIVABILITY[Pipeline] Start of Pipeline[Pipeline] readTrusted[Pipeline] End of Pipelinehudson.plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128:fatal: Couldn't find remote ref refs/heads/4eedb3bfatal: The remote end hung up unexpectedly at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at
[JIRA] (JENKINS-58207) 2.181 JNA update breaks NegotiateSSO
Title: Message Title ethorsa commented on JENKINS-58207 Re: 2.181 JNA update breaks NegotiateSSO It should be visible already. Do you have up to date Metadata? In doubt, you can download it manually: https://updates.jenkins.io/download/plugins/NegotiateSSO/ Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200266.1561541748000.4851.1578497700734%40Atlassian.JIRA.
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr updated an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Change By:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref". h4. ExamplePipeline job wftest created and configured as Pipeline script from SCM with the following parameters: * SCM: Git * Repository URL: {{ g...@git.serv.d.net:ts-source.git }} * Refspec: {{ +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* }} * Branch Specifier: 4eedb3b * Script Path: .jenkins/test.groovy.jenkins/test.groovy{code: java groovy }println readTrusted(".jenkins/test.groovy"){code} h4. Build log{ {}}{ code: java text }Checking out git g...@git.serv.d.net:ts-source.git into /var/lib/jenkins/jobs/wftest/workspace@script to read .jenkins/test. groovyNo groovyNo credentials specified > git rev-parse --is-inside-work-tree # timeout=10Fetching changes from the remote Git repository > git config remote.origin.url g...@git.serv.d.net:ts-source.git # timeout=10Fetching upstream changes from g...@git.serv.d.net:ts-source.git > git --version # timeout=10 > git fetch --tags --progress g...@git.serv.d.net:ts-source.git +refs/heads/*:refs/remotes/origin/* +refs/changes/*:refs/remotes/origin/* > git rev-parse 4eedb3b^{commit} # timeout=10Checking out Revision 4eedb3baaa6d528d22180784e0001d99d618bda9 (detached) > git config core.sparsecheckout # timeout=10 > git checkout -f 4eedb3baaa6d528d22180784e0001d99d618bda9Commit message: ".jenkins: make the jobseed job running in sandbox" > git rev-list --no-walk 3c75ef69338675fe751d97af3173c206aef58d94 # timeout= 10Running 10Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] readTrusted [Pipeline] End of Pipelinehudson Pipelinehudson .plugins.git.GitException: Command "git fetch --tags --progress origin +refs/heads/4eedb3b:refs/remotes/origin/4eedb3b --prune" returned status code 128: fatal: Couldn't find remote ref refs/heads/ 4eedb3bfatal 4eedb3bfatal : The remote end hung up unexpectedlyat org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2042) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1761) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$400(CliGitAPIImpl.java:72) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:442) at jenkins.plugins.git.GitSCMFileSystem$BuilderImpl.build(GitSCMFileSystem.java:351) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:198) at jenkins.scm.api.SCMFileSystem.of(SCMFileSystem.java:174) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:101) at org.jenkinsci.plugins.workflow.multibranch.ReadTrustedStep$Execution.run(ReadTrustedStep.java:82) at
[JIRA] (JENKINS-60697) readTrusted does not honor the refspec on Pipeline script from SCM GIT
Title: Message Title
Welt Fahr created an issue
Jenkins / JENKINS-60697
readTrusted does not honor the refspec on Pipeline script from SCM GIT
Issue Type:
Bug
Assignee:
Unassigned
Components:
git-plugin
Created:
2020-01-08 15:23
Environment:
OS: Alpine Linux 3.8.4 x64 Open JDK 8 Jenkins 2.176.1
Labels:
pipeline git
Priority:
Major
Reporter:
Welt Fahr
In a pipeline script from SCM, using a git repository with Refspec, readTrusted is not using the refsspec are fails with error "Couldn't find remote ref". Example Pipeline job wftest created and configured as Pipeline script from SCM with the following parameters:
SCM: Git
Repository URL: g...@git.serv.d.net:ts-source.git
Refspec: +refs/heads/:refs/remotes/origin/ +refs/changes/:refs/remotes/origin/
Branch Specifier: 4eedb3b
Script Path: .jenkins/test.groovy
.jenkins/test.groovy
println readTrusted(".jenkins/test.groovy")
[JIRA] (JENKINS-59973) rtUpload / rtDownload fail with HTTP 401 / 403
Title: Message Title ethorsa commented on JENKINS-59973 Re: rtUpload / rtDownload fail with HTTP 401 / 403 I have test the latest v3.5.0 – which should include the snapshot changes – using the three credential types: Username / API key API key (= secret text) Username / encryped password All remain failing with HTTP/1.1 403 and produce the same log messages: access.log 2020-01-08 08:22:39,027 [ACCEPTED LOGIN] for client : anonymous / . request.log 20200108082239|8|REQUEST||anonymous|POST|/api/search/aql|HTTP/1.1|403|203 The test with username / password showed a |11| instead of the |8|, but i don't know what this number stands for. The overall setup is the same as used for the previous tests. For completeness, here are the used versions: Artifactory 6.12.3 Jenkins 2.190.3 Artifactory Jenkins Plugin 3.5.0 The curl call mentioned earlier still works when executed from the agent. Are there any reasonable places to add some logging? I can build the plugin from source, so maybe that's a way to gain more insight. Add Comment
[JIRA] (JENKINS-49500) In every pipeline build with triggers, a new trigger is created and the old one is stopped
Title: Message Title Scott Hebert updated JENKINS-49500 Fixed in 1.5.0 Jenkins / JENKINS-49500 In every pipeline build with triggers, a new trigger is created and the old one is stopped Change By: Scott Hebert Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203369.1575384648000.4828.1578495600588%40Atlassian.JIRA.
[JIRA] (JENKINS-48377) Job Tags don't pass to Ansible Tower/AWX
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48377 Job Tags don't pass to Ansible Tower/AWX Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.186972.151243328.4823.1578495540249%40Atlassian.JIRA.
[JIRA] (JENKINS-48377) Job Tags don't pass to Ansible Tower/AWX
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48377 Job Tags don't pass to Ansible Tower/AWX Change By: John Westcott Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.186972.151243328.4820.1578495481083%40Atlassian.JIRA.
[JIRA] (JENKINS-48438) Workflow Templates with project sync or inventory update have incorrect links
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48438 Workflow Templates with project sync or inventory update have incorrect links Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187037.1512671212000.4817.1578495481040%40Atlassian.JIRA.
[JIRA] (JENKINS-48663) Job Template execution getting 400 request
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48663 Job Template execution getting 400 request Change By: John Westcott Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187340.1513821798000.4812.1578495480827%40Atlassian.JIRA.
[JIRA] (JENKINS-48663) Job Template execution getting 400 request
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48663 Job Template execution getting 400 request Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187340.1513821798000.4814.1578495480968%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott resolved as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187621.1515346312000.4807.1578495420783%40Atlassian.JIRA.
[JIRA] (JENKINS-49915) ansible-tower-plugin not passing extra variables
Title: Message Title John Westcott closed an issue as Not A Defect Jenkins / JENKINS-49915 ansible-tower-plugin not passing extra variables Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.188905.1520245664000.4804.1578495420728%40Atlassian.JIRA.
[JIRA] (JENKINS-48835) Testing a connection results in "The item does not exist"
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-48835 Testing a connection results in "The item does not exist" Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.187621.1515346312000.4810.1578495420827%40Atlassian.JIRA.
[JIRA] (JENKINS-54341) Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-54341 Ansible Tower Plugin 0.9.0 not compatible with Tower 3.2.5 Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.194994.1540896444000.4802.1578495361710%40Atlassian.JIRA.
[JIRA] (JENKINS-58725) Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending.
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-58725 Ansible-Tower Plugin: Ansible Tower will hang when Jenkins job is cancelled on the web portal. And now the latter jobs will all be pending. Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.201018.1564479331000.4795.1578495240435%40Atlassian.JIRA.
[JIRA] (JENKINS-56250) Ansible Tower Plugin not injecting Environment Variables for later use
Title: Message Title John Westcott updated JENKINS-56250 Jenkins / JENKINS-56250 Ansible Tower Plugin not injecting Environment Variables for later use Change By: John Westcott Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197817.1550853641000.4799.1578495240528%40Atlassian.JIRA.
[JIRA] (JENKINS-56300) New step or option that does not block on individual job completion
Title: Message Title John Westcott closed an issue as Fixed Jenkins / JENKINS-56300 New step or option that does not block on individual job completion Change By: John Westcott Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197880.1551226267000.4797.1578495240468%40Atlassian.JIRA.
[JIRA] (JENKINS-60352) Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1
Title: Message Title John Westcott resolved as Fixed Please reopen the ticket if the latest release does not resolve this issue. Jenkins / JENKINS-60352 Ansible Tower Plugin does not pass credentials from job to Ansible tower 3.6.1 Change By: John Westcott Status: Open Resolved Resolution: Fixed Released As: 0.14.0 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) --
[JIRA] (JENKINS-60696) With the webhooks, the active choice reactive does not work
Title: Message Title
Jerome Huet created an issue
Jenkins / JENKINS-60696
With the webhooks, the active choice reactive does not work
Issue Type:
Bug
Assignee:
Bruno P. Kinoshita
Attachments:
Cities.png, reactive parameter failed.png, States.png
Components:
active-choices-plugin
Created:
2020-01-08 14:32
Environment:
Jenkins 2.206, Active-choices 2.2.1
Priority:
Major
Reporter:
Jerome Huet
I used the example 2 on the wiki site (" Active Choices Reactive Parameter: Configuration Options (Example 02)"). It works well When I used with trigger webhooks from a change is pushed to GitLab, the reactive parameter is failed like you can see on 'reactive parameter failed.png' image
Add Comment
[JIRA] (JENKINS-59449) ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link
Title: Message Title Ramon Leon resolved as Cannot Reproduce Resolved as Cannot Reproduce because it was already fixed by removing the test. Jenkins / JENKINS-59449 ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link Change By: Ramon Leon Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you 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-60088) Change pod label - build label from unique key to value.
Title: Message Title Vincent Latombe updated JENKINS-60088 Jenkins / JENKINS-60088 Change pod label - build label from unique key to value. Change By: Vincent Latombe Status: In Review Resolved Resolution: Fixed Released As: 1.22.1 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202932.1573141389000.4787.1578493921150%40Atlassian.JIRA.
[JIRA] (JENKINS-59449) ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link
Title: Message Title Ramon Leon commented on JENKINS-59449 Re: ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link The failing test was removed by Oliver Gondza on September 19th: acceptance-test-harness: 19a80edf JENKINS-59362: Gradle: removing ignored tests for issues noone had a look at for 2 years so the test is no longer in ATH. It is on acceptance-test-harness-1.69 and acceptance-test-harness-1.68 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202034.1568905564000.4773.1578493800294%40Atlassian.JIRA.
[JIRA] (JENKINS-59449) ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link
Title: Message Title Ramon Leon assigned an issue to Ramon Leon Jenkins / JENKINS-59449 ATH Test error plugins.GradlePluginTest.run_gradle_script_build_scan_link Change By: Ramon Leon Assignee: Stefan Wolf Ramon Leon Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.202034.1568905564000.4771.1578493740286%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title Jesse Glick assigned an issue to Unassigned Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Change By: Jesse Glick Assignee: Oliver Gondža Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203939.1578490571000.4764.1578492120430%40Atlassian.JIRA.
[JIRA] (JENKINS-60613) Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0
Title: Message Title Andrew Sumner commented on JENKINS-60613 Re: Cannot use Jenkins variable to override Release Number after plugin upgrade to 3.0 Good news, I've finally got this working. The solution ended up being rather simple - around 20 lines of code. Shame the Jenkins documentation is garbage, it should have been much easier to get this up and running. I've got a bit more testing to do but should have a new release out in the next few days. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203842.1577724088000.4761.1578491400131%40Atlassian.JIRA.
[JIRA] (JENKINS-60695) "Filter by AWS secret namespace ID" not working
Title: Message Title
Dominik Bartholdi created an issue
Jenkins / JENKINS-60695
"Filter by AWS secret namespace ID" not working
Issue Type:
Bug
Assignee:
Chris Kilding
Components:
aws-secrets-manager-credentials-provider-plugin
Created:
2020-01-08 13:40
Priority:
Major
Reporter:
Dominik Bartholdi
I created credentials like this:
aws secretsmanager create-secret --name 'jks/DB_USER_X' --secret-string 'zz' --tags 'Key=jenkins:credentials:username,Value=u' --description ''
Then I used the documented policy template: https://github.com/jenkinsci/aws-secrets-manager-credentials-provider-plugin/blob/master/docs/iam/secret-namespace-id.json to filter credentials by a namespace. My complete policy looked like this:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": "secretsmanager:GetSecretValue",
"Resource": "arn:aws:secretsmanager:::secret:jks/*",
"Effect": "Allow"
},
{
"Action": "secretsmanager:ListSecrets",
"Resource": "*",
"Effect": "Allow"
}
]
}
unfortunate this ends up in this error:
com.cloudbees.plugins.credentials.CredentialsUnavailableException:
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title Daniel Estermann commented on JENKINS-60264 Re: Running a multibranch pipeline job results in missing workspace error Thank you for pointing that out! Now I see something else, which is also suspicious. Maven doesn't print a report on test result as usual. Usually it outputs the number of tests run, how many are failed or skipped, no matter if test fails or succeeds. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203252.1574679668000.4752.1578490800705%40Atlassian.JIRA.
[JIRA] (JENKINS-60694) JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule
Title: Message Title A. Jard created an issue Jenkins / JENKINS-60694 JellyTestSuite fails with timeout issue on Windows runner because it uses HudsonTestCase instead of JenkinsRule Issue Type: Bug Assignee: Oliver Gondža Components: jenkins-test-harness Created: 2020-01-08 13:36 Environment: Windows agent on kubernetes jenkins-test-harness-2.57 and above with jetty version greater than 9.4.6.v20170531 Priority: Minor Reporter: A. Jard The test class TestInjection generated by maven-hpi-plugin fails to run the test suite with a timeout exception when updating jenkins-test-harness from 2.56 to 2.57 on Windows agent. The same mvn install command run on a Linux agent run fine. After investigation, the reason is that JellyTestSuite is based on HudsonTestCase, and HudsonTestCase does not work on the Windows agent with a jetty above 9.4.6.v20170531. Between jenkins-test-harness-2:56 and jenkins-test-harness:2.57 jetty version has changed from 9.4.5.v20170502 to 9.4.22.v20191022. Setting jetty version to 9.4.6.v20170531 in maven dependencies with jenkins-test-harness:2.57 (and above) solve the issue. JellyTestSuiteBuilder should be updated to use JenkinsRule and not the deprecated HudsonTestCase. https://github.com/jenkinsci/jenkins-test-harness/blob/0e0ec3c9ccbe6314d488faa248e2f50f312f3cad/src/main/java/org/jvnet/hudson/test/JellyTestSuiteBuilder.java#L138 Link to maven-hpi-plugin code that generate the TestInjection class: https://github.com/jenkinsci/maven-hpi-plugin/blob/master/src/main/java/org/jenkinsci/maven/plugins/hpi/TestInsertionMojo.java
[JIRA] (JENKINS-60693) Allow editing credential id
Title: Message Title Jesse Rittner created an issue Jenkins / JENKINS-60693 Allow editing credential id Issue Type: Story Assignee: Unassigned Components: credentials-plugin Created: 2020-01-08 13:28 Priority: Minor Reporter: Jesse Rittner Currently there appears to be no way to change the id of a credential once it has been created. The user instead is required to manually create a new secret with the same contents. This is very annoying, especially because it requires tracking down the actual credentials themselves again. Instead, the credential id should be a mutable property of a credential. It would also be acceptable if there were simply an option to clone a credential with a new id. Add Comment
[JIRA] (JENKINS-60692) credential type icon not correctly reflected
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-60692 credential type icon not correctly reflected Issue Type: Bug Assignee: Chris Kilding Attachments: Screenshot 2020-01-08 at 10.00.12.png Components: aws-secrets-manager-credentials-provider-plugin Created: 2020-01-08 13:25 Priority: Minor Reporter: Dominik Bartholdi I created a username/password credentials with the following command: aws secretsmanager create-secret --name 'DB_USER_X' --secret-string 'zz' --tags 'Key=jenkins:credentials:username,Value=u' --description '' although this worked and the credentials also show up in jenkins, the credentials have the wrong type icon shown in the credentials list screen: all four credentials shown in the above screenshot should have the same icon in the first position of each line - all should be of type "UserName with Password". Currently the ones from AWS Provider show a different icon with the tool tip "AWS Secrets Manager secret" (which in fact is the icon for "Secret text"). This is very irritating for a user.
[JIRA] (JENKINS-43022) Not correct exclude path to domains
Title: Message Title Mark Waite closed an issue as Fixed Jenkins / JENKINS-43022 Not correct exclude path to domains Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.180124.149017306.4744.1578489300824%40Atlassian.JIRA.
[JIRA] (JENKINS-60264) Running a multibranch pipeline job results in missing workspace error
Title: Message Title Gavin Mogan commented on JENKINS-60264 Re: Running a multibranch pipeline job results in missing workspace error Repeating from on gitter: your bug essentially reads "I am building my own docker image using secret steps. The secret tests fail, and my pipeline fails". Which seems right, when tests fail, mvn exit code > 0, and pipeline exits Based on your super truncated error message / log, I'm pretty sure its failing on the mvn test. I don't know what jenkins, or your pom file does for mvn test, but it doesn't feel like a pipeline issue to me. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203252.1574679668000.4735.1578487865189%40Atlassian.JIRA.
[JIRA] (JENKINS-58512) No page found '/io/jenkins/plugins/multibranch/BranchPriorityStrategy/config.jelly' for class jenkins.advancedqueue.PriorityConfiguration
Title: Message Title Kalle Niemitalo commented on JENKINS-58512 Re: No page found '/io/jenkins/plugins/multibranch/BranchPriorityStrategy/config.jelly' for class jenkins.advancedqueue.PriorityConfiguration The same happens with Jenkins 2.204.1 (LTS). Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.200656.1563275679000.4732.1578487680410%40Atlassian.JIRA.
[JIRA] (JENKINS-53492) Set priorities for Multibranch Pipelines
Title: Message Title Kalle Niemitalo commented on JENKINS-53492 Re: Set priorities for Multibranch Pipelines There is now Multi-Branch priority sorter, which extends Priority Sorter but currently suffers from JENKINS-58512. Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.193962.1536573062000.4728.1578487620180%40Atlassian.JIRA.
[JIRA] (JENKINS-60690) Build start failed with JsonParseException: Unexpected character
Title: Message Title Daniel Schulze updated an issue Jenkins / JENKINS-60690 Build start failed with JsonParseException: Unexpected character Change By: Daniel Schulze Priority: Major Minor Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203935.1578483391000.4724.1578486900106%40Atlassian.JIRA.
[JIRA] (JENKINS-51980) Missing Build Trigger Section after Upgrade of Jenkins
Title: Message Title Christian Schmitt commented on JENKINS-51980 Re: Missing Build Trigger Section after Upgrade of Jenkins Facing the same issue. And unfortunately moving to the multibranch pipeline plugin is not an option for us since the lack of some features (e.g. incremental maven module builds)... Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.191476.1529169756000.4723.1578486481090%40Atlassian.JIRA.
[JIRA] (JENKINS-60691) javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.34.jar!/lib/form/block.jelly:32:22:
Title: Message Title Jagjeet Chadha updated an issue Jenkins / JENKINS-60691 javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/cache/jenkins/war/WEB-INF/lib/jenkins-core-2.34.jar!/lib/form/block.jelly:32:22: hudson/matrix/MatrixProject Change By: Jagjeet Chadha Issue Type: Task Bug Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.203936.1578484795000.4720.1578485760194%40Atlassian.JIRA.
[JIRA] (JENKINS-60536) Jenkins job hangs in Jira call after git rev-list command
Title: Message Title
David France edited a comment on JENKINS-60536
Re: Jenkins job hangs in Jira call after git rev-list command
We've being seeing much the same problem stack that Kieran reported, trying to progress issues by a workflow action in Jira. We first became aware of the problem on 20/12/2019.The locking thread:{noformat}"Handling GET /view/Pipelines/job/.../457/ from a.b.c.d : qtp64133603-15 AbstractBuild/index.jelly SubversionChangeLogSet/digest.jelly" #15 prio=5 os_prio=0 cpu=8985.66ms elapsed=5244.95s tid=0x64d07000 nid=0x1fdc waiting for monitor entry [0x665b7000] java.lang.Thread.State: BLOCKED (on object monitor)at org.apache.http.nio.reactor.ssl.SSLIOSession.close(SSLIOSession.java:605)- waiting to lock <0x8613f660> (a org.apache.http.nio.reactor.ssl.SSLIOSession)at org.apache.http.impl.nio.NHttpConnectionBase.close(NHttpConnectionBase.java:511)at org.apache.http.impl.nio.conn.CPoolEntry.closeConnection(CPoolEntry.java:75)at org.apache.http.impl.nio.conn.CPoolEntry.close(CPoolEntry.java:101)at org.apache.http.nio.pool.AbstractNIOConnPool.processPendingRequest(AbstractNIOConnPool.java:423)at org.apache.http.nio.pool.AbstractNIOConnPool.lease(AbstractNIOConnPool.java:280)at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.requestConnection(PoolingNHttpClientConnectionManager.java:295)at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.requestConnection(AbstractClientExchangeHandler.java:377)at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.start(DefaultClientExchangeHandlerImpl.java:129)at org.apache.http.impl.nio.client.InternalHttpAsyncClient.execute(InternalHttpAsyncClient.java:141)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:75)at org.apache.http.impl.nio.client.CloseableHttpAsyncClient.execute(CloseableHttpAsyncClient.java:108)at com.atlassian.httpclient.apache.httpcomponents.SettableFuturePromiseHttpPromiseAsyncClient.execute(SettableFuturePromiseHttpPromiseAsyncClient.java:36)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.doExecute(ApacheAsyncHttpClient.java:417)at com.atlassian.httpclient.apache.httpcomponents.ApacheAsyncHttpClient.execute(ApacheAsyncHttpClient.java:364)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.execute(DefaultRequest.java:297)at com.atlassian.jira.rest.client.internal.async.AtlassianHttpClientDecorator$AuthenticatedRequestBuilder.execute(AtlassianHttpClientDecorator.java:83)at com.atlassian.httpclient.apache.httpcomponents.DefaultRequest$DefaultRequestBuilder.get(DefaultRequest.java:253)at com.atlassian.jira.rest.client.internal.async.AbstractAsynchronousRestClient.getAndParse(AbstractAsynchronousRestClient.java:69)at com.atlassian.jira.rest.client.internal.async.AsynchronousIssueRestClient.getIssue(AsynchronousIssueRestClient.java:186)at com.atlassian.jira.rest.client.internal.async.AsynchronousIssueRestClient.getIssue(AsynchronousIssueRestClient.java:177)at hudson.plugins.jira.JiraRestService.getIssue(JiraRestService.java:154)at hudson.plugins.jira.JiraSession.getIssue(JiraSession.java:126)at hudson.plugins.jira.JiraSite.lambda$getIssue$0(JiraSite.java:878)at hudson.plugins.jira.JiraSite$$Lambda$303/0x2262d840.call(Unknown Source)at com.google.common.cache.LocalCache$LocalManualCache$1.load(LocalCache.java:4767)at
[JIRA] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
Title: Message Title Mark Waite updated JENKINS-10385 Jenkins / JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.140577.138173000.4703.1578485100877%40Atlassian.JIRA.
[JIRA] (JENKINS-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Mark Waite updated JENKINS-39768 Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.176357.1479284097000.4692.1578484921349%40Atlassian.JIRA.
[JIRA] (JENKINS-24125) Git Polling fails for job restricted to Mac OS X slave (with Windows master)
Title: Message Title Mark Waite updated JENKINS-24125 Jenkins / JENKINS-24125 Git Polling fails for job restricted to Mac OS X slave (with Windows master) Change By: Mark Waite Status: Reopened Open Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.156599.1407279545000.4700.1578484921760%40Atlassian.JIRA.
[JIRA] (JENKINS-30316) Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build.
Title: Message Title Mark Waite updated JENKINS-30316 Jenkins / JENKINS-30316 Kicking off a build manually causes git-plugin to retrieve all commits since last time a build was triggered manually instead of since last build. Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.164905.1441408158000.4695.1578484921450%40Atlassian.JIRA.
[JIRA] (JENKINS-55972) Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master
Title: Message Title Mark Waite updated JENKINS-55972 Jenkins / JENKINS-55972 Unable to git clone on slave ,agent is launched via ssh. Git clone working fine on master Change By: Mark Waite Status: Fixed but Unreleased Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.197383.1549364479000.4684.1578484860264%40Atlassian.JIRA.
