[JIRA] (JENKINS-60939) Multiple Echo in stage not rendering.
Title: Message Title CHRISTOPHER KELLY created an issue Jenkins / JENKINS-60939 Multiple Echo in stage not rendering. Issue Type: Bug Assignee: Unassigned Attachments: Code.png, Expanded Output.png, Output.png Components: pipeline Created: 2020-02-02 01:30 Environment: Latest jenkins/plugins running on windows if it matters. Jenkins ver. 2.219 Blue Ocean 1.22.0 Priority: Minor Reporter: CHRISTOPHER KELLY The echo works for 1 out of the 4 statements completely but all 4 partially. As your can see on the "Output.png" attachment MyJob_PublishConfig is shown how I want all 4 to look but the other 3 you have to expand the item as shown in "Expanded Output.png" I am sure I am doing something stupid but I honestly do not see a difference in the 4 echo statements. Add Comment
[JIRA] (JENKINS-60906) Write list data to
Title: Message Title _peedus updated an issue Jenkins / JENKINS-60906 Write list data to Change By: _peedus 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.204297.1580312483000.10403.1580585100199%40Atlassian.JIRA.
[JIRA] (JENKINS-60906) Write list data to
Title: Message Title
_peedus updated an issue
Jenkins / JENKINS-60906
Write list data to
Change By:
_peedus
Hi,While writing data to influxDB using [InfluxDBPlugin|https://wiki.jenkins.io/display/JENKINS/InfluxDB+Plugin], is there a possibility to provide list data to the *_customDataMap_* and *_customDataMapTags_* # multiple records of same table data (list belonging to same entity) # multiple records of different table (list belonging to different entity){{//sample data}}def data ="" error:500], [case:4, error:1001], [case:4, error:91]], *fix_detail*:[[fix:1101, prio:1], [fix:, prio:5]]] Is this supported? At the moment, I am able to write individual record of entities, but adding multiple records all at once fails.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
[JIRA] (JENKINS-15061) Wrong LIBPATH when running ssh slave on AIX
Title: Message Title Ivan Fernandez Calvo updated JENKINS-15061 Jenkins / JENKINS-15061 Wrong LIBPATH when running ssh slave on AIX Change By: Ivan Fernandez Calvo 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.145781.1346937144000.10389.1580577361448%40Atlassian.JIRA.
[JIRA] (JENKINS-13776) Slave is unable to checkout svn due to missing resources
Title: Message Title Ivan Fernandez Calvo updated JENKINS-13776 Jenkins / JENKINS-13776 Slave is unable to checkout svn due to missing resources Change By: Ivan Fernandez Calvo 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.144243.1337057985000.10391.1580577361521%40Atlassian.JIRA.
[JIRA] (JENKINS-8329) UTF-8 characters turn to question marks in slave log, display correctly in master log
Title: Message Title Ivan Fernandez Calvo updated JENKINS-8329 Jenkins / JENKINS-8329 UTF-8 characters turn to question marks in slave log, display correctly in master log Change By: Ivan Fernandez Calvo 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.138439.129256249.10393.1580577361578%40Atlassian.JIRA.
[JIRA] (JENKINS-17256) Error while parsing PuTTY key file
Title: Message Title Ivan Fernandez Calvo updated JENKINS-17256 Jenkins / JENKINS-17256 Error while parsing PuTTY key file Change By: Ivan Fernandez Calvo 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.148088.1363622262000.10382.1580577361270%40Atlassian.JIRA.
[JIRA] (JENKINS-37617) space in Host address cauese unknown/connection error
Title: Message Title Ivan Fernandez Calvo updated JENKINS-37617 Jenkins / JENKINS-37617 space in Host address cauese unknown/connection error Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.27 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.173735.1471946633000.10356.1580577301420%40Atlassian.JIRA.
[JIRA] (JENKINS-19465) Slave hangs while being launched
Title: Message Title Ivan Fernandez Calvo updated JENKINS-19465 Jenkins / JENKINS-19465 Slave hangs while being launched Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.150915.1378267668000.10358.1580577301458%40Atlassian.JIRA.
[JIRA] (JENKINS-43779) Plugin not respecting node JAVA_HOME
Title: Message Title Ivan Fernandez Calvo updated JENKINS-43779 Jenkins / JENKINS-43779 Plugin not respecting node JAVA_HOME Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.181197.1492814051000.10353.1580577240162%40Atlassian.JIRA.
[JIRA] (JENKINS-45001) KnownHostsFileKeyVerificationStrategy is not configurable
Title: Message Title Ivan Fernandez Calvo updated JENKINS-45001 Jenkins / JENKINS-45001 KnownHostsFileKeyVerificationStrategy is not configurable Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.183088.1497971728000.10351.1580577180478%40Atlassian.JIRA.
[JIRA] (JENKINS-48618) SSH Slaves should pass read timeout to TrileadSSH and gracefully handle it in the logic
Title: Message Title Ivan Fernandez Calvo resolved as Fixed Jenkins / JENKINS-48618 SSH Slaves should pass read timeout to TrileadSSH and gracefully handle it in the logic Change By: Ivan Fernandez Calvo Status: In Progress Resolved Resolution: Fixed Released As: trilead-ssh2-build-217-jenkins-16 ssh-slaves-1.31.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.187267.1513635711000.10349.1580577180452%40Atlassian.JIRA.
[JIRA] (JENKINS-48617) SSH Slaves should ALWAYS pass connection timeout to connection.connect()
Title: Message Title Ivan Fernandez Calvo updated JENKINS-48617 Jenkins / JENKINS-48617 SSH Slaves should ALWAYS pass connection timeout to connection.connect() Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.187266.1513634884000.10347.1580577180430%40Atlassian.JIRA.
[JIRA] (JENKINS-49118) SSH Slaves 1.25 Breaks
Title: Message Title Ivan Fernandez Calvo updated JENKINS-49118 Jenkins / JENKINS-49118 SSH Slaves 1.25 Breaks Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.30.0 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.187953.1516729442000.10335.1580577120879%40Atlassian.JIRA.
[JIRA] (JENKINS-48829) Linux slaves disconnect intermittently
Title: Message Title Ivan Fernandez Calvo updated JENKINS-48829 Jenkins / JENKINS-48829 Linux slaves disconnect intermittently Change By: Ivan Fernandez Calvo 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.187613.1515184181000.10345.1580577121119%40Atlassian.JIRA.
[JIRA] (JENKINS-48955) master-slave connection getting terminated once in every 12 hours and recovered after 1 minute
Title: Message Title Ivan Fernandez Calvo updated JENKINS-48955 Jenkins / JENKINS-48955 master-slave connection getting terminated once in every 12 hours and recovered after 1 minute Change By: Ivan Fernandez Calvo 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.187765.1516088319000.10343.1580577121088%40Atlassian.JIRA.
[JIRA] (JENKINS-51352) Windows slave not getting connected
Title: Message Title Ivan Fernandez Calvo updated JENKINS-51352 Jenkins / JENKINS-51352 Windows slave not getting connected Change By: Ivan Fernandez Calvo 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.190698.1526438065000.10328.1580577060647%40Atlassian.JIRA.
[JIRA] (JENKINS-50601) SSH plugin cannot negotiate
Title: Message Title Ivan Fernandez Calvo updated JENKINS-50601 Jenkins / JENKINS-50601 SSH plugin cannot negotiate Change By: Ivan Fernandez Calvo 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.189675.1522946455000.10330.1580577060677%40Atlassian.JIRA.
[JIRA] (JENKINS-53810) Launch Agents fails with ERROR: null java.util.concurrent.CancellationException
Title: Message Title Ivan Fernandez Calvo updated JENKINS-53810 Jenkins / JENKINS-53810 Launch Agents fails with ERROR: null java.util.concurrent.CancellationException Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.30.0 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.194324.1538032375000.10309.1580577000928%40Atlassian.JIRA.
[JIRA] (JENKINS-56885) It is possible to save a Node without host configuration
Title: Message Title Ivan Fernandez Calvo updated JENKINS-56885 Jenkins / JENKINS-56885 It is possible to save a Node without host configuration Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.30.0 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.198556.1554386094000.10306.1580576940221%40Atlassian.JIRA.
[JIRA] (JENKINS-55353) Upgrade Jenkins core to 2.138.4
Title: Message Title Ivan Fernandez Calvo updated JENKINS-55353 Jenkins / JENKINS-55353 Upgrade Jenkins core to 2.138.4 Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.30.0 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.196456.1546023241000.10307.1580576940238%40Atlassian.JIRA.
[JIRA] (JENKINS-57018) Allow to enable/disable TCP_NODELAY in SSHConnector
Title: Message Title Ivan Fernandez Calvo updated JENKINS-57018 Jenkins / JENKINS-57018 Allow to enable/disable TCP_NODELAY in SSHConnector Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.30.0 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.198720.155540360.10304.1580576880256%40Atlassian.JIRA.
[JIRA] (JENKINS-57019) Allow to set working directory in SSHConnector
Title: Message Title Ivan Fernandez Calvo updated JENKINS-57019 Jenkins / JENKINS-57019 Allow to set working directory in SSHConnector Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.198721.1555403717000.10303.1580576880137%40Atlassian.JIRA.
[JIRA] (JENKINS-58589) Re-make the retry connection process
Title: Message Title Ivan Fernandez Calvo updated JENKINS-58589 Jenkins / JENKINS-58589 Re-make the retry connection process Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.200745.156373970.10300.1580576820564%40Atlassian.JIRA.
[JIRA] (JENKINS-59427) Rename SSH Slaves Plugin
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59427 Jenkins / JENKINS-59427 Rename SSH Slaves Plugin Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.202010.1568797619000.10299.1580576820553%40Atlassian.JIRA.
[JIRA] (JENKINS-60812) Failed known_hosts verification for non-standard ssh port
Title: Message Title Ivan Fernandez Calvo updated JENKINS-60812 Jenkins / JENKINS-60812 Failed known_hosts verification for non-standard ssh port Change By: Ivan Fernandez Calvo Status: In Review Resolved Resolution: Fixed Released As: ssh-slaves-1.31.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.204147.1579417162000.10293.1580576760266%40Atlassian.JIRA.
[JIRA] (JENKINS-59732) SSH agent descriptors shouldn't say "agent agents"
Title: Message Title Ivan Fernandez Calvo updated JENKINS-59732 Jenkins / JENKINS-59732 SSH agent descriptors shouldn't say "agent agents" Change By: Ivan Fernandez Calvo Status: Fixed but Unreleased Resolved Released As: ssh-slaves-1.31.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.202450.1570725387000.10295.1580576760417%40Atlassian.JIRA.
[JIRA] (JENKINS-60358) Support Root=null value in Template workspace - Currently it is overridden, failing sync
Title: Message Title Shai Shapira commented on JENKINS-60358 Re: Support Root=null value in Template workspace - Currently it is overridden, failing sync Any Update? 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.203377.1575437377000.10291.1580576640250%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title jerry wiltse commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently Thanks for the effort! i just updated my last post with the actual calling code rather than the thing with the agent labels. Indeed, this semaphore-like strategy is another form of the previously posted suggestions with a limited number of named queues, where jobs get assigned to queues at the start and which suffers from the limitations/disadvantages you mentioned. For our case, it's a lot less desirable than the current queuing strategy, if only the wait step didn't have the verbosity problem. I'll continue to look for suggestions on making the current strategy work, and working around that problem. 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.181710.1494001199000.10243.1580576220834%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob, def List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) { def Map branches = [failFast: failFast]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranches def String itemValue = items[i]branches[itemValue] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code}Make items a def so that it is more versatile. For example, [each item can be a map|https://jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/] from a matrix of items and not just a String.You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.My previous example is not a true semaphore. All it does is generate a limited number of lock IDs using the modulo operator.
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
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,def items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesdef itemValue = items[i]branches[itemValue] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code}Make items a def so that it is more versatile. For example, [each item can be a map|https://jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/] from a matrix of items and not just a String .You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.My previous example is not a true semaphore. All it does is generate a limited number of lock IDs using the modulo operator.
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-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,def items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [ failFast : failFast ]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesdef itemValue = items[i]branches[itemValue] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code}Make items a def so that it is more versatile. For example, [each item can be a map|https://jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/] from a matrix of items and not just a String.You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.My previous example is not a true semaphore. All it does is generate a limited number of lock IDs using the modulo operator.
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-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob, List def items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranches String def itemValue = items[i]branches[itemValue] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code} Make items a def so that it is more versatile. For example, [each item can be a map|https://jenkins.io/blog/2019/12/02/matrix-building-with-scripted-pipeline/] from a matrix of items. You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.My previous example is not a true semaphore. All it does is generate a limited number of lock IDs using the modulo operator.
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-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesString itemValue = items[i]branches[itemValue] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code}You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent. My previous example is not a true semaphore. All it does is generate a limited number of lock IDs using the modulo operator.
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.181710.1494001199000.10008.1580575620962%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
jerry wiltse edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
I don't understand this most recent suggestion. I've never worked with semaphores, proper or otherwise. The drawbacks already sound significant and prohibitive.[~teilo] we're still stuck on this.Our current implementation adds 25%-75% to the runtime of a parallel job in our bigger jobs, presumably because of the CPU monopolization that you mentioned. Right now, we simply can't use it, and so we still don't have a throttling mechanism for our case.If waitUntil() could be changed to be a single step as you mentioned, that could solve it for us with less custom code, that would be desirable. I'd be surprised if anyone would disagree with the premise of that request. Where could i file the feature request for that step? I don't know what plugin it would be part of.In the meantime, do you have any other suggestions on how to fix our current implementation so that it doesn't kill performance?{code:java}static def parallelLimitedBranches(CpsScript currentJob,List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]Deque latch = new LinkedBlockingDeque(maxConcurrentBranches)maxConcurrentBranches.times {latch.offer("$it")}items.each {branches["${it}"] = {def queueSlot = nullwhile (true) {queueSlot = latch.pollFirst();if (queueSlot != null) { break;}}try {body(it)}finally {latch.offer(queueSlot)}}}currentJob.parallel(branches)}{code}With calling code in the form of:{code:java} List agents = Jenkins.instance.computers.collect { Computer computer -> computer.getName()}maxParallelBranches = 10 parallelLimitedBranches(currentJob, agents uuids , maxParallelBranches, false) { String agent uuid ->currentJob.stage( agent "${uuid.trim( ) }") {currentJob.node( agent parallelAgentLabel ) {echo "somevalue"}} } {code}
Add Comment
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesString branchName itemValue = items[i]branches[branchName] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body( itemValue )}}}currentJob.parallel(branches)}{code}You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.
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.181710.1494001199000.9912.1580574783940%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesString itemValue = items[i]branches[ branchName itemValue ] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body(itemValue)}}}currentJob.parallel(branches)}{code}You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.
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.181710.1494001199000.9914.1580574783998%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title
Sam Gleske edited a comment on JENKINS-44085
Re: have a simple way to limit the number of parallel branches that run concurrently
Using my "color" concurrent lock example...{code:java}static def parallelLimitedBranches(CpsScript currentJob,List items,Integer maxConcurrentBranches,Boolean failFast = false,Closure body) {def branches = [:]for(int i = 0; i < items.size(); i++) {int lockId = i % maxConcurrentBranchesString branchName = items[i]branches[branchName] = { ->lock("${currentJob.rawBuild.parent.fullName}-${lockId}") {body()}}}currentJob.parallel(branches)}{code} You're doing something weird with trying to manually select agents... don't do that. Use agent labels and label expressions instead. Rely on Jenkins to select an appropriate agent and only focus on executing your code on said agent.
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.181710.1494001199000.9820.1580574661027%40Atlassian.JIRA.
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Sam Gleske commented on JENKINS-44085 Re: have a simple way to limit the number of parallel branches that run concurrently Using my "color" concurrent lock example... static def parallelLimitedBranches( CpsScript currentJob, Listitems, Integer maxConcurrentBranches, Boolean failFast = false, Closure body) { def branches = [:] for(int i = 0; i < items.size(); i++) { int lockId = i % maxConcurrentBranches String branchName = items[i] branches[branchName] = { -> lock("${currentJob.rawBuild.parent.fullName}-${lockId}") { body() } } } currentJob.parallel(branches) } 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.181710.1494001199000.9773.1580574420916%40Atlassian.JIRA.
[JIRA] (JENKINS-60756) Failed to deploy. java.io.IOException: Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed
Title: Message Title Mykola Lynnyk commented on JENKINS-60756 Re: Failed to deploy. java.io.IOException: Remote call on JNLP4-connect connection from x.x.x.x/x.x.x.x:abcd failed Alse reproducible on MacOS and Linux (CentOS and Ubuntu) slaves with Windows-based Jenkins master. Windows slaves do not seem to be affected. 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.204016.1578984971000.9770.1580574120311%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title
João Salavessa edited a comment on JENKINS-60798
Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Running _kubectl_ with the above file I get the below:{{$ kubectl --kubeconfig=.kube4111259011631954122config version}} {{Client Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}} {{ * Unable to connect to the server: x509: certificate signed by unknown authority * }} If I add " * _insecure-skip-tls-verify: true_ * " to the file it works as expected:{{$ kubectl --kubeconfig=.kube4111259011631954122config_insecure-skip-tls-verify-true version}} {{Client Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}} {{Server Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:11:50Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}}
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-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title
João Salavessa commented on JENKINS-60798
Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Running kubectl with the above file I get the below: $ kubectl --kubeconfig=.kube4111259011631954122config version Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"} Unable to connect to the server: x509: certificate signed by unknown authority If I add "insecure-skip-tls-verify: true" to the file it works as expected: $ kubectl --kubeconfig=.kube4111259011631954122config_insecure-skip-tls-verify-true version }}{{Client Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:11:50Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}
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-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title
João Salavessa edited a comment on JENKINS-60798
Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Running _kubectl_ with the above file I get the below:{{$ kubectl --kubeconfig=.kube4111259011631954122config version}}{{Client Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}}{{Unable to connect to the server: x509: certificate signed by unknown authority}} If I add "_insecure-skip-tls-verify: true_" to the file it works as expected:{{$ kubectl --kubeconfig=.kube4111259011631954122config_insecure-skip-tls-verify-true version}}{{ }}{{ Client Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:20:18Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}}{{Server Version: version.Info \ {Major:"1", Minor:"15", GitVersion:"v1.15.6", GitCommit:"7015f71e75f670eb9e7ebd4b5749639d42e20079", GitTreeState:"clean", BuildDate:"2019-11-13T11:11:50Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}}}
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-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title
João Salavessa commented on JENKINS-60798
Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Tested: job fails with the same message. The "current-context" is now set correctly but the cluster's "insecure-skip-tls-verify" is not present (and I suppose kubectl defaults that to false). Generated file below: $ cat .kube4111259011631954122config --- clusters: - cluster: {{ server: "https://api.internal.k8s.com"}} {{ name: "k8s"}} contexts: - context: {{ cluster: "k8s"}} {{ user: "cluster-admin"}} {{ name: "k8s"}} current-context: "k8s" users: - name: "cluster-admin" {{ user:}} {{ as-user-extra: {}}} {{ password: ".."}} {{ username: "jenkins"}}
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.204126.1579192576000.9761.1580570400197%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA I'm referring to this, I don't know what dashboard do you mean.. Atlassian JIRA Cloud, it's not possible to create a user without an email, so you need to create API token. Then create a global Jenkins credential, where you put Atlassian ID email as username and API token as password. 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.204322.158041457.9759.1580568720051%40Atlassian.JIRA.
[JIRA] (JENKINS-60925) Integration with JIRA
Title: Message Title Radek Antoniuk commented on JENKINS-60925 Re: Integration with JIRA I'm referring to this, I don't know what dashboard do you mean.. Atlassian JIRA Cloud, it's not possible to create a user without an email, so you need to create API token. Then create a global Jenkins credential, where you put Atlassian ID email as username and API token as password. 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.204322.158041457.9757.1580568670202%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" João Salavessa could you try with https://repo.jenkins-ci.org/incrementals/org/jenkinsci/plugins/kubernetes-credentials/0.6.1-rc83.76c66431124a/ ? 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.204126.1579192576000.9755.1580567520277%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated JENKINS-60798 Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe 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.204126.1579192576000.9752.1580567280524%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe started work on JENKINS-60798 Change By: Vincent Latombe Status: Reopened 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.204126.1579192576000.9749.1580567280477%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe updated an issue Jenkins / JENKINS-60798 Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" Change By: Vincent Latombe Component/s: kubernetes-credentials-plugin 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.204126.1579192576000.9743.1580567040305%40Atlassian.JIRA.
[JIRA] (JENKINS-60798) Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1"
Title: Message Title Vincent Latombe commented on JENKINS-60798 Re: Setup Kubernetes CLI (kubectl) error: "FATAL: Failed to run kubectl version 1" I probably read the initial report too quickly. The problem seems to be no current context is set. 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.204126.1579192576000.9746.1580567040344%40Atlassian.JIRA.
[JIRA] (JENKINS-53780) jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins
Title: Message Title Radek Antoniuk closed an issue as Incomplete Closing with timeout from the reporter. Jenkins / JENKINS-53780 jenkins jira plugin failed to instantiate key hudson.plugins.jira.JiraProjectProperty when restart jenkins Change By: Radek Antoniuk Status: Open Closed Resolution: Incomplete 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-53070) Jira-Plugin ignored no_proxy settings
Title: Message Title Radek Antoniuk resolved as Duplicate I believe it was was fixed in JENKINS-51164. Jenkins / JENKINS-53070 Jira-Plugin ignored no_proxy settings Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate 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-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Labels: jenkins plugin 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.204327.1580464056000.9735.1580562060492%40Atlassian.JIRA.
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk resolved as Duplicate Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Status: Open Resolved Resolution: Duplicate 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.204327.1580464056000.9732.1580562060422%40Atlassian.JIRA.
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Radek Antoniuk updated an issue Jenkins / JENKINS-60930 jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Change By: Radek Antoniuk Component/s: jira-issue-updater-plugin Component/s: jira-plugin Component/s: jiratestresultreporter-plugin 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.204327.1580464056000.9729.1580562000246%40Atlassian.JIRA.
[JIRA] (JENKINS-37809) Throttling based on parameters does not work in Pipelines
Title: Message Title Rurui Ye commented on JENKINS-37809 Re: Throttling based on parameters does not work in Pipelines any update on this? I saw it was linked to the workUnitContext issue 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.173942.1472562343000.9719.1580561220294%40Atlassian.JIRA.
[JIRA] (JENKINS-37929) WorkUnitContext.actions does not populate for Pipeline steps
Title: Message Title Rurui Ye commented on JENKINS-37929 Re: WorkUnitContext.actions does not populate for Pipeline steps this is still a blocking issue for jenkins, way does it resolved? 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.174071.147282570.9713.1580560620367%40Atlassian.JIRA.
[JIRA] (JENKINS-37929) WorkUnitContext.actions does not populate for Pipeline steps
Title: Message Title Rurui Ye reopened an issue Jenkins / JENKINS-37929 WorkUnitContext.actions does not populate for Pipeline steps Change By: Rurui Ye Resolution: Not A Defect Status: Resolved Reopened 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.174071.147282570.9716.1580560620451%40Atlassian.JIRA.
[JIRA] (JENKINS-60930) jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found
Title: Message Title Wisen Tanasa commented on JENKINS-60930 Re: jira-trigger-plugin fails to trigger job and throws org.codehaus.jettison.json.JSONException: JSONObject["name"] not found Thanks for raising this issue! I'm closing this one as it's duplicated with JENKINS-53794. 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.204327.1580464056000.9709.1580546820136%40Atlassian.JIRA.
