[JIRA] (JENKINS-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title malcolm crum updated an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Change By: malcolm crum Environment: Jenkins ver. 2.89.3 and 2.89.4, docker commons 1. 9 and 1. 11, docker pipeline 1.15 and 1 . 15. 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google 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-49710) Pipelines run under heavy load sometimes hang running Docker
Title: Message Title malcolm crum created an issue Jenkins / JENKINS-49710 Pipelines run under heavy load sometimes hang running Docker Issue Type: Bug Assignee: Nicolas De Loof Components: docker, pipeline Created: 2018-02-23 09:02 Environment: Jenkins ver. 2.89.3 and 2.89.4, docker commons 1.11, docker pipeline 1.15.1 Priority: Minor Reporter: malcolm crum We have some load tests that run ~50 tests at a time overnight, in loops - so thousands of tests in a night. About 1% of them hang forever and must be manually killed. Jenkins log: Started by upstream project "tools/release-validator" build number 92 originally caused by: Started by timer Obtained Jenkinsfile from git [...] Running in Durability level: MAX_SURVIVABILITY Loading library TestRunner@master Attempting to resolve master from remote references... > git --version # timeout=10 > git ls-remote -h -t [...] # timeout=10 Found match: refs/heads/master revision 4f9f1287a87cedcccbe456d96176084fbfb2500c > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url [...] # timeout=10 Fetching without tags Fetching upstream changes from [...] > git --version # timeout=10 > git fetch --no-tags --progress [...] +refs/heads/*:refs/remotes/origin/* Checking out Revision 4f9f1287a87cedcccbe456d96176084fbfb2500c (master) > git config core.sparsecheckout # timeout=10 > git checkout -f 4f9f1287a87cedcccbe456d96176084fbfb2500c Commit message: "[...]" > git rev-list --no-walk 4f9f1287a87cedcccbe456d96176084fbfb2500c # timeout=10 [Pipeline] node Running on Jenkins
[JIRA] (JENKINS-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
malcolm crum edited a comment on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
[~pjaytycy], I just tested the following code:{code}node() { stage('Build') {println 'I prepare the build for the parallel steps' } stage('Test') { parallel ( "win7-vs2012" : { stage("checkout") { }; stage("build") { }; stage("test") { } }, "win10-vs2015" : { stage("checkout") { }; stage("build") { }; stage("test") { }}, "linux-gcc5" : { stage("checkout") { }; stage("build") { }; stage("test") { } }) }}{ / code}I didn't see the stages in the parallel steps. I don't think that's supported in blue ocean right now . : !Screen Shot 2016-11-21 at 15.41.33.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title malcolm crum updated an issue Jenkins / JENKINS-33185 Visualize parallel steps within a Pipeline Stage Change By: malcolm crum Attachment: Screen Shot 2016-11-21 at 15.41.33.png Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
malcolm crum commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Pieter-Jan Busschaert, I just tested the following code:
node() { stage('Build') { println 'I prepare the build for the parallel steps' } stage('Test') { parallel ( "win7-vs2012" : { stage("checkout") { }; stage("build") { }; stage("test") { } }, "win10-vs2015" : { stage("checkout") { }; stage("build") { }; stage("test") { }}, "linux-gcc5" : { stage("checkout") { }; stage("build") { }; stage("test") { } } ) } } {/code} I didn't see the stages in the parallel steps. I don't think that's supported in blue ocean right now.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-33185) Visualize parallel steps within a Pipeline Stage
Title: Message Title
malcolm crum commented on JENKINS-33185
Re: Visualize parallel steps within a Pipeline Stage
Can you try this instead:
node() {
stage('Build') {
println 'I prepare the build for the parallel steps'
}
stage('Test') {
parallel (
"chrome" : { println 'running tests in chrome' },
"firefox" : { println 'running tests in firefox' },
"edge" : { println 'running tests in edge' }
)
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google 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-34561) Allow to detect different Jenkinsfile filenames
Title: Message Title malcolm crum commented on JENKINS-34561 Re: Allow to detect different Jenkinsfile filenames Any plans on this coming to public Jenkins? I have a Jenkinsfile that runs unit tests and a Jenkinsfile that builds the whole repo, and would like to use the multi-branch plugin with both of them. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-38681) Declarative Pipeline documentation unclear on restrictions
Title: Message Title malcolm crum created an issue Jenkins / JENKINS-38681 Declarative Pipeline documentation unclear on restrictions Issue Type: Improvement Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2016/Oct/04 7:40 AM Environment: Jenkins 2.7.4, pipeline-model-definition 0.2 Labels: pipeline Priority: Minor Reporter: malcolm crum I thought that I could write regular Pipeline within a declarative pipeline stage, and asked about it here: http://stackoverflow.com/questions/39832862/jenkins-cannot-define-variable-in-pipeline-stage After posting it in IRC I was directed to https://github.com/jenkinsci/pipeline-model-definition-plugin/blob/master/SYNTAX.md#declarative-subset-of-groovy which explained the limitations. @abayer suggested I created this Jira ticket for clearer documentation.
[JIRA] (JENKINS-36411) Cannot access environment variable from parameterized plugin in pipeline checkout
Title: Message Title malcolm crum commented on JENKINS-36411 Re: Cannot access environment variable from parameterized plugin in pipeline checkout Thanks, that makes sense. In that case this ticket can be closed. Is there a way to do something similar with Pipeline, then? I.e. click Build With Parameters, enter the name of a branch, and have pipeline checkout that branch and run the jenkinsfile in it? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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-36764) Pipeline: Send notification "Back to normal" state
Title: Message Title malcolm crum closed an issue as Duplicate Bad internet caused a double post. Closing as dupe. Jenkins / JENKINS-36764 Pipeline: Send notification "Back to normal" state Change By: malcolm crum Status: Open Closed Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google 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
[JIRA] (JENKINS-36765) Pipeline: Send notification "Back to normal" state
Title: Message Title
malcolm crum created an issue
Jenkins / JENKINS-36765
Pipeline: Send notification "Back to normal" state
Issue Type:
Improvement
Assignee:
Kurt Madel
Components:
slack-plugin
Created:
2016/Jul/18 2:48 PM
Labels:
pipeline slack
Priority:
Minor
Reporter:
malcolm crum
I understand how to send slack notifications in a Pipeline script on success, or on failure. This is useful for build jobs. For automated tests, a notification on each job is not so useful. Instead, I'd rather be notified when a job fails, or when a job succeeds and the previous job failed. Pre-Pipeline, this was referred to as "Back to normal" I think. I'd like a way to know that a previous build failed. Something like this:
[... test completed successfully]
if (previousBuild.success() == false) {
[send slack message: "Test back to normal]
}
[JIRA] (JENKINS-36764) Pipeline: Send notification "Back to normal" state
Title: Message Title
malcolm crum created an issue
Jenkins / JENKINS-36764
Pipeline: Send notification "Back to normal" state
Issue Type:
Improvement
Assignee:
Kurt Madel
Components:
slack-plugin
Created:
2016/Jul/18 2:46 PM
Labels:
pipeline slack
Priority:
Minor
Reporter:
malcolm crum
I understand how to send slack notifications in a Pipeline script on success, or on failure. This is useful for build jobs. For automated tests, a notification on each job is not so useful. Instead, I'd rather be notified when a job fails, or when a job succeeds and the previous job failed. Pre-Pipeline, this was referred to as "Back to normal" I think. I'd like a way to know that a previous build failed. Something like this:
[... test completed successfully]
if (previousBuild.success() == false) {
[send slack message: "Test back to normal]
}
[JIRA] (JENKINS-36411) Cannot access environment variable from parameterized plugin in pipeline checkout
Title: Message Title malcolm crum created an issue Jenkins / JENKINS-36411 Cannot access environment variable from parameterized plugin in pipeline checkout Issue Type: Bug Assignee: Oleg Nenashev Components: envinject-plugin, workflow-plugin Created: 2016/Jul/04 11:39 AM Environment: Jenkins v1.639, Pipeline 2.2, Environment Injector Plugin 1.92.1 Priority: Minor Reporter: malcolm crum I have a pipeline job set up as such: "This build is parameterized" with a "PRODUCT_CONFIG_BRANCH" string parameter "Pipeline script from SCM" with branch specifier `refs/heads/$PRODUCT_CONFIG_BRANCH` When I run the build, it never seems to read the $PRODUCT_CONFIG_BRANCH variable. If I set the variable in the Properties Content section, it uses this. However, I'd prefer to be able to easily set it every time I click Build.
[JIRA] [workflow-plugin] (JENKINS-35609) GitStep is missing its descriptor with example build
Title: Message Title malcolm crum created an issue Jenkins / JENKINS-35609 GitStep is missing its descriptor with example build Issue Type: Bug Assignee: Jesse Glick Attachments: jenkinsexception.txt Components: workflow-plugin Created: 2016/Jun/10 1:33 PM Environment: Ubuntu 14.04 Labels: exception pipeline Priority: Minor Reporter: malcolm crum I've been testing the waters of Jenkins 2 as I'm interested in the pipeline workthrough but hit a snag. 1. docker run -p 8080:8080 -p 5:5 --name jenkins2 jenkinsci/jenkins:2.8
