[JIRA] (JENKINS-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Comment: Text after textarea still shows 1pm CEST ; not sure if the feature is not working or if the preview is wrong. (should display 1pm GMT or 2PM CEST) 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Comment: Preview is wrong 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Attachment: l7.png 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Comment: !l7.png! 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-43228) Cron Time Zone is not reflected in preview
Title: Message Title Julien Pivotto commented on JENKINS-43228 Re: Cron Time Zone is not reflected in preview Yes, it is only display and validation. 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-43228) Cron Time Zone is not reflected in preview
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-43228 Cron Time Zone is not reflected in preview Change By: Julien Pivotto Issue Type: Improvement Bug 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto commented on JENKINS-13293 Re: Add cron syntax to set Time Zone https://issues.jenkins-ci.org/browse/JENKINS-43228 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-43228) Cron Time Zone is not reflectod in preview
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-43228 Cron Time Zone is not reflectod in preview Change By: Julien Pivotto It would be nice to have the ability to set what time zone scheduled builds should run in !l7 . png|thumbnail! Common crontab syntax is TZ= Text after textarea still shows 1pm CEST ; not sure if the feature is not working or if the preview is wrong. (should display 1pm GMT 30 11 * * * or 2PM CEST) 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-43228) Cron Time Zone is not reflected in preview
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-43228 Cron Time Zone is not reflected in preview Change By: Julien Pivotto Summary: Cron Time Zone is not reflectod reflected in preview 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-43228) Cron Time Zone is not reflectod in preview
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-43228 Cron Time Zone is not reflectod in preview Change By: Julien Pivotto Attachment: l7.png 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-43228) Cron Time Zone is not reflectod in preview
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-43228 Cron Time Zone is not reflectod in preview Issue Type: Improvement Assignee: Unassigned Attachments: l7.png Components: core Created: 2017/Mar/30 12:05 PM Priority: Major Reporter: Julien Pivotto It would be nice to have the ability to set what time zone scheduled builds should run in. Common crontab syntax is TZ=GMT 30 11 * * * Add Comment
[JIRA] (JENKINS-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto commented on JENKINS-13293 Re: Add cron syntax to set Time Zone Preview is wrong 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto edited a comment on JENKINS-13293 Re: Add cron syntax to set Time Zone Text after textarea still shows 1pm CEST ; not sure if the feature is not working or if the preview is wrong. (should display 1pm GMT or 2PM CEST) 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto reopened an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Resolution: Duplicate Status: Resolved Reopened 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto commented on JENKINS-13293 Re: Add cron syntax to set Time Zone Text after textarea still shows 1pm CEST ; not sure if the feature is not working or if the preview is wrong. 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto commented on JENKINS-13293 Re: Add cron syntax to set Time Zone 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-13293) Add cron syntax to set Time Zone
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-13293 Add cron syntax to set Time Zone Change By: Julien Pivotto Attachment: l7.png 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-32619) Javadoc link displays only documentation frame with no content
Title: Message Title Julien Pivotto commented on JENKINS-32619 Re: Javadoc link displays only documentation frame with no content This is a bug in the configuration. See https://wiki.jenkins-ci.org/display/JENKINS/Configuring+Content+Security+Policy There is nothing to do at the plugin level. The resolution of this bug is that as a workaround we open by default the non-framed page. 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-33059) Changing Gerrit trigger configuration requires restart of Jenkins
Title: Message Title Julien Pivotto commented on JENKINS-33059 Re: Changing Gerrit trigger configuration requires restart of Jenkins We experienced this. Changing the path to SSH key requires a restart, so a downtime. 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-33059) Changing Gerrit trigger configuration requires restart of Jenkins
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-33059 Changing Gerrit trigger configuration requires restart of Jenkins Change By: Julien Pivotto Priority: Major Minor 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-41334) Support parallel execution of stages in Declarative
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-41334
Support parallel execution of stages in Declarative
Change By:
Julien Pivotto
Comment:
Would also love to be able to code those parallel:{code}pipeline { stages {def parallelstages = [:]paralellstages['foo'] = { stage {agent {docker 'hello' } }}parallel parallelstages }}{code}
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-41334) Support parallel execution of stages in Declarative
Title: Message Title
Julien Pivotto edited a comment on JENKINS-41334
Re: Support parallel execution of stages in Declarative
Would also love to be able to code those parallel:{code}pipeline { stages {def parallelstages = [:]paralellstages['foo'] = { stage {agent {docker { ' hello ' } } }}parallel parallelstages }}{code}
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-41334) Support parallel execution of stages in Declarative
Title: Message Title
Julien Pivotto commented on JENKINS-41334
Re: Support parallel execution of stages in Declarative
Would also love to be able to code those parallel:
pipeline {
stages {
def parallelstages = [:]
paralellstages['foo'] = {
stage {
agent {docker {hello} }
}
}
parallel parallelstages
}
}
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-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title Julien Pivotto edited a comment on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized [~jamesdumay] This is pretty bad. I think as an immepdate immediate action we could at least print a warning when some steps are not displayed -- because that will confuse lots of users:«Warning! This pipeline contains steps that can not be displayed in Blue Ocean. Please go to [classic UI] to see all the steps. Read more in [JENKINS-35836].»[JENKINS-35836] is a link to this,[classic UI] is a link to the build "pipeline steps" view. 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-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title Julien Pivotto commented on JENKINS-35836 Re: Steps outside a stage or within a stage but outside a parallel do not get visualized James Dumay This is pretty bad. I think as an immepdate action we could at least print a warning when some steps are not displayed – because that will confuse lots of users: «Warning! This pipeline contains steps that can not be displayed in Blue Ocean. Please go to [classic UI] to see all the steps. Read more in JENKINS-35836.» JENKINS-35836 is a link to this, [classic UI] is a link to the build "pipeline steps" view. 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-22448) Add support for PKCS #8 private keys
Title: Message Title Julien Pivotto commented on JENKINS-22448 Re: Add support for PKCS #8 private keys The problem is that Jenkins expects a RSA key, not a private key Convert /var/lib/jenkins/cert/cci-jenkins.key into a plain RSA key: cp /var/lib/jenkins/cert/cci-jenkins.key /var/lib/jenkins/cert/cci-jenkins.key.full openssl rsa -in /var/lib/jenkins/cert/cci-jenkins.key.full -out /var/lib/jenkins/cert/cci-jenkins.key http://stackoverflow.com/questions/17733536/how-to-convert-a-private-key-to-an-rsa-private-key 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs "(and yes, I know, polling is evil, whenever I can I have triggers configured on modern scm to push jobs, but sometimes it's just not possible, believe me you don't want to know all the why's)" It is not evil. We use polling without schedule (https://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin#GitPlugin-Pushnotificationfromrepository) so it is more pushing than polling, and still have the problem. 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto edited a comment on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs I even tried to add the hudson.plugins.git.extensions.impl.IgnoreNotifyCommit() extention without success.EDIT: confirmed that works it does not work 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto edited a comment on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs [~squalou] A workaround that might work: !wa.png|thumbnail!EDIT: confirmed that it does not work 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-40622) Add the ability to fold/unfold similar actions in build menu
Title: Message Title Julien Pivotto commented on JENKINS-40622 Re: Add the ability to fold/unfold similar actions in build menu Should that touch Hudson.model.Actionable? 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-40622) Add the ability to fold/unfold similar actions in build menu
Title: Message Title Julien Pivotto commented on JENKINS-40622 Re: Add the ability to fold/unfold similar actions in build menu I have published a workaround https://github.com/Inuits/jenkins-global-lib 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-40622) Add the ability to fold/unfold similar actions in build menu
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-40622 Add the ability to fold/unfold similar actions in build menu Issue Type: New Feature Assignee: Mark Waite Attachments: MBS.png, MBS2.png, MBS3.png Components: core, git-plugin Created: 2016/Dec/22 8:43 AM Priority: Minor Reporter: Julien Pivotto When using multiple get repositories (with Pipeline) the build menu is useless. To find the "Waiting for input" button, you need to scroll a lot:I propose that we add the ability to fold similar actions, like in attached screenshots: Add Comment
[JIRA] (JENKINS-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Julien Pivotto commented on JENKINS-38751 Re: Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job Yes, for that I agree. 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-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Julien Pivotto commented on JENKINS-38751 Re: Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job I do not agree. DO is far form being acceptable as default. It misses tons of features (build parameters? folders? slave executors?) and is really (already) too heavy even for moderns laptops and browsers. 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-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto commented on JENKINS-39770 Re: PipelineRunGraph not rendered when there is more that 100 nodes Michael Neale We should at least handle that case and print a message that we can not display more than X nodes (and X can even be smaller, e.g 42!) 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-39968) git checkouts are not pipeline-parallel safe
Title: Message Title Julien Pivotto edited a comment on JENKINS-39968 Re: git checkouts are not pipeline-parallel safe We check out 30 different git repositories.We set the branch to 'master'.The plugins pick the master branch of all the repositories.But,If there is a change in one repo, the plugin will display the change in all the repos that are checkout out at the same time (in other parallel() threads) , even if the commit is not in that repo. 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-39968) git checkouts are not pipeline-parallel safe
Title: Message Title Julien Pivotto commented on JENKINS-39968 Re: git checkouts are not pipeline-parallel safe We check out 30 different git repositories. We set the branch to 'master'. The plugins pick the master branch of all the repositories. But, If there is a change in one repo, the plugin will display the change in all the repos that are checkout out at the same time, even if the commit is not in that repo. 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-39749) Parallel SCM fetches are shown in random order in builds menu
Title: Message Title Julien Pivotto assigned an issue to Mark Waite Jenkins / JENKINS-39749 Parallel SCM fetches are shown in random order in builds menu Change By: Julien Pivotto Assignee: Mark Waite 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-39749) Parallel SCM fetches are shown in random order in builds menu
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39749 Parallel SCM fetches are shown in random order in builds menu Change By: Julien Pivotto Component/s: git-plugin 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-39862) Make stash/unstash work in container.inside
Title: Message Title Julien Pivotto closed an issue as Won't Do I do not need this anymore Jenkins / JENKINS-39862 Make stash/unstash work in container.inside Change By: Julien Pivotto Status: Open Closed Assignee: Julien Pivotto Resolution: Won't Do 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
[JIRA] (JENKINS-37589) Replay link does not show up if Jenkinsfile had a syntax error
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-37589 Replay link does not show up if Jenkinsfile had a syntax error Change By: Julien Pivotto Attachment: PP.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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs Change By: Julien Pivotto Attachment: wa.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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs Change By: Julien Pivotto Attachment: wa.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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs squalou jenkins A workaround that might work: 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39615 Global Pipeline Libraries triggers the 'poll SCM' of jobs Change By: Julien Pivotto Attachment: wa.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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto edited a comment on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs I even tried to add the hudson.plugins.git.extensions.impl.IgnoreNotifyCommit() extention without success. EDIT: that works 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-39615) Global Pipeline Libraries triggers the 'poll SCM' of jobs
Title: Message Title Julien Pivotto commented on JENKINS-39615 Re: Global Pipeline Libraries triggers the 'poll SCM' of jobs I even tried to add the hudson.plugins.git.extensions.impl.IgnoreNotifyCommit() extention without success. 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-38751) Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job
Title: Message Title Julien Pivotto commented on JENKINS-38751 Re: Blue Ocean should provide an "escape" link to get back to a classic view of a Pipeline/job My proposal is to have a "Close Blue Ocean" button, at the same place as the "Open Blue Ocean" button. That would make sense. 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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title Julien Pivotto commented on JENKINS-39818 Re: When using multiple scm repositories, ScmName should be honored PR opened 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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title Julien Pivotto assigned an issue to Julien Pivotto Jenkins / JENKINS-39818 When using multiple scm repositories, ScmName should be honored Change By: Julien Pivotto Assignee: Julien Pivotto 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-39455) Changing build name during run causes a second swim lane to get created
Title: Message Title Julien Pivotto commented on JENKINS-39455 Re: Changing build name during run causes a second swim lane to get created Then it is fixed we are good here 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-39862) Make stash/unstash work in container.inside
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39862 Make stash/unstash work in container.inside Change By: Julien Pivotto Summary: Make stash/unstash work in containter container .inside 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-39968) git checkouts are not pipeline-parallel safe
Title: Message Title Julien Pivotto commented on JENKINS-39968 Re: git checkouts are not pipeline-parallel safe PS: I originally set this as major because of potential side effects of this bug. Maybe it affects all the SCM plugins, or affects other things than changelogs. 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-39968) git checkouts are not pipeline-parallel safe
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39968
git checkouts are not pipeline-parallel safe
Change By:
Julien Pivotto
We have a specific workflow that enables us to discover that bug. However, it could and will probably happen to other people soon.When running scm checkouts in parallels in a Jenkins file, the changes discovered are discovered for *every* git checkout that runs at the same time.In our example, we run checkouts with 8 threads in parallel (background: https://roidelapluie.be/blog/2016/11/18/gitslave-jenkins/ ).One change is displayed in 8 different repositories, the 8 repositories that are checked out at the same time.The next checkouts do not contains the changes, so I guess it is kind of a global variable that is reset after the checkout. {code:java}lock('checkout') {def checkouts = [:]def threads = 8stage('Super Repo') {checkout([$class: 'GitSCM',branches: [[name: branch]],doGenerateSubmoduleConfigurations: false,extensions: [[$class: 'CleanCheckout'], [$class: 'ScmName', name: 'super']],submoduleCfg: [],userRemoteConfigs: [[url: "${gitBaseUrl}/${superRepo}"]]])def repos = readFile('.gitslave')def reposLines = repos.readLines()for (i = 0; i < threads; i++){checkouts["Thread ${i}"] = []}def idx = 0for (line in reposLines) {def repoInfo = line.split(' ')def repoUrl = repoInfo[0]def repoPath = repoInfo[1]def curatedRepoUrl = repoUrl.substring(4, repoUrl.length()-1)def curatedRepoPath = repoPath.substring(1, repoPath.length()-1)echo("Thread ${idx%threads}")checkouts["Thread ${idx%threads}"] << [path: curatedRepoPath, url: "${gitBaseUrl}/${curatedRepoUrl}"]idx++}}stage('GitSlave Repos') {def doCheckouts = [:]for (i = 0; i < threads; i++){def j = idoCheckouts["Thread ${j}"] = {for (co in checkouts["Thread ${j}"]) {retry(3) { checkout([$class: 'GitSCM', branches: [[name: branch]], doGenerateSubmoduleConfigurations: false, extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: co.path], [$class: 'CleanCheckout'], [$class: 'ScmName', name: co.path]], submoduleCfg: [], userRemoteConfigs: [[url: co.url]]])}}}}parallel doCheckouts}{code}
[JIRA] (JENKINS-39968) git checkouts are not pipeline-parallel safe
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39968 git checkouts are not pipeline-parallel safe Change By: Julien Pivotto We have a specific workflow that enables us to discover that bug. However, it could and will probably happen to other people soon.When running scm checkouts in parallels in a Jenkins file, the changes discovered are discovered for *every* git checkout that runs at the same time.In our example, we run checkouts with 8 threads in parallel (background: https://roidelapluie.be/blog/2016/11/18/gitslave-jenkins/ ).One change is displayed in 8 different repositories, the 8 repositories that are checked out at the same time. The next checkouts do not contains the changes, so I guess it is kind of a global variable that is reset after the checkout. 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
[JIRA] (JENKINS-39968) git checkouts are not pipeline-parallel safe
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39968 git checkouts are not pipeline-parallel safe Issue Type: Bug Assignee: Mark Waite Attachments: parallelcheckout.png, parallelcheckout2.png Components: git-plugin Created: 2016/Nov/23 11:25 AM Priority: Major Reporter: Julien Pivotto We have a specific workflow that enables us to discover that bug. However, it could and will probably happen to other people soon. When running scm checkouts in parallels in a Jenkins file, the changes discovered are discovered for every git checkout that runs at the same time. In our example, we run checkouts with 8 threads in parallel (background: https://roidelapluie.be/blog/2016/11/18/gitslave-jenkins/ ). One change is displayed in 8 different repositories, the 8 repositories that are checked out at the same time. Add Comment
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step
Title: Message Title Julien Pivotto commented on JENKINS-37324 Re: We would like a more meaningful description of a step If you want more background and why we clone so much repos – https://roidelapluie.be/blog/2016/11/18/gitslave-jenkins/ 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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title Julien Pivotto edited a comment on JENKINS-35836 Re: Stage graph needs to cope with steps at the stage level at the same time as parallel If you look at my proposal closer: !view-out-of-stage2.png|thumbnail! the horizontal axis means "time", not "stage". It means that groups of steps outside of parallel (or stage) are represented by nodes.If there are 2 x 2 parallel, they are displayed1 32 4and not1234Again, it is about time and no longer about stage.You can identify the stage by the line on top of the nodes, if the stage covers multiple columns. 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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title Julien Pivotto commented on JENKINS-35836 Re: Stage graph needs to cope with steps at the stage level at the same time as parallel If you look at my proposal closer: the horizontal axis means "time", not "stage". It means that groups of steps outside of parallel are represented by nodes. If there are 2 x 2 parallel, they are displayed 1 3 2 4 and not 1 2 3 4 Again, it is about time and no longer about stage. You can identify the stage by the line on top of the nodes, if the stage covers multiple columns. 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-39862) Make stash/unstash work in containter.inside
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39862
Make stash/unstash work in containter.inside
Change By:
Julien Pivotto
It would be great to be able to: {code} stash 'workspace'docker.inside('centos-7') { dir('/tmp'){ unstash 'workspace' }} {code}
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-39862) Make stash/unstash work in containter.inside
Title: Message Title
Julien Pivotto created an issue
Jenkins / JENKINS-39862
Make stash/unstash work in containter.inside
Issue Type:
Improvement
Assignee:
Unassigned
Components:
docker-workflow-plugin, workflow-basic-steps-plugin
Created:
2016/Nov/18 10:08 AM
Priority:
Minor
Reporter:
Julien Pivotto
It would be great to be able to: stash 'workspace' docker.inside('centos-7') { dir('/tmp') { unstash 'workspace' } }
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39850) Blue Ocean should respect build.displayName
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39850 Blue Ocean should respect build.displayName Change By: Julien Pivotto Summary: Blue Ocean does not should respect build.displayName 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-39850) Blue Ocean does not respect build.displayName
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39850 Blue Ocean does not respect build.displayName Change By: Julien Pivotto Issue Type: Bug Improvement 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-39860) messages column in blue ocean should displayif there are more commits
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39860 messages column in blue ocean should displayif there are more commits Issue Type: Improvement Assignee: Unassigned Attachments: message.png Components: blueocean-plugin Created: 2016/Nov/18 9:05 AM Priority: Minor Reporter: Julien Pivotto When there is more than 1 commit, it should be clear in the message column. pic attached. Add Comment
[JIRA] (JENKINS-39848) Impossible to view steps that are outside stages/parallels
Title: Message Title Julien Pivotto closed an issue as Duplicate Jenkins / JENKINS-39848 Impossible to view steps that are outside stages/parallels Change By: Julien Pivotto 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 https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-35836 Stage graph needs to cope with steps at the stage level at the same time as parallel Change By: Julien Pivotto Attachment: view-out-of-stage.png Attachment: view-out-of-stage2.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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-35836 Stage graph needs to cope with steps at the stage level at the same time as parallel Change By: Julien Pivotto Attachment: runtime.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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title
Julien Pivotto edited a comment on JENKINS-35836
Re: Stage graph needs to cope with steps at the stage level at the same time as parallel
!view-out-of-stage.png|thumbnail! Given the following pipeline{code}node {//out of the stagesh ('sleep 10') stage('S1') { // prepare the parallel jobssh ('sleep 20')// run themparallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') }// another onesh ('sleep 10') }// cleanupsh ('sleep 10')}{code}All the steps outstage stage // parallels do not show up in blue ocean.This very annoying. You sometimes want to do some prep in a stage before running parallels. proposal: !view-out-of-stage2.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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-35836 Stage graph needs to cope with steps at the stage level at the same time as parallel Change By: Julien Pivotto Attachment: runtime.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-35836) Stage graph needs to cope with steps at the stage level at the same time as parallel
Title: Message Title
Julien Pivotto commented on JENKINS-35836
Re: Stage graph needs to cope with steps at the stage level at the same time as parallel
Given the following pipeline
node {
//out of the stage
sh ('sleep 10')
stage('S1') {
// prepare the parallel jobs
sh ('sleep 20')
// run them
parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') }
// another one
sh ('sleep 10')
}
// cleanup
sh ('sleep 10')
}
All the steps outstage stage // parallels do not show up in blue ocean. This very annoying. You sometimes want to do some prep in a stage before running parallels.
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-39857) Display steps durations in Blue Ocean
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39857 Display steps durations in Blue Ocean Issue Type: Improvement Assignee: Unassigned Attachments: runtime.png Components: blueocean-plugin Created: 2016/Nov/18 7:33 AM Priority: Minor Reporter: Julien Pivotto Would be great to see Steps duration in Blue Ocean Add Comment
[JIRA] (JENKINS-39847) Misrepresentation of multiple parallels
Title: Message Title Julien Pivotto commented on JENKINS-39847 Re: Misrepresentation of multiple parallels Thanks 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-39851) No duration is shown for stages with the same name
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39851 No duration is shown for stages with the same name Issue Type: Bug Assignee: Sam Van Oort Attachments: SameName.png Components: pipeline-stage-view-plugin Created: 2016/Nov/18 5:34 AM Priority: Minor Reporter: Julien Pivotto When two stages have the same name, the stage view plugin behaves strangely. Add Comment
[JIRA] (JENKINS-39850) Blue Ocean does not respect build.displayName
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39850 Blue Ocean does not respect build.displayName Change By: Julien Pivotto Summary: Blue Ocean does not respect build. displayName 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-39850) Blue Ocean does not respect displayName
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39850 Blue Ocean does not respect displayName Issue Type: Bug Assignee: Unassigned Attachments: RNname.png, RNname2.png Components: blueocean-plugin Created: 2016/Nov/18 5:23 AM Priority: Minor Reporter: Julien Pivotto Code allows you to set: currentBuild.displayName = 'foo' But Blue ocean does not respect it. Attached: classic and BO views. Add Comment
[JIRA] (JENKINS-39848) Impossible to view steps that are outside stages/parallels
Title: Message Title Julien Pivotto commented on JENKINS-39848 Re: Impossible to view steps that are outside stages/parallels Mockup of what I think could be done 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-39848) Impossible to view steps that are outside stages/parallels
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39848 Impossible to view steps that are outside stages/parallels Change By: Julien Pivotto Attachment: view-out-of-stage2.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-39848) Impossible to view steps that are outside stages/parallels
Title: Message Title
Julien Pivotto created an issue
Jenkins / JENKINS-39848
Impossible to view steps that are outside stages/parallels
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
view-out-of-stage.png
Components:
blueocean-plugin
Created:
2016/Nov/18 4:27 AM
Priority:
Major
Reporter:
Julien Pivotto
Given the following pipeline
node {
//out of the stage
sh ('sleep 10')
stage('S1') {
// prepare the parallel jobs
sh ('sleep 20')
// run them
parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') }
// another one
sh ('sleep 10')
}
// cleanup
sh ('sleep 10')
}
All the steps outstage stage // parallels do not show up in blue ocean. This very annoying. You sometimes want to do some prep in a stage before running parallels.
[JIRA] (JENKINS-39847) Misrepresentation of multiple parallels
Title: Message Title Julien Pivotto commented on JENKINS-39847 Re: Misrepresentation of multiple parallels before you ask why we should support single // — this is because the content of // might be autogenerated (by code or anything else) 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-39847) Misrepresentation of multiple parallels
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39847
Misrepresentation of multiple parallels
Change By:
Julien Pivotto
The following pipeline{code}node { stage('S1') { parallel 'S1.0': { sh('sleep 10') }parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') } }stage('S2') { parallel 'S2.0': { sh('sleep 10') }parallel 'S2.1': { sh('sleep 10') } }}{code}Is represented as this: !piprep.png|thumbnail! - S1.0 is not displayed- S2.0 and S2.1 should be under stage 2- S2.0 and S2.1 are not marked as finished Additional note:Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
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-39847) Misrepresentation of multiple parallels
Title: Message Title
Julien Pivotto created an issue
Jenkins / JENKINS-39847
Misrepresentation of multiple parallels
Issue Type:
Bug
Assignee:
Unassigned
Attachments:
piprep.png
Components:
blueocean-plugin
Created:
2016/Nov/18 4:13 AM
Priority:
Minor
Reporter:
Julien Pivotto
The following pipeline
node {
stage('S1') {
parallel 'S1.0': { sh('sleep 10') }
parallel 'S1.1.1': { sh('sleep 10') }, 'S1.1.2': { sh('sleep 10') }
}
stage('S2') {
parallel 'S2.0': { sh('sleep 10') }
parallel 'S2.1': { sh('sleep 10') }
}
}
Is represented as this:
S2.0 and S2.1 should be under stage 2
S2.0 and S2.1 are not marked as finished
Additional note: Made with Pipeline plugin patched with https://github.com/jenkinsci/blueocean-plugin/pull/605
[JIRA] (JENKINS-39843) java.util.EmptyStackException in Blue Ocean UI
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39843
java.util.EmptyStackException in Blue Ocean UI
Change By:
Julien Pivotto
URL is http://dev018.foo:8080/blue/rest/organizations/jenkins/pipelines/foo/9.2-jenkins2/build/runs/363/nodes/{code}javax.servlet.ServletException: java.util.EmptyStackException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at
[JIRA] (JENKINS-39843) java.util.EmptyStackException in Blue Ocean UI
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39843
java.util.EmptyStackException in Blue Ocean UI
Change By:
Julien Pivotto
URL is http://dev018.foo:8080/blue/rest/organizations/jenkins/pipelines/foo/9.2-jenkins2/build/runs/363/nodes/ {code}javax.servlet.ServletException: java.util.EmptyStackException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:812) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1669) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:135) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:206) at
[JIRA] (JENKINS-39843) java.util.EmptyStackException in Blue Ocean UI
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39843 java.util.EmptyStackException in Blue Ocean UI Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/17 10:14 PM Priority: Major Reporter: Julien Pivotto javax.servlet.ServletException: java.util.EmptyStackException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$3.doDispatch(MetaClass.java:197) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:362) at
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title
Julien Pivotto commented on JENKINS-39770
Re: PipelineRunGraph not rendered when there is more that 100 nodes
lock('checkout') {
stage('checkout') {
checkout([$class: 'GitSCM',
branches: [[name: branch]],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'CleanCheckout'], [$class: 'ScmName', name: 'super']],
submoduleCfg: [],
userRemoteConfigs: [[url: "${gitBaseUrl}/${superRepo}"]]])
def repos = readFile('.gitslave')
def reposLines = repos.readLines()
def checkouts = [:]
for (line in reposLines) {
def repoInfo = line.split(' ')
def repoUrl = repoInfo[0]
def repoPath = repoInfo[1]
def curatedRepoUrl = repoUrl.substring(4, repoUrl.length()-1)
def curatedRepoPath = repoPath.substring(1, repoPath.length()-1)
def thisCheckout = {
retry(3) {
checkout([$class: 'GitSCM',
branches: [[name: branch]],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'RelativeTargetDirectory', relativeTargetDir: curatedRepoPath], [$class: 'CleanCheckout'], [$class: 'ScmName', name: curatedRepoPath]],
submoduleCfg: [],
userRemoteConfigs: [[url: "${gitBaseUrl}/${curatedRepoUrl}"]]])
}
checkouts[curatedRepoPath] = thisCheckout
}
parallel checkouts
}
}
That piece of code does a SCM checkout of multiple repos in parallel. That creates a lot of nodes in blue ocean but those nodes are not necessary. Maybe a noNodes {} step around them could do the trick.
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Julien Pivotto commented on JENKINS-37324 Re: We would like a more meaningful description of a step via flow nodes same goes for almost any step – read file from repo – which file? sh – which script? which name? 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-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title
Julien Pivotto commented on JENKINS-37324
Re: We would like a more meaningful description of a step via flow nodes
We clone multiple SCM repositories. They are identified by the ScmName parameter, but we can not see the difference in BO. This is very annoying.
checkout([$class: 'GitSCM',
branches: [[name: branch]],
doGenerateSubmoduleConfigurations: false,
extensions: [[$class: 'CleanCheckout'], [$class: 'ScmName', name: 'super']],
submoduleCfg: [],
userRemoteConfigs: [[url: "${gitBaseUrl}/${superRepo}"]]])
Here is the repo called 'super'
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-37324) We would like a more meaningful description of a step via flow nodes
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-37324 We would like a more meaningful description of a step via flow nodes Change By: Julien Pivotto Attachment: changes.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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39818 When using multiple scm repositories, ScmName should be honored Change By: Julien Pivotto Issue Type: Bug Improvement 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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39818 When using multiple scm repositories, ScmName should be honored Change By: Julien Pivotto Component/s: workflow-scm-step-plugin 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-39818) When using multiple scm repositories, ScmName should be honored
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39818 When using multiple scm repositories, ScmName should be honored Issue Type: Bug Assignee: Mark Waite Attachments: changes.png Components: git-plugin Created: 2016/Nov/17 12:10 PM Priority: Minor Reporter: Julien Pivotto We use multiple git repos. On the change list, we do not see the repo name, even if we set the custom repo name. The changelist should display that name if it is set. Add Comment
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto edited a comment on JENKINS-39770 Re: PipelineRunGraph not rendered when there is more that 100 nodes We have 33 repositoriesWe run three operations on each of them:checkout -- fetch tags -- push new tagPlus other stages (build, publish, doc, release).The total is greater that 100.I think this is because the API /run/x/nodes is paginated ( https://github.com/jenkinsci/blueocean-plugin/blob/f1475e883adbfa8d7aeafc6a4e6aff216cfc/blueocean-rest/src/main/java/io/jenkins/blueocean/rest/pageable/PagedResponse.java#L31 )I do not CARE about SEEING the 100 bullets. Actually that would be horrible. But having that parallelism decreases the duration from 60s to 5s. 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-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto commented on JENKINS-39770 Re: PipelineRunGraph not rendered when there is more that 100 nodes We have 33 repositories We run three operations on each of them: checkout – fetch tags – push new tag Plus other stages (build, publish, doc, release). The total is greater that 100. I think this is because the API /run/x/nodes is paginated ( https://github.com/jenkinsci/blueocean-plugin/blob/f1475e883adbfa8d7aeafc6a4e6aff216cfc/blueocean-rest/src/main/java/io/jenkins/blueocean/rest/pageable/PagedResponse.java#L31 ) I do not CARE about SEEING the 100 bullets. Actually that would be horrible. But having that increases the speed to 60s to 5s. 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-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto edited a comment on JENKINS-39770 Re: PipelineRunGraph not rendered when there is more that 100 nodes We have 33 repositoriesWe run three operations on each of them:checkout -- fetch tags -- push new tagPlus other stages (build, publish, doc, release).The total is greater that 100.I think this is because the API /run/x/nodes is paginated ( https://github.com/jenkinsci/blueocean-plugin/blob/f1475e883adbfa8d7aeafc6a4e6aff216cfc/blueocean-rest/src/main/java/io/jenkins/blueocean/rest/pageable/PagedResponse.java#L31 )I do not CARE about SEEING the 100 bullets. Actually that would be horrible. But having that increases decreases the speed to duration from 60s to 5s. 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-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto commented on JENKINS-39770 Re: PipelineRunGraph not rendered when there is more that 100 nodes I think the scope of this ticket should be: raise a correct error messages if there are more than 100 nodes to display 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-39770) PipelineRunGraph not rendered
Title: Message Title Julien Pivotto commented on JENKINS-39770 Re: PipelineRunGraph not rendered Works without parallel. 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-39770) PipelineRunGraph not rendered when there is more that 100 nodes
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered when there is more that 100 nodes Change By: Julien Pivotto Summary: PipelineRunGraph not rendered when there is more that 100 nodes 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-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto edited a comment on JENKINS-39770
Re: PipelineRunGraph not rendered
HOW TO REPREDUCEPipeline:{code} def max=100 stage('test'){node {checkouts = [:]for (i=0; i< 100 max ; i++) {def x = icheckouts["foo${x}"] = {checkout([$class: 'GitSCM', branches: [[name: '*/master']],doGenerateSubmoduleConfigurations: false, extensions:[[$class: 'RelativeTargetDirectory', relativeTargetDir: "foo${x}"],[$class: 'ScmName', name: "foo${x}"]],submoduleCfg: [], userRemoteConfigs: [[url: "/tmp/foo${x}"]]]) }}parallel checkouts }}{code}Shell:{code}cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in $(seq 0 150); do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done{code} Works with def max=98
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-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto commented on JENKINS-39770
Re: PipelineRunGraph not rendered
HOW TO REPREDUCE Pipeline:
stage('test'){
node {
checkouts = [:]
for (i=0; i<100; i++) {
def x = i
checkouts["foo${x}"] = {
checkout([$class: 'GitSCM', branches: [[name: '*/master']],
doGenerateSubmoduleConfigurations: false, extensions:
[[$class: 'RelativeTargetDirectory', relativeTargetDir: "foo${x}"],
[$class: 'ScmName', name: "foo${x}"]],
submoduleCfg: [], userRemoteConfigs: [[url: "/tmp/foo${x}"]]])
}
}
parallel checkouts
}
}
Shell:
cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in $(seq 0 150); do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done
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
[JIRA] (JENKINS-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Julien Pivotto commented on JENKINS-39768 Re: Multiple checkout in Pipeline but only one seen in git data Mark Waite here you go. 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.
