[JIRA] (JENKINS-53127) Parallel sequential stages should display stage label
Title: Message Title Hokwang Lee commented on JENKINS-53127 Re: Parallel sequential stages should display stage label Oh, this is really really needed !!! Actually "Building and testing and supp... " is meaningless. stage name, in this case, Linux, Windows, iOS, is more important. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48096) EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance
Title: Message Title pete barnes commented on JENKINS-48096 Re: EC2 plugin does not obtain new credentials based on IAM role each time it launch a new slave instance Francis Upton any plans to close out this issue? it's a blocker for us. Only way we can seem to get it to work is to keep saving the credentials manually (which forces a refresh). However it means we can't use it for automation. Thanks! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Basil Crow commented on JENKINS-53569 Re: Remoting deadlock observed after upgrading to 3.26 I've attached to the bug full jstack output as well as the standard out of the Swarm Client and FINEST level log files from the Swarm Client. Note that compared to a successful connection, "Connected" is never printed to standard out. Even though the deadlock happens in the Swarm Client, the stack trace implicates Remoting. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Basil Crow updated an issue Jenkins / JENKINS-53569 Remoting deadlock observed after upgrading to 3.26 Change By: Basil Crow Attachment: jstack.txt Attachment: swarm-client.log Attachment: swarm-client.stdout.log Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53569) Remoting deadlock observed after upgrading to 3.26
Title: Message Title Basil Crow created an issue Jenkins / JENKINS-53569 Remoting deadlock observed after upgrading to 3.26 Issue Type: Bug Assignee: Jeff Thompson Components: remoting, swarm-plugin Created: 2018-09-14 05:34 Environment: Server: Jenkins 2.138.1 LTS (Remoting 3.25) Client: Swarm Client 3.14 (Remoting 3.26) Priority: Major Reporter: Basil Crow After upgrading my Jenkins master and the Swarm Client to the latest stable versions, I am seeing a new deadlock on the Swarm Client side when trying to connect to the master. The relevant output from jstack: Found one Java-level deadlock: = "pool-1-thread-3": waiting to lock monitor 0x00d12970 (object 0x000784a00fc0, a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer), which is held by "Thread-2" "Thread-2": waiting for ownable synchronizer 0x000784a4ac68, (a java.util.concurrent.locks.ReentrantReadWriteLock$NonfairSync), which is held by "pool-1-thread-3" Java stack information for the threads listed above: === "pool-1-thread-3": at org.jenkinsci.remoting.protocol.FilterLayer.onRecvRemoved(FilterLayer.java:134) - waiting to lock <0x000784a00fc0> (a org.jenkinsci.remoting.protocol.impl.ConnectionHeadersFilterLayer) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.getNextRecv(ProtocolStack.java:929) at org.jenkinsci.remoting.protocol.ProtocolStack$Ptr.onRecv(ProtocolStack.java:663) at
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Dominik Bartholdi commented on JENKINS-53545 Re: Error while saving System Configuration in Jenkins why do you think this has anything to do with the config-file-provider plugin? ...it seems not even to be installed. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann updated an issue Jenkins / JENKINS-53547 Parallel sequential pipeline rendering appears distorted while jobs are running Change By: Mathias Hasselmann Attachment: ghost tail.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann commented on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running We are lucky today, ghost tail: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Dominik Bartholdi assigned an issue to Unassigned Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Dominik Bartholdi Assignee: Dominik Bartholdi Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53545) Error while saving System Configuration in Jenkins
Title: Message Title Dominik Bartholdi updated an issue Jenkins / JENKINS-53545 Error while saving System Configuration in Jenkins Change By: Dominik Bartholdi Component/s: config-file-provider-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann commented on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running Just had the pleasure to catch a build with parallel branches missing in the status: Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann edited a comment on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running Just had the pleasure to catch a build with parallel branches missing in the status: !branches missing.png|thumbnail! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann updated an issue Jenkins / JENKINS-53547 Parallel sequential pipeline rendering appears distorted while jobs are running Change By: Mathias Hasselmann Attachment: branches missing.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann commented on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running Attached the full Jenkinsfile. Guess it's best to see the full picture. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann updated an issue Jenkins / JENKINS-53547 Parallel sequential pipeline rendering appears distorted while jobs are running Change By: Mathias Hasselmann Attachment: Jenkinsfile Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Olivier Lamy commented on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running any sample Jenkinsfile to reproduce? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title
Olivier Lamy commented on JENKINS-53311
Re: [Blue Ocean] Sequential stages appear to be completed but are still executing
weird as the parent node ('Nested B') has correct status RUNNING but not 'Nested B-1'.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes
Title: Message Title Jie Shen started work on JENKINS-53560 Change By: Jie Shen Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes
Title: Message Title Jie Shen commented on JENKINS-53560 Re: "Cannot stop sshd service" when provisioning Azure Windows nodes Thank you for reporting this issue, I will investigate and find out what we can do to improve it. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes
Title: Message Title Jie Shen assigned an issue to Jie Shen Jenkins / JENKINS-53560 "Cannot stop sshd service" when provisioning Azure Windows nodes Change By: Jie Shen Assignee: Azure DevOps Jie Shen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45041) Shared library pluging - can't use getResource to load a resource?
Title: Message Title Ilguiz Latypov commented on JENKINS-45041 Re: Shared library pluging - can't use getResource to load a resource? It's a pity libraryResource() is shy about selecting the currently active implicit library's resource. Instead I get an error, hudson.AbortException: Library resource com/COMPANY/FILE.EXT ambiguous among libraries [VER1, VER2] If the pipeline plugin has a way to select the innermost folder's implicit library, it could apply the same algorithm (or stick to the active version) when resolving the library resource. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Olivier Lamy assigned an issue to Olivier Lamy Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Olivier Lamy Assignee: Olivier Lamy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53568) slicer label updates all configs, not only changed ones
Title: Message Title Ian Williams created an issue Jenkins / JENKINS-53568 slicer label updates all configs, not only changed ones Issue Type: Bug Assignee: Mikael Gaunin Components: configurationslicing-plugin Created: 2018-09-13 23:26 Environment: configuration-slicing-plugin:1.45 metadata-1.1.0b Priority: Major Reporter: Ian Williams We have >55 unique labels and > 5000 jobs. Using configurationslicing Tied Label Slicer option, moved jobs from 3 labels (~10 jobs) to a new label category, click Save. The spinner goes forever before eventually timing out. We can see the timestamps of every single Jenkins job being updated. There is evidence in the logs it appears to be logging: INFO: Submitted to metadata-queue: hudson.model.FreeStyleProject@48ba120b for every single job. It's been running for 3+ hrs and it's 1/2 way done. Label slicer - AND every other slicer should ONLY update affected jobs. It appears perhaps under JENKINS-10431, some slicers were corrected. ALL slicers with global update pattern must be fixed and this behaviour eliminated.
[JIRA] (JENKINS-53248) Pipeline descends into infinite loop on deep class inheritence
Title: Message Title Stuart Rowe commented on JENKINS-53248 Re: Pipeline descends into infinite loop on deep class inheritence This appears to be the same as the issue I described in JENKINS-52395. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Indeed yes, it is critical. This has somehow slipped. It was looked at some time ago, but unfortunately is a HUGE amount of work as there is no way in the pipeline engine to track this information (especially not if people are using scripted pipelines, which are still popular, and were included at the time). It is not at all a small job cc Vivek Pandey Jenn Briden this somehow has slipped off the radar. It was on the old roadmap but don't know the status of it now. Given how old it is, it may be more feasible to do this in a declarative only context now and actually be possible. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Michael Neale assigned an issue to Unassigned Jenkins / JENKINS-39203 All stages show up as UNSTABLE when only one stage should Change By: Michael Neale Priority: Major Critical Assignee: Andrew Bayer Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title Taylor Patton commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should This critical issue is maddening. It's almost as if we have to separate our pipeline into small components (jobs) like we did with freestyle jobs, for the build status reporting to make sense. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53553) History trend should be shown only for at least two values
Title: Message Title Ulli Hafner edited a comment on JENKINS-53553 Re: History trend should be shown only for at least two values The task scanner has not been converted to the new API yet. It takes a little bit more time since some views need customization . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53553) History trend should be shown only for at least two values
Title: Message Title Ulli Hafner commented on JENKINS-53553 Re: History trend should be shown only for at least two values The task scanner has not been converted to the new API yet. It takes a little bit more time since some views need customization Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52239) being able to select which severity level to display in the graphical on job status page
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-52239 being able to select which severity level to display in the graphical on job status page Change By: Ulli Hafner currently jcurrently in the graphical all severities are displayed. in FPGA developpement we have a lot of warning severity (normal severity) and a few errors (high severity). in the graphical displayed errors are masked by the high number of warning.is it possible to choose which severity to display in the graphical ? we would like to display only errors (high severity) for instance. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53567) Create tools for all of the violations parsers (alias to other parser)
Title: Message Title Ulli Hafner created an issue Jenkins / JENKINS-53567 Create tools for all of the violations parsers (alias to other parser) Issue Type: Improvement Assignee: Ulli Hafner Components: warnings-plugin Created: 2018-09-13 21:03 Priority: Minor Reporter: Ulli Hafner Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Devin Nusbaum Labels: pipeline windows Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title
Devin Nusbaum updated an issue
Jenkins / JENKINS-53311
[Blue Ocean] Sequential stages appear to be completed but are still executing
Change By:
Devin Nusbaum
We have a visualisation problem in new "Sequential Stages". Stage likes In some cases, sequential stages get a green check mark and appear to be completed when it is executed even though they are still executing .Minimal pipeline example:{code:java}pipeline {agent any stages {stage('Parallel') {failFast falseparallel {stage('Nested B') {stages { stage('Nested B-1') { steps { echo 'Nested A-1' } } stage('Nested B-2') { steps { sleep time: 5, unit: 'MINUTES' } }}}stage('Nested C') {when { _expression_ { false == true }}stages { stage('Nested C-1') { steps { echo 'Nested C-1' } } stage('Nested C-2') { steps { echo 'Nested C-2' } }}}stage('Nested A') {steps { sleep time: 5, unit: 'MINUTES'}}}}}}{code}
Add Comment
[JIRA] (JENKINS-53311) [Blue Ocean] New sequential stage likes completed when it is executed
Title: Message Title
Devin Nusbaum commented on JENKINS-53311
Re: [Blue Ocean] New sequential stage likes completed when it is executed
I spent a few minutes reproducing this today. It looks like a legitimate bug. I will update the title and description to make them a little clearer. Here is the most minimal test case I could come up with:
pipeline {
agent any
stages {
stage('Parallel') {
parallel {
stage('Nested A') {
steps {
echo 'A'
}
}
stage('Nested B') {
stages {
stage('Nested B-1') {
steps {
sleep time: 1, unit: 'MINUTES'
}
}
}
}
}
}
}
}
And here is a screenshot that showing that Nested B-1 has a green check mark even though it is still executing:
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] Sequential stages appear to be completed but are still executing
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53311 [Blue Ocean] Sequential stages appear to be completed but are still executing Change By: Devin Nusbaum Summary: [Blue Ocean] New sequential stage likes Sequential stages appear to be completed when it is executed but are still executing Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53311) [Blue Ocean] New sequential stage likes completed when it is executed
Title: Message Title Devin Nusbaum updated an issue Jenkins / JENKINS-53311 [Blue Ocean] New sequential stage likes completed when it is executed Change By: Devin Nusbaum Attachment: Screen Shot 2018-09-13 at 16.52.57.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31710) view-job-filters plugin, Regular Expression Filter by SCM Configuration, doesn't work when filtering "Freestyle projects"
Title: Message Title Sven Schoenung resolved as Fixed Jenkins / JENKINS-31710 view-job-filters plugin, Regular _expression_ Filter by SCM Configuration, doesn't work when filtering "Freestyle projects" Change By: Sven Schoenung Status: Open Resolved Assignee: Jacob Robertson Sven Schoenung Resolution: Fixed Released As: 2.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-31710) view-job-filters plugin, Regular Expression Filter by SCM Configuration, doesn't work when filtering "Freestyle projects"
Title: Message Title Sven Schoenung commented on JENKINS-31710 Re: view-job-filters plugin, Regular _expression_ Filter by SCM Configuration, doesn't work when filtering "Freestyle projects" Fixed in 2.0.1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sven Schoenung resolved as Fixed Jenkins / JENKINS-29991 view-job-filters-plugin with SCM Job Configuration not working Change By: Sven Schoenung Status: Open Resolved Assignee: Jacob Robertson Sven Schoenung Resolution: Fixed Released As: 2.0.1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-29991) view-job-filters-plugin with SCM Job Configuration not working
Title: Message Title Sven Schoenung commented on JENKINS-29991 Re: view-job-filters-plugin with SCM Job Configuration not working Fixed in 2.0.1. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45200) Archiving artifacts fails, but build step is shown with a green dot
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-45200 Archiving artifacts fails, but build step is shown with a green dot Change By: Jesse Glick Status: Reopened Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Devin Nusbaum resolved as Fixed Since I have not heard back either way, I am going to go ahead and close this issue because at least one way it could happen was fixed in Jenkins 2.136. Please feel free to reopen the issue if you are still seeing it in Jenkins 2.136 or newer, Jenkins / JENKINS-30231 Build creates second workspace@2 for non-concurrent build configuration Change By: Devin Nusbaum Status: Open Resolved Assignee: Kohsuke Kawaguchi Devin Nusbaum Resolution: Fixed Released As: Jenkins Core 2.136 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-30231) Build creates second workspace@2 for non-concurrent build configuration
Title: Message Title Devin Nusbaum edited a comment on JENKINS-30231 Re: Build creates second workspace@2 for non-concurrent build configuration Since I have not heard back either way, I am going to go ahead and close this issue because at least one way it could happen was fixed in Jenkins 2.136. Please feel free to reopen the issue if you are still seeing it in Jenkins 2.136 or newer , . Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli closed an issue as Cannot Reproduce Jenkins / JENKINS-49502 trigger properties in scripted pipeline require 2 builds to get registered Change By: mike cirioli Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49502) trigger properties in scripted pipeline require 2 builds to get registered
Title: Message Title mike cirioli commented on JENKINS-49502 Re: trigger properties in scripted pipeline require 2 builds to get registered quick update - i have re-verified that you no longer need to run a scripted job with triggers twice in order to have them registered. Closing this issue. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Jesse Glick updated an issue Jenkins / JENKINS-50772 Content type not set reasonably Change By: Jesse Glick Component/s: apache-httpcomponents-client-4-api-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50772) Content type not set reasonably
Title: Message Title Jesse Glick commented on JENKINS-50772 Re: Content type not set reasonably Right, the question is whether the URL itself can encode the desired content type or whether this needs to be handled as an HTTP header by the uploading code. In the latter case, RobustHttpClient.uploadFile would need to be amended to set a header. (Then the next question is what content type to pick. Files.probeContentType seems like the right choice.) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53465) ChannelClosedException in Maven channel
Title: Message Title Jesse Glick commented on JENKINS-53465 Re: ChannelClosedException in Maven channel sto poodoff once again the warnings (JENKINS-53481) have nothing whatsoever to do with build failures. The failure reported originally in this issue looks like some kind of hard-to-diagnose Remoting channel outage. The latest failure looks like an error in your build, not a Jenkins issue. all is ok if run the same project in Terminal or IDE. It fails in Jenkins only. So stop using this plugin and use a freestyle or Pipeline job instead, with a simple shell step to run mvn. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52165) Use push rather than pull for durable task logging
Title: Message Title Jesse Glick updated JENKINS-52165 Jenkins / JENKINS-52165 Use push rather than pull for durable task logging Change By: Jesse Glick Status: Open Fixed but Unreleased Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52165) Use push rather than pull for durable task logging
Title: Message Title Jesse Glick stopped work on JENKINS-52165 Change By: Jesse Glick Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52165) Use push rather than pull for durable task logging
Title: Message Title Jesse Glick updated JENKINS-52165 Jenkins / JENKINS-52165 Use push rather than pull for durable task logging Change By: Jesse Glick Status: In Review Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53566) /about/ does not reflect packaged overrides
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-53566 /about/ does not reflect packaged overrides Issue Type: Bug Assignee: Oleg Nenashev Components: custom-war-packager Created: 2018-09-13 18:21 Priority: Minor Reporter: Jesse Glick If you package a custom version of remoting and then run the resulting WAR, /about/ still claims to contain the stock version under Maven ID. This seems to be because tmp/output/target/*-SNAPSHOT/WEB-INF/classes/META-INF/licenses.xml still contains 'Jenkins remoting layer' groupId='org.jenkins-ci.main' artifactId='remoting' version='3.25' url="" class="code-quote" style="color: #009100">'http://jenkins-ci.org/remoting/'>Contains the bootstrap code to bridge separate JVMs into a single semi-shared space. Reusable outside Jenkins. If it is too much work to patch this file, suggest at least amending the documentation for patching core libraries to explain that this URL should be ignored. Alternately, perhaps core should be looking at WEB-INF/lib/remoting-*-SNAPSHOT.jar!/META-INF/maven/org.jenkins-ci.main/remoting/pom.properties for overridden versions.
[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.
Title: Message Title R. Tyler Croy updated JENKINS-51304 Jenkins / JENKINS-51304 All evergreen-client calls should retry on connection failures. Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53541) Provide an API for a client to record a tainted update level
Title: Message Title R. Tyler Croy started work on JENKINS-53541 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy I believe this is redundant with this change to rely on socket.io as the default transport in the client Jenkins / JENKINS-51304 All evergreen-client calls should retry on connection failures. Change By: R. Tyler Croy Assignee: Baptiste Mathus R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-51304) All evergreen-client calls should retry on connection failures.
Title: Message Title R. Tyler Croy started work on JENKINS-51304 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52525) Investigate switchinig evergreen-client to use strictly socket.io messaging
Title: Message Title R. Tyler Croy updated JENKINS-52525 Jenkins / JENKINS-52525 Investigate switchinig evergreen-client to use strictly socket.io messaging Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53543) evergreen-client should re-authenticate when the jwt has expired.
Title: Message Title R. Tyler Croy updated JENKINS-53543 Jenkins / JENKINS-53543 evergreen-client should re-authenticate when the jwt has expired. Change By: R. Tyler Croy Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52569) Write end user docs to start instance (docker and aws flavors)
Title: Message Title R. Tyler Croy stopped work on JENKINS-52569 Change By: R. Tyler Croy Status: In Progress Open Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52525) Investigate switchinig evergreen-client to use strictly socket.io messaging
Title: Message Title R. Tyler Croy started work on JENKINS-52525 Change By: R. Tyler Croy Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52810) Parameterized Remote Trigger Plugin is not triggering job in remote jenkins
Title: Message Title Robert Hencke reopened an issue This is a bug not around the URL being null, but around the hostLocks and hostPermits fields being null when deserializing older configurations. I have submitted a pull request to fix here: https://github.com/jenkinsci/parameterized-remote-trigger-plugin/pull/47 Jenkins / JENKINS-52810 Parameterized Remote Trigger Plugin is not triggering job in remote jenkins Change By: Robert Hencke Resolution: Not A Defect Status: Resolved Reopened Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53564) Unable to open Jenkinsfile in blueocean pipeline editor
Title: Message Title
Mario Jauvin created an issue
Jenkins / JENKINS-53564
Unable to open Jenkinsfile in blueocean pipeline editor
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-pipeline-editor-plugin
Created:
2018-09-13 16:48
Environment:
Blueocean 1.8.2 Jenkins 2.121.3 Windows 10
Priority:
Major
Reporter:
Mario Jauvin
If I create the following Jenkins file in the pipeline editor:
pipeline {
agent any
stages {
stage('Build') {
steps {
sh 'mvn clean package'
}
}
}
}
Everything works fine. If I add the following snippet after the stage line:
tools {
maven 'mvn'
jdk 'jdk8'
}
Then the pipeline editor displays a blank page. If I remove the snipped then all is back normal in the editor. This Jenkinsfile is the same as the Jenkinsfile in the https://github.com/jenkinsci/jenkins-test-harness-htmlunit/blob/master/Jenkinsfile repository which is utilized by the ci.jenkins.io build site.
[JIRA] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password
Title: Message Title Mark Waite commented on JENKINS-28460 Re: Failed to connect to private bitbucket repository with username/password Thanks James Howe, that is good news. I can enable that in my regression tests and it should pass. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password
Title: Message Title James Howe commented on JENKINS-28460 Re: Failed to connect to private bitbucket repository with username/password Mark Waite no, that works too AFAICT. Though obviously not a great way to do it, as your password is then in plaintext all over the place. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password
Title: Message Title Mark Waite commented on JENKINS-28460 Re: Failed to connect to private bitbucket repository with username/password Thanks James Howe! The specific case that was failing for me did not use a Jenkins credential. It embedded the username and password into the URL as in: https://username:passw...@bitbucket.org/username/private-repo.git I suspect that case may still be broken. I believe it is a largely irrelevant case, but it was not well-behaved the last time I checked (3 years ago). I have a test in my regression kit that is known to fail with that case. I haven't run that known failure test in quite a while. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53563) RegistryKeyMaterialFactory should support multiple credentials
Title: Message Title
Alon Bar-Lev created an issue
Jenkins / JENKINS-53563
RegistryKeyMaterialFactory should support multiple credentials
Issue Type:
Bug
Assignee:
Unassigned
Components:
docker-commons-plugin
Created:
2018-09-13 15:47
Environment:
master
Priority:
Major
Reporter:
Alon Bar-Lev
Hello, We have a process that fetches a file from one repo then push to different repository.
dir('docker') {
docker.withRegistry(BASE_IMAGE_REGISTRY_URL, BASE_IMAGE_REGISTRY_JENKINS,) {
docker.withRegistry(LOCAL_REGISTRY_URL, LOCAL_REGISTRY_JENKINS,) {
stage("package/docker") {
sh([script: 'make'])
}
}
}
}
We have discovered that the docker.withRegistry create a new `DOCKER_CONFIG` for each docker.withRegistry and traced it to `org.jenkinsci.plugins.docker.commons.impl.RegistryKeyMaterialFactory`. Per each materialize() there is unconditional call to `createSecretsDirectory()` which loses loses the credentials in previous block. In this implementation only a single docker registry may be authenticated, while docker supports many. Suggested implementation:
Do not create new secrets directory if already exist, it can be checked via the `DOCKER_CONFIG` variable. Maybe force first time creation within the entire instance to
[JIRA] (JENKINS-52525) Investigate switchinig evergreen-client to use strictly socket.io messaging
Title: Message Title R. Tyler Croy updated an issue Jenkins / JENKINS-52525 Investigate switchinig evergreen-client to use strictly socket.io messaging Change By: R. Tyler Croy Sprint: Evergreen - Milestone 1 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53528) Parallel-test-executor can excessively split tests
Title: Message Title Steve Arch assigned an issue to Steve Arch Jenkins / JENKINS-53528 Parallel-test-executor can excessively split tests Change By: Steve Arch Assignee: Steve Arch Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53528) Parallel-test-executor can excessively split tests
Title: Message Title Steve Arch commented on JENKINS-53528 Re: Parallel-test-executor can excessively split tests PR: https://github.com/jenkinsci/parallel-test-executor-plugin/pull/38 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53528) Parallel-test-executor can excessively split tests
Title: Message Title Steve Arch updated JENKINS-53528 Jenkins / JENKINS-53528 Parallel-test-executor can excessively split tests Change By: Steve Arch Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52525) Investigate switchinig evergreen-client to use strictly socket.io messaging
Title: Message Title R. Tyler Croy assigned an issue to R. Tyler Croy I need to do this as a consequence of JENKINS-53543 Jenkins / JENKINS-52525 Investigate switchinig evergreen-client to use strictly socket.io messaging Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53528) Parallel-test-executor can excessively split tests
Title: Message Title Steve Arch started work on JENKINS-53528 Change By: Steve Arch Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42671) Durable Task 1.13 does not have the compatibleSince definition in POM
Title: Message Title Devin Nusbaum updated JENKINS-42671 There are no plans to make this change, and we are long past the 1.13 release, so I am going ahead and closing it. Jenkins / JENKINS-42671 Durable Task 1.13 does not have the compatibleSince definition in POM Change By: Devin Nusbaum Status: In Review Closed Resolution: Won't Do Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53561) ApiTokenStore.HashedToken is not serializable
Title: Message Title James Nord assigned an issue to James Nord Jenkins / JENKINS-53561 ApiTokenStore.HashedToken is not serializable Change By: James Nord Assignee: James Nord Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53562) Add remote root directory configuration
Title: Message Title Luca Naldini assigned an issue to Unassigned Jenkins / JENKINS-53562 Add remote root directory configuration Change By: Luca Naldini Assignee: Evan Brown Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53562) Add remote root directory configuration
Title: Message Title Luca Naldini created an issue Jenkins / JENKINS-53562 Add remote root directory configuration Issue Type: New Feature Assignee: Evan Brown Components: google-compute-engine-plugin Created: 2018-09-13 15:06 Priority: Major Reporter: Luca Naldini The node is currently starting up and outputting: NOTE: Relative remote path resolved to: /home/jenkins/./.jenkins-slave Evacuated stdout Agent successfully connected and online I would like to be able to set the remote host to /home/jenkins instead. Non-cloud slaves have the option Remote root directory and would be nice if this plugin could add that possibility too. Add Comment
[JIRA] (JENKINS-53365) any plugin depending on junit plugin is forced to depend on scm-api
Title: Message Title James Nord updated JENKINS-53365 Jenkins / JENKINS-53365 any plugin depending on junit plugin is forced to depend on scm-api Change By: James Nord Status: In Review Closed Resolution: Fixed Released As: junit-1.25 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53561) ApiTokenStore.HashedToken is not serializable
Title: Message Title James Nord created an issue Jenkins / JENKINS-53561 ApiTokenStore.HashedToken is not serializable Issue Type: Improvement Assignee: Unassigned Components: core Created: 2018-09-13 14:42 Priority: Minor Reporter: James Nord I have a need to serialise the HashedToken via remoting, however it does not implement Serializable. it should be given it is stored on disk via XStream marked as serializable anyway (and it has a readResolve() method ) Add Comment This message was sent
[JIRA] (JENKINS-53465) ChannelClosedException in Maven channel
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-53465 ChannelClosedException in Maven channel Change By: sakshi sood After upgrading jenkins from 2.89.4 to 2. 121 138 . 3 1 , I am not able build my code using maven. The build is failing and logs have lots of seeing the below errors in the logs . Please note i have upgraded all my plugins to latest version.Sep 07, 2018 12:23:23 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.FilePath$28 in [ file:/var/lib/tomcat7/webapps/ROOT/WEB-INF/lib/jenkins-core-2.121.3.jar |file://var/lib/tomcat7/webapps/ROOT/WEB-INF/lib/jenkins-core-2.121.3.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:24 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.Git$1 in [ file:/var/hudson/master/plugins/git-client/WEB-INF/lib/git-client.jar |file://var/hudson/master/plugins/git-client/WEB-INF/lib/git-client.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:25 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1 in [ file:/var/hudson/master/plugins/git-client/WEB-INF/lib/git-client.jar |file://var/hudson/master/plugins/git-client/WEB-INF/lib/git-client.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:36 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.FilePath$27 in [ file:/var/lib/tomcat7/webapps/ROOT/WEB-INF/lib/jenkins-core-2.121.3.jar |file://var/lib/tomcat7/webapps/ROOT/WEB-INF/lib/jenkins-core-2.121.3.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:52 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class hudson.maven.reporters.MavenArtifactArchiver$2 in [ file:/var/hudson/master/plugins/maven-plugin/WEB-INF/lib/maven-plugin.jar |file://var/hudson/master/plugins/maven-plugin/WEB-INF/lib/maven-plugin.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:53 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.whitesource.jenkins.extractor.maven.MavenDependenciesRecorder$1 in [ file:/var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource.jar |file://var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource.jar] ; see: [ https://jenkins.io/redirect/serialization-of-anonymous-classes/ ] Sep 07, 2018 12:23:53 PM org.jenkinsci.remoting.util.AnonymousClassWarnings warnWARNING: Attempt to (de-)serialize anonymous class org.jfrog.hudson.maven2.MavenDependenciesRecorder$1 in [
[JIRA] (JENKINS-53456) Whitesource-plugin affected by JEP-200
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-53456 Whitesource-plugin affected by JEP-200 Change By: sakshi sood I have upgraded Jenkins from version 2.89.4 to [ 2. 121 138 . 3 1|https://updates.jenkins-ci.org/download/war/2.138.1/jenkins.war] I can see below lines in the logs post upgradeWARNING: org.whitesource.agent.api.model.DependencyInfo in [ file:/var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource-fs-a |file://var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource-fs-a] gent-18.6.3.jar might be dangerous, so rejecting; see [ https://jenkins.io/redirect/class-filter/ ] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53456) Whitesource-plugin affected by JEP-200
Title: Message Title sakshi sood updated an issue Jenkins / JENKINS-53456 Whitesource-plugin affected by JEP-200 Change By: sakshi sood I have upgraded Jenkins from version 2.89.4 to [ 2.138.1 |https://updates.jenkins-ci.org/download/war/2.138.1/jenkins.war] I can see below lines in the logs post upgradeWARNING: org.whitesource.agent.api.model.DependencyInfo in [file:/var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource-fs-a|file://var/hudson/master/plugins/whitesource/WEB-INF/lib/whitesource-fs-a] gent-18.6.3.jar might be dangerous, so rejecting; see [https://jenkins.io/redirect/class-filter/] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53547) Parallel sequential pipeline rendering appears distorted while jobs are running
Title: Message Title Mathias Hasselmann commented on JENKINS-53547 Re: Parallel sequential pipeline rendering appears distorted while jobs are running Also note how there is only one or even no blue circle indicating activity while actually multiple blue circles should be shown because multiple stages are active. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53560) "Cannot stop sshd service" when provisioning Azure Windows nodes
Title: Message Title Nick Jones created an issue Jenkins / JENKINS-53560 "Cannot stop sshd service" when provisioning Azure Windows nodes Issue Type: Bug Assignee: Azure DevOps Components: azure-vm-agents-plugin Created: 2018-09-13 14:30 Environment: Azure VM Agents plugin 0.7.3, custom Windows Server 2016-based images for Azure agent VMs. Priority: Minor Reporter: Nick Jones Occasionally – maybe 10% of the time we provision Azure agents – the agent setup fails with the following error: Restart-Service : Service 'sshd (sshd)' cannot be stopped due to the following error: Cannot stop sshd service on computer '.'. At line:1 char:1 + Restart-Service sshd + + CategoryInfo : CloseError: (System.ServiceProcess.ServiceContro ller:ServiceController) [Restart-Service], ServiceCommandException + FullyQualifiedErrorId : CouldNotStopService,Microsoft.PowerShell.Command s.RestartServiceCommand I understand that restarting sshd is necessary in order to pick up new environment variables, but perhaps there could be a longer attempt, or more than one? Eventually the agent is detected to have failed to provision, and a new one is spawned automatically – so no manual intervention is necessary – but with the 10-15 minute provisioning time for our Azure Windows Server 2016 agents, that causes quite a wait. Can anything more be done here?
[JIRA] (JENKINS-43146) java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira
Title: Message Title Nil Paul commented on JENKINS-43146 Re: java.lang.NullPointerException when publish JUnit.xml result to Zephyr for Jira Using jenkins version 2.121.3. I am getting below error:- [ZapiTestResultReporter] [INFO] Examining test results... Build result is UNSTABLE Total Test Cases : 4ERROR: Build step failed with exception java.lang.NullPointerException at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.executeTestsZFJC(TestCaseUtil.java:1168) at com.thed.zephyr.jenkins.utils.rest.TestCaseUtil.processTestCaseDetails(TestCaseUtil.java:715) at com.thed.zephyr.jenkins.reporter.ZfjReporter.perform(ZfjReporter.java:101) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:744) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:690) at hudson.model.Build$BuildExecution.post2(Build.java:186) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:635) at hudson.model.Run.execute(Run.java:1823) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Build step 'Publish test result to Zephyr for JIRA' marked build as failure Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Chen Fliesher - I reproduced that exact error with Script Security 1.45 installed, but could not reproduce it with Script Security 1.46. You should be fine with 1.46. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password
Title: Message Title James Howe commented on JENKINS-28460 Re: Failed to connect to private bitbucket repository with username/password This seems to work fine now. Just add the URL e.g. https://bitbucket.org/owner/repo.git and select a username+password credential. Jenkins 2.138.1, Git client plugin 2.7.3, Git plugin 3.9.1, Credentials Plugin 2.1.18 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-28460) Failed to connect to private bitbucket repository with username/password
Title: Message Title James Howe resolved as Fixed Jenkins / JENKINS-28460 Failed to connect to private bitbucket repository with username/password Change By: James Howe Status: Reopened Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49483) When using Streams, custom view definition seems to be ignored
Title: Message Title Mateusz Delikat assigned an issue to Paul Allen Jenkins / JENKINS-49483 When using Streams, custom view definition seems to be ignored Change By: Mateusz Delikat Assignee: Paul Allen Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53559) PTC integrity plugin used via Pipeline script can not run on other Master due to maschine dependent hash
Title: Message Title
Gregor Heilmann updated an issue
Jenkins / JENKINS-53559
PTC integrity plugin used via Pipeline script can not run on other Master due to maschine dependent hash
Change By:
Gregor Heilmann
I am facing an issue with PTC integrity plugin used via Pipeline script.In principle it is working fine. But when trying to execute the job on a different master the script fails, as the checkout command for PTC includes the hash for the server configuration as well as Configuration name: _configurationName_, _serverConfig_:e.g: {{ checkout }}{{ ([ $class: 'IntegritySCM', }}{{checkpointBeforeBuild: false, }} {{ configPath: '/any/any/project.pj', }} {{ configurationName: 'ed1d9d74-cb0b-4446-ba16-0b5520e061cf', }}{{restoreTimestamp: false, }}{{serverConfig: '6038a84b-7e07-4c2f-b2d6-fe95e4039f3c', }}{{skipAuthorInfo: false }} {{ ]) }} If the plugin could be improved to also accept the name of the configuration instead or additional to the hash, this would increase interoperability of the pipeline scripts a lot. And also the {{configurationName:}} could be ommited omitted I think...e.g: {{ checkout }}{{ ([ $class: 'IntegritySCM', }}{{checkpointBeforeBuild: false, }} {{ configPath: '/any/any/project.pj', }} {{ restoreTimestamp: false, }}{{serverConfig: 'u...@mks.location.domain.com:7001', }}{{skipAuthorInfo: false }} {{ ]) }} In the drop down menu of the snippet generator, also the name is in clear text and not represented as hash ;)
Add Comment
This message was
[JIRA] (JENKINS-53559) PTC integrity plugin used via Pipeline script can not run on other Master due to maschine dependent hash
Title: Message Title
Gregor Heilmann created an issue
Jenkins / JENKINS-53559
PTC integrity plugin used via Pipeline script can not run on other Master due to maschine dependent hash
Issue Type:
Improvement
Assignee:
PTC ALM
Components:
integrity-plugin
Created:
2018-09-13 13:44
Environment:
Jenkins 2.121.3 Windows Server 2008 R2 PTC Integrity Plugin 2.2
Labels:
plugin pipeline configuration
Priority:
Major
Reporter:
Gregor Heilmann
I am facing an issue with PTC integrity plugin used via Pipeline script. In principle it is working fine. But when trying to execute the job on a different master the script fails, as the checkout command for PTC includes the hash for the server configuration as well as Configuration name: configurationName, serverConfig: e.g: checkout{{([ $class: 'IntegritySCM', }} {{ checkpointBeforeBuild: false,}} {{ configPath: '/any/any/project.pj',}} {{ configurationName: 'ed1d9d74-cb0b-4446-ba16-0b5520e061cf', }} {{ restoreTimestamp: false, }} {{ serverConfig: '6038a84b-7e07-4c2f-b2d6-fe95e4039f3c', }} {{ skipAuthorInfo: false}} {{ ])}} If the plugin could be improved to also accept the name of the configuration instead or additional to the hash, this would increase interoperability of the pipeline scripts a lot. And also the configurationName: could be ommited I think... e.g: checkout{{([ $class: 'IntegritySCM', }} {{ checkpointBeforeBuild: false,}} {{ configPath: '/any/any/project.pj',}} {{restoreTimestamp: false, }} {{ serverConfig: 'u...@mks.location.domain.com:7001', }} {{ skipAuthorInfo: false}} {{ ])}} In the drop down menu of the
[JIRA] (JENKINS-53420) groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding
Title: Message Title Andrew Bayer commented on JENKINS-53420 Re: groovy.lang.MissingPropertyException: No such property: node for class: groovy.lang.Binding Chen Fliesher - that error showed up with 1.46 installed? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53553) History trend should be shown only for at least two values
Title: Message Title David Aldrich commented on JENKINS-53553 Re: History trend should be shown only for at least two values How does one use the task scanning functionality? (to search for TODO etc). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53536) Charts to deploy dropdown not populating correctly
Title: Message Title Guillermo Sanchez Urien commented on JENKINS-53536 Re: Charts to deploy dropdown not populating correctly Hi Steve, thanks for reporting, but the issue is that the plugin only supports classic Helm charts (https://github.com/helm/charts-classic), which are now obsolete. We haven't had the opportunity to stay current, and unfortunately I cannot provide you an estimate of when we will. But if you want to contribute with any PR, we would be happy to include it! Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53558) Apply top level failFast option to all parallel stages inside Jenkinsfile.
Title: Message Title
Leonard Lee created an issue
Jenkins / JENKINS-53558
Apply top level failFast option to all parallel stages inside Jenkinsfile.
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2018-09-13 12:30
Priority:
Minor
Reporter:
Leonard Lee
We would like to have a top-level option failFast true for all parallel stages inside a single Jenkinsfile.
pipeline {
agent any
stages {
failFast true // Could we have a top-level failFast option?
stage('Parallel Stage One') {
// failFast true
parallel {
stage('Stage A') { }
stage('Stage B') { }
stage('Stage C') { }
}
}
stage('Parallel Stage Two') {
// failFast true
parallel {
stage('Stage D') { }
stage('Stage E') { }
stage('Stage F') { }
}
}
stage('Parallel Stage Three') {
// failFast true
parallel {
stage('Stage G') { }
stage('Stage H') { }
stage('Stage I') { }
}
}
}
}
[JIRA] (JENKINS-53556) Fix invalid proxy settings and validation
Title: Message Title Naresh Rayapati commented on JENKINS-53556 Re: Fix invalid proxy settings and validation PR: Merged above pull request, will release it soon. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49033) Issue with HPE Application Automation Tools plugin
Title: Message Title Rolando-Mihai Vlad commented on JENKINS-49033 Re: Issue with HPE Application Automation Tools plugin Hello Edwin, I forgot to ask you to add the LoadRunner version and plugin version. Also, please add the whole LRA folder for both cases. Regards, Rolando Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53557) Add jiraWaitForIssueUpdate step
Title: Message Title Naresh Rayapati updated JENKINS-53557 Jenkins / JENKINS-53557 Add jiraWaitForIssueUpdate step Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53557) Add jiraWaitForIssueUpdate step
Title: Message Title Naresh Rayapati started work on JENKINS-53557 Change By: Naresh Rayapati Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-53557) Add jiraWaitForIssueUpdate step
Title: Message Title Naresh Rayapati created an issue Jenkins / JENKINS-53557 Add jiraWaitForIssueUpdate step Issue Type: New Feature Assignee: Naresh Rayapati Components: jira-steps-plugin Created: 2018-09-13 11:07 Priority: Minor Reporter: Naresh Rayapati Add a new step allowing to pause a pipeline until a Jira issue is updated. PR: https://github.com/jenkinsci/jira-steps-plugin/pull/79 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-53556) Fix invalid proxy settings and validation
Title: Message Title Naresh Rayapati updated JENKINS-53556 Jenkins / JENKINS-53556 Fix invalid proxy settings and validation Change By: Naresh Rayapati Status: In Progress Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
