[JIRA] (JENKINS-61047) Matrix: allow to use axis values from variable
Title: Message Title Fabian Holler created an issue Jenkins / JENKINS-61047 Matrix: allow to use axis values from variable Issue Type: New Feature Assignee: Andrew Bayer Components: pipeline-model-definition-plugin Created: 2020-02-11 11:09 Priority: Minor Reporter: Fabian Holler Please support to pass in the axis values for matrix builds via a variable. This would enable to calculate the stages to execute during runtime. This is often needed e.g. when in a monorepository certain stages should only be run for applications that changed in a git commit. See also: https://issues.jenkins-ci.org/browse/JENKINS-40986?focusedCommentId=381841=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-381841 Add Comment
[JIRA] (JENKINS-49732) java.util.LinkedHashMap$Entry not serializable in Pipeline
Title: Message Title Fabian Holler commented on JENKINS-49732 Re: java.util.LinkedHashMap$Entry not serializable in Pipeline Ulad Muraveika thanks a lot, that is very useful! 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.188674.1519637279000.12386.1573571340229%40Atlassian.JIRA.
[JIRA] (JENKINS-49732) java.util.LinkedHashMap$Entry not serializable in Pipeline
Title: Message Title Fabian Holler commented on JENKINS-49732 Re: java.util.LinkedHashMap$Entry not serializable in Pipeline Does it mean the workaround using `.each` instead does not work anymore since JENKINS-26481? 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.188674.1519637279000.12347.1573567860379%40Atlassian.JIRA.
[JIRA] (JENKINS-52158) Conditional parallel failfast
Title: Message Title Fabian Holler edited a comment on JENKINS-52158 Re: Conditional parallel failfast We also need this. Passing Allowing to pass `failFast` as a boolean parameter to parallel() would also be an option. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191910.1529948514000.5429.1562666480429%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52158) Conditional parallel failfast
Title: Message Title Fabian Holler commented on JENKINS-52158 Re: Conditional parallel failfast We also need this. Passing `failFast` as a boolean parameter to parallel() would also be an option. 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.191910.1529948514000.5424.1562666340192%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42836) Build parameter not expanded in script path
Title: Message Title Fabian Holler edited a comment on JENKINS-42836 Re: Build parameter not expanded in script path It works only when 'lightweight checkout' is disabled. There is the ticket https://issues.jenkins-ci.org/browse/JENKINS-42971 for the 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-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title
Fabian Holler edited a comment on JENKINS-42971
Re: Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
We have I can confirm that it works if "lightweight checkout" is disabled for git SCM with 'Workflow: Job' 2.32 installed with and Jenkins 2.173 and it does not work . It behaves exactly like in Should the ticket description with GIT as SCM. be closed? ("lightweight checkout" is disabled)
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-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title Fabian Holler updated an issue Jenkins / JENKINS-42971 Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts Change By: Fabian Holler Comment: I can confirm that it works if "lightweight checkout" is disabled for git SCM with 'Workflow: Job' 2.32 and Jenkins 2.173.Should the ticket be closed? 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-42836) Build parameter not expanded in script path
Title: Message Title Fabian Holler commented on JENKINS-42836 Re: Build parameter not expanded in script path There is the ticket https://issues.jenkins-ci.org/browse/JENKINS-42971 for the 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-42971) Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
Title: Message Title
Fabian Holler commented on JENKINS-42971
Re: Pipeline script from SCM does not expand build parameters/env variables for lightweight checkouts
We have 'Workflow: Job' 2.32 installed with Jenkins 2.173 and it does not work. It behaves exactly like in the ticket description with GIT as SCM. ("lightweight checkout" is disabled)
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-42836) Build parameter not expanded in script path
Title: Message Title
Fabian Holler commented on JENKINS-42836
Re: Build parameter not expanded in script path
This does not work for me. I have the "Pipeline: Groovy" Plugin version 2.62 installed. Similiar to described in the ticket I do the following:
Configure my Pipeline job to have a string parameter called branch
In the "Pipeline script from SCM" section, I enter as branch specifier ${branch}
I start the job and as value for the branch parameter develop.
The job fails during checkout with stderr: fatal: Couldn't find remote ref refs/heads/${branch} The variable is not dereferenced.
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-46119) Use the job name in context string
Title: Message Title Fabian Holler reopened an issue Reopening the issue, it's not fixed, the Github Source plugin should support to customize the context string Jenkins / JENKINS-46119 Use the job name in context string Change By: Fabian Holler Resolution: Fixed Status: Closed 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-39106) Unable to use reference repository
Title: Message Title Fabian Holler commented on JENKINS-39106 Re: Unable to use reference repository Marcus Sjölin: Why are you unable to use the reference repository for git checkouts? 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-51542) Git checkout is slower than the command line execution
Title: Message Title Fabian Holler commented on JENKINS-51542 Re: Git checkout is slower than the command line execution We also run into the issue with pipeline scripts + git repositories + a local reference repository. During initial checkout for the pipeline script, the "lightweight checkout" options increases the checkout a lot. With lightweight checkout disabled + reference repo it takes ~5sec. With lightweight checkout enabled + reference repo it takes ~15min. The checkout done via checkout(scm), takes often ~15min despite the reference repository. If I do a "git clone --reference" on the same host, same filesystem it takes ~5sec. Freestyle Git checkouts with a reference repository a fast as expected. 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-55140) Allow to unstash all stashes with a single command
Title: Message Title Fabian Holler created an issue Jenkins / JENKINS-55140 Allow to unstash all stashes with a single command Issue Type: New Feature Assignee: Unassigned Components: workflow-api-plugin Created: 2018-12-12 09:30 Priority: Minor Reporter: Fabian Holler In our pipeline jobs we run ~100 tasks that run on different agents. We are using stash() to collect a result file from each task. At the end of the pipeline we unstash all and summarize the results. Currently it's only possible by calling unstash() for each previous stash with the stash name. It would be handy if it would be possible to either: unstash all stashes with a single command, without having to specify stash names being able to pass a regex to unstash() to match names, this regex could also support to unstash all stashes Add Comment
[JIRA] (JENKINS-46119) Use the job name in context string
Title: Message Title Fabian Holler commented on JENKINS-46119 Re: Use the job name in context string When you run multiple Jenkins job per Github PR you currently end up with having several "continuous-integration/jenkins/" status messages. It's unclear which status refers to which CI job (build, test, etc). Alternatively being able to disable posting the status to github from the plugin at all would help. Then I could post the status myself with a script with the information I want. When I currently do this, I end up with multiple status messages for the same job run in github. 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-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Fabian Holler edited a comment on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects I stumpled upon the same issue.We specified to checkout the git repository that contains the Jenkinsfile in a subdirectory.All jobs failed because Jenkins failed to find the Jenkinsfile in the wrong directory.Either:- it must be ensured that 'Script Path' is relative to the specified checkout subdirectory or- the option should be removed for specifying the repository for the Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Fabian Holler edited a comment on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects I stumpled upon the same issue.We specified to checkout the git repository that contains the Jenkinsfile in a subdirectory.All jobs failed because Jenkins failed to find the Jenkinsfile in the wrong directory.Either:- it must be ensured that 'Script Path' is relative to the specified checkout subdirectory or- the option should be removed for specifying the repository for the Jenkinsfile Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-43052) Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects
Title: Message Title Fabian Holler commented on JENKINS-43052 Re: Disallow "Additional Behaviors > Check out to a sub-directory" for Pipeline projects I stumpled upon the same issue. We specified to checkout the git repository that contains the Jenkinsfile in a subdirectory. All jobs failed because Jenkins failed to find the Jenkinsfile in the wrong directory. Either: it must be ensured that 'Script Path' is relative to the specified checkout subdirectory or the option should be removed Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53032) Support dynamic definition of parallel running stages
Title: Message Title Fabian Holler updated an issue Jenkins / JENKINS-53032 Support dynamic definition of parallel running stages Change By: Fabian Holler Summary: Support dynamic defintion definition of parallel running stages Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-53032) Support dynamic defintion of parallel running stages
Title: Message Title
Fabian Holler updated an issue
Jenkins / JENKINS-53032
Support dynamic defintion of parallel running stages
Change By:
Fabian Holler
We often have the usecase that we need to define stages that we run in parallel during runtime.E.g.: we run a script to determine which application changed in a branch and want to run in parallel for each application stages like Build, Test, Check etc.It seems to be not supported currently. I couldn't find a way to realize it. I tried different variations of the syntax but couldn't make it work.Example of what I would like to do:{code:java}pipeline { agent none stages { stage('Discover Changed Applications') { agent any steps {script { apps = ["app-one", "app-two"] } } } stage('parallel') { steps {script { pstages = [:] for (int i = 0; i < apps.size(); i++) { app = apps[i] pstages[app] = { stages {stage('Build application ') { agent { label 'build' } steps{ sh 'echo build' }}stage('Test application ') { agent { label 'test' } steps{ sh 'echo test' }} } } } parallel(pstages)} } } }}{code}
Add Comment
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)
--
You received this message because you are subscribed to
[JIRA] (JENKINS-53032) Support dynamic defintion of parallel running stages
Title: Message Title
Fabian Holler created an issue
Jenkins / JENKINS-53032
Support dynamic defintion of parallel running stages
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2018-08-14 10:26
Priority:
Minor
Reporter:
Fabian Holler
We often have the usecase that we need to define stages that we run in parallel during runtime. E.g.: we run a script to determine which application changed in a branch and want to run in parallel for each application stages like Build, Test, Check etc. It seems to be not supported currently. I couldn't find a way to realize it. I tried different variations of the syntax but couldn't make it work. Example of what I would like to do:
pipeline {
agent none
stages {
stage('Discover Changed Applications') {
steps {
script {
apps = ["app-one", "app-two"]
}
}
}
stage('parallel') {
steps {
script {
pstages = [:]
for (int i = 0; i < apps.size(); i++) {
app = apps[i]
pstages[app] = {
stages {
stage('Build application ') {
agent { label 'build' }
steps{
sh 'echo build'
}
}
stage('Test application ') {
agent { label 'test' }
steps{
sh 'echo test'
}
}
}
}
}
parallel(pstages)
}
}
}
}
}
