[JIRA] (JENKINS-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Kevin Lannen commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library This functionality is available with the scripted syntax if that's what you are trying to do though. 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-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title Kevin Lannen commented on JENKINS-49662 Re: Ability to create custom stages in parallel blocks in pipeline shared library Yes, there's a very good reason why the code won't work. I wrote that code to demonstrate what how I would like the API to work as a feature request, not as code that currently works hence why this feature request exists. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen edited a comment on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan ++ We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan ++We have used both JGit and the cli git and both have this issue. We would prefer to use cli git as it seems to be more reliable in other areas but it seemed to hang more during branch indexing then JGit does. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan There definitely needs to be some sort of timeout here, this happens less now since we have backed off our polling interval to avoid it (not ideal). We have been able to link all the times that these have occurred to connection issues with our Bitbucket server. A connection error should not require a restart of Jenkins though 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen updated an issue Jenkins / JENKINS-48933 Unstoppable Multibranch Pipeline Scan Change By: Kevin Lannen Component/s: git-plugin 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan This seems similar to this issue: https://issues.jenkins-ci.org/browse/JENKINS-32767 We are using Bitbucket for our source control. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen commented on JENKINS-48933 Re: Unstoppable Multibranch Pipeline Scan We are running into this same issue, This is a major issue for us since restarting Jenkins is not a valid workaround during the workday. 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-48933) Unstoppable Multibranch Pipeline Scan
Title: Message Title Kevin Lannen updated an issue Jenkins / JENKINS-48933 Unstoppable Multibranch Pipeline Scan Change By: Kevin Lannen Priority: Minor Major 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-43820) Stage name must be a string literal
Title: Message Title Kevin Lannen commented on JENKINS-43820 Re: Stage name must be a string literal This is a serious blocker to using the declarative syntax to define a pipeline in a shared library. What is the "conscious design decision" that led to this? From my perspective there is no downside to allowing this flexibility. 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-49662) Ability to create custom stages in parallel blocks in pipeline shared library
Title: Message Title
Kevin Lannen created an issue
Jenkins / JENKINS-49662
Ability to create custom stages in parallel blocks in pipeline shared library
Issue Type:
New Feature
Assignee:
Unassigned
Components:
pipeline
Created:
2018-02-20 22:46
Priority:
Minor
Reporter:
Kevin Lannen
I would like to be able to easily run the same steps across multiple nodes using the declarative pipeline and a shared library. This does not currently seem to be possible since only custom steps can be created in shared libraries. Example jenkinsfile:
pipeline {
agent any
stages {
stage('Build everywhere') {
runOnAllPlatforms {
sh 'doing build things'
}
}
}
}
Example shared library vars/runOnAllPlatforms.groovy:
def call(Closure body) {
parallel {
stage('RHEL') {
agent {
node { label 'rhel7' }
}
steps {
body()
}
stage('Apple') {
agent {
node { label 'apple' }
}
steps {
body()
}
steps {
body()
}
}
}
