[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
Added lockable-resources-plugin as a potential dependency since a semaphore step could be implemented. Semaphore-like behavior with lock step Can be achieved by calculating lock names using modulo operator to cycle through an integer. Here's an example using rainbow colors.
int concurrency = 3
List colors = ['red', 'orange', 'yellow', 'green', 'blue', 'indigo', 'violet']
Map tasks = [failFast: false]
for(int i=0; iString color = colors[i]
int lock_id = i % concurrency
tasks["Code ${color}"] = { ->
stage("Code ${color}") {
lock("color-lock-${lock_id}") {
echo "This color is ${color}"
sleep 30
}
}
}
}
// execute the tasks in parallel with concurrency limits
stage("Rainbow") {
parallel(tasks)
}
The above code will execute 7 stages in parallel; however it will not run more than 3 concurrently. The above will create custom locks:
color-lock-0
color-lock-1
color-lock-2
All concurrent tasks will race for one of the three locks. It's not perfectly efficient (certainly not as efficient as a real semaphore) and there are some limitations. Limitations with this workaround Your pipeline will take as long as your slowest locks. So if you unfortunately have several long running jobs racing for the same lock (e.g. color-lock-1), then your pipeline could be longer than if it were a proper semaphore. Example scenario with the three locks:
color-lock-0 takes 20 seconds to cycle through all jobs.
color-lock-1 takes 30 minutes to cycle through all jobs.
color-lock-2 takes 2 minutes to cycle through all jobs.
Then your job will take 30 minutes to run... where as with a true semaphore it would have been much faster because the longer running jobs would take the next available lock in the semaphore rather than be blocked.
Add Comment
[JIRA] (JENKINS-44085) have a simple way to limit the number of parallel branches that run concurrently
Title: Message Title Sam Gleske updated an issue Jenkins / JENKINS-44085 have a simple way to limit the number of parallel branches that run concurrently Change By: Sam Gleske Component/s: lockable-resources-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.181710.1494001199000.5839.1574567701530%40Atlassian.JIRA.
[JIRA] (JENKINS-60257) Jenkins配置gitlab的API token时出现未知错误
Title: Message Title Zbynek Konecny moved an issue Jenkins / JENKINS-60257 Jenkins配置gitlab的API token时出现未知错误 Change By: Zbynek Konecny Project: Jenkins Events Key: EVENTS JENKINS - 53 60257 Issue Type: Task Bug Workflow: EVENTS: Simple Issue Tracking Workflow JNJira + In-Review Status: To Do Open Component/s: other Component/s: other Due Date: 10/Nov/20 Add Comment
[JIRA] (JENKINS-60256) Selecting Frame on Jenkins Server Gives a.addEventListener is not a function error message
Title: Message Title Zbynek Konecny moved an issue Jenkins / JENKINS-60256 Selecting Frame on Jenkins Server Gives a.addEventListener is not a function error message Change By: Zbynek Konecny Project: Jenkins Events Key: EVENTS JENKINS - 54 60256 Workflow: EVENTS: Simple Issue Tracking Workflow JNJira + In-Review Status: To Do Open Component/s: core Component/s: other Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Andrey Babushkin commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head I think this is happening due to our pipeline durability settings override - we've set it to MAX_PERFORMANCE. Therefore all pipelines die when Jenkins master dies 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.196374.1545361815000.5797.1574540760603%40Atlassian.JIRA.
[JIRA] (JENKINS-60255) EC2 plugin creating extra unused EC2 instances
Title: Message Title John Jeffers created an issue Jenkins / JENKINS-60255 EC2 plugin creating extra unused EC2 instances Issue Type: Bug Assignee: FABRIZIO MANFREDI Components: ec2-plugin Created: 2019-11-23 20:22 Environment: Jenkins version 2.190.3, running in k8s using official docker image ec2 plugin version 1.46.1 Priority: Critical Reporter: John Jeffers The EC2 plugin creates extra EC2 instances that it does not end up using. For instance, right now there are 5 EC2 instances launched by the plugin, but only 2 of those are registered in Jenkins as build executors. If I terminate the unused instances, the plugin launches new ones. Is there any way to fix this? Add Comment
[JIRA] (JENKINS-60254) Pipeline NodeJS dev-test-prod
Title: Message Title
Zbynek Konecny commented on JENKINS-60254
Re: Pipeline NodeJS dev-test-prod
Doesn't look like a bug, just a problem with pipeline syntax. Note that $ in pipeline (groovy) is used for expanding groovy variables, so "${npm bin}" is not valid. You can either of the following instead: sh "echo \$(npm bin)" sh 'echo $(npm bin)' (these call echo command in your shell and hence $ is interpreted by shell).
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.201182.1565289374000.5791.1574540520294%40Atlassian.JIRA.
[JIRA] (JENKINS-60254) Pipeline NodeJS dev-test-prod
Title: Message Title Zbynek Konecny closed an issue as Not A Defect Jenkins / JENKINS-60254 Pipeline NodeJS dev-test-prod Change By: Zbynek Konecny Status: Open Closed Resolution: Not A Defect 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.201182.1565289374000.5793.1574540520335%40Atlassian.JIRA.
[JIRA] (JENKINS-60254) Pipeline NodeJS dev-test-prod
Title: Message Title Zbynek Konecny moved an issue Jenkins / JENKINS-60254 Pipeline NodeJS dev-test-prod Change By: Zbynek Konecny Project: Jenkins Events Key: EVENTS JENKINS - 56 60254 Workflow: EVENTS: Simple Issue Tracking Workflow JNJira + In-Review Status: To Do Open Component/s: other Component/s: other Due Date: 7/Aug/19 Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
[JIRA] (JENKINS-60253) Validate Pipeline Maven Plugin with PostgreSQL 12
Title: Message Title Cyrille Le Clerc started work on JENKINS-60253 Change By: Cyrille Le Clerc Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203242.1574527644000.5784.1574527680542%40Atlassian.JIRA.
[JIRA] (JENKINS-60253) Validate Pipeline Maven Plugin with PostgreSQL 12
Title: Message Title Cyrille Le Clerc updated JENKINS-60253 Jenkins / JENKINS-60253 Validate Pipeline Maven Plugin with PostgreSQL 12 Change By: Cyrille Le Clerc 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.203242.1574527644000.5785.1574527680572%40Atlassian.JIRA.
[JIRA] (JENKINS-60253) Validate Pipeline Maven Plugin with PostgreSQL 12
Title: Message Title Cyrille Le Clerc closed an issue as Fixed Jenkins / JENKINS-60253 Validate Pipeline Maven Plugin with PostgreSQL 12 Change By: Cyrille Le Clerc Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203242.1574527644000.5787.1574527680682%40Atlassian.JIRA.
[JIRA] (JENKINS-60253) Validate Pipeline Maven Plugin with PostgreSQL 12
Title: Message Title Cyrille Le Clerc updated JENKINS-60253 Jenkins / JENKINS-60253 Validate Pipeline Maven Plugin with PostgreSQL 12 Change By: Cyrille Le Clerc Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.203242.1574527644000.5786.1574527680598%40Atlassian.JIRA.
[JIRA] (JENKINS-60253) Validate Pipeline Maven Plugin with PostgreSQL 12
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-60253 Validate Pipeline Maven Plugin with PostgreSQL 12 Issue Type: Improvement Assignee: Cyrille Le Clerc Components: pipeline-maven-plugin Created: 2019-11-23 16:47 Priority: Minor Reporter: Cyrille Le Clerc Pipeline Maven Plugin 3.8.2 successfully tested with PostgreSQL 12.1 for MacOS Tested both on an installation from scratch and upgrading a Pipeline Maven Plugin database from PostgreSQL 11 to PostgreSQL 12.1. Add Comment
[JIRA] (JENKINS-60252) 100% CPU Utilization on Jenkins Master running on ECS
Title: Message Title Zbynek Konecny moved an issue Jenkins / JENKINS-60252 100% CPU Utilization on Jenkins Master running on ECS Change By: Zbynek Konecny Project: Infrastructure Jenkins Key: INFRA JENKINS - 2343 60252 Workflow: classic default workflow JNJira + In-Review Component/s: docker Component/s: docker Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this
