[JIRA] (JENKINS-39682) Generated Mutlibranch Pipeline Job does not index branches
Title: Message Title Daniel Spilker assigned an issue to Unassigned Jenkins / JENKINS-39682 Generated Mutlibranch Pipeline Job does not index branches Change By: Daniel Spilker Assignee: Daniel Spilker 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-39682) Generated Mutlibranch Pipeline Job does not index branches
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-39682 Generated Mutlibranch Pipeline Job does not index branches Job DSL uses standard Jenkins API to create jobs, specifically Jenkins#createProjectFromXML(String name, InputStream xml). If the job does not trigger after creating from Job DSL, it will probably also not trigger after creating through CLI or REST API which use the same API internally. This should not be fixed at the consumer side of the API. It needs either to be fixed in core or in Multibranch Pipeline plugin. Change By: Daniel Spilker Component/s: core Component/s: workflow-multibranch-plugin Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38920) JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned
Title: Message Title Daniel Spilker closed an issue as Fixed Fixed in 0.19.0. Jenkins / JENKINS-38920 JPI plugin Manifest lacks Plugin-Class attribute when Gradle project was previously cleaned Change By: Daniel Spilker Status: Resolved Closed 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-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Julien Pivotto created an issue Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data Issue Type: Bug Assignee: Mark Waite Attachments: multiscm3.png, multiscm4.png, multiscm5.png Components: git-plugin, pipeline, workflow-scm-step-plugin Created: 2016/Nov/16 8:14 AM Priority: Major Reporter: Julien Pivotto When using multiple SCM, only one is seen in "git data"; only one is seen in the pipeline stage view as well. See screenshots. Add Comment
[JIRA] (JENKINS-39164) CommandInterpreter return value fix: causes incompatibility with Env-inject plugin in Jenkins v2.26
Title: Message Title Daniel Beck resolved as Cannot Reproduce Resolving as Cannot Reproduce for now, reopen when you can provide complete and unambiguous steps to reproduce this issue on a clean Jenkins installation. Jenkins / JENKINS-39164 CommandInterpreter return value fix: causes incompatibility with Env-inject plugin in Jenkins v2.26 Change By: Daniel Beck Status: Open Resolved Resolution: Cannot Reproduce 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
[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 There shoild be commits in all the builds; only 9.2-jenkins2-177 has commits in the first repo. Other build have commits in other repositories; that is not shown. Shows that we have multiple repositories. Clicking on any repo points to that page. Always about the first 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-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Julien Pivotto edited a comment on JENKINS-39768 Re: Multiple checkout in Pipeline but only one seen in git data !multiscm3.png|thumbnail! There shoild should be commits in all the builds; only 9.2-jenkins2-177 has commits in the first repo. Other build have commits in other repositories; that is not shown. !multiscm4.png|thumbnail! Shows that we have multiple repositories. !multiscm5.png|thumbnail! Clicking on any repo points to that page. Always about the first 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-37500) scm-syn-configurtaion issues with multi branch project
Title: Message Title Marco Lenzo commented on JENKINS-37500 Re: scm-syn-configurtaion issues with multi branch project We are experiencing the same issue which is a blocker to us since the plugin becomes unusable once it enters this state. 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-17129) Gradle plugin does not support HudsonTestCase
Title: Message Title Daniel Spilker closed an issue as Fixed Sergey Kadaner Your problem is unreleated to this bug report. The original report was about a `NoClassDefFoundError` and you got a `FileSystemException` which is completely different. Do not reopen unrelated bug reports. Your problem has been reported as JENKINS-4409 and has been fixed in Jenkins 1.596.3. You just need to update your core version. Jenkins / JENKINS-17129 Gradle plugin does not support HudsonTestCase Change By: Daniel Spilker Status: Reopened Closed Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-28293) Display more information about Pipeline steps
Title: Message Title Attila Strba commented on JENKINS-28293 Re: Display more information about Pipeline steps Sam Van Oort Thank you for the comprehensive answer. The JENKINS-26522 looks quite good and is exactly what would help us. I still wonder thet currently there was no need for more detail for analysis. Prehaps our pipeline job is too complex, but it is due to the complexity of our project. If there is way to drive this forward or anyway I could help just let me know... I see the future of jenkins in pipelines but BlueOcean to come is yet too far away for us 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-35401) Need equivalent to mvn release:prepare
Title: Message Title Daniel Spilker updated an issue Jenkins / JENKINS-35401 Need equivalent to mvn release:prepare There are several plugins which provide this feature. Rather than adding a release task to the Gradle JPI plugin, we should just describe how to use one of the existing plugins to cut a release. Change By: Daniel Spilker Issue Type: Bug New Feature 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-39765) freeStyleJob should support an update argument to specify if you want or not override
Title: Message Title jlpinardon commented on JENKINS-39765 Re: freeStyleJob should support an update argument to specify if you want or not override I think that the point here should not to control job's overriding overwriting in every cases, but only if one of the jobs (re)generated within a DSL script has the same name as the seed job. In other words,it should only control the case where the "tryDSL" seed job's DSL scripts tries to create a job named "tryDSL" in the same folder than the seed job. It is actually a security option, which should be activated by default and lead to a seed job failure if the case is encountered. 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-39769) update to latest config-file-provider
Title: Message Title Dominik Bartholdi created an issue Jenkins / JENKINS-39769 update to latest config-file-provider Issue Type: Task Assignee: Daniel Spilker Components: job-dsl-plugin Created: 2016/Nov/16 9:07 AM Priority: Minor Reporter: Dominik Bartholdi The config-file-provider plugin is getting a large refactoring to support configuration files on folder level (integration with folder-plugin). Unfortunate some java API changes could not be done in a backward compatible way... (but data is migrated!) The current beta version of the config-file-provider plugin is available on the experimental update center. I prepared all the changes for the job-dsl-plugin in a PR... Add Comment
[JIRA] (JENKINS-37500) scm-syn-configurtaion issues with multi branch project
Title: Message Title Marco Nenciarini updated an issue Jenkins / JENKINS-37500 scm-syn-configurtaion issues with multi branch project Change By: Marco Nenciarini Priority: Minor Major 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 created an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/16 9:11 AM Priority: Major Reporter: Julien Pivotto Using the Bule Ocean plugin, I see the following traceback: error rendering PipelineRunGraph TypeError: child is undefined Stack trace: render/selectedStage//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10705:25 render/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40 render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68260:27 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68283:29 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67825:25 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67721:16 [445]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:74734:18 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67834:18 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67721:16 [445]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:74734:18 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67834:18 [394]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67721:16 [445]//dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39770
PipelineRunGraph not rendered
Change By:
Julien Pivotto
Using the Bule Ocean plugin, I see the following traceback:{code}error rendering PipelineRunGraph TypeError: child is undefinedStack trace:render/selectedStagerender/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33[394][394][394][394][445][394][394][445][394][394][445]mountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72953:16[471]batchedMountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72975:3[416]batchedUpdates@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75831:3[433][433][433]_renderExtension@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7547:17_renderAllExtensions@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7529:25componentDidUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7447:13[361][444][471][471][471][453][453][471][471][416]enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75934:5enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75542:3[452][390]_onScrollHandler@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:12224:17{code}Using Jenkins 2.30 ; Blue Ocean beta 12. Disclaimer: I run stages in parallel.
Add Comment
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39770
PipelineRunGraph not rendered
Change By:
Julien Pivotto
Using the Bule Ocean plugin, I see the following traceback:{code}error rendering PipelineRunGraph TypeError: child is undefinedStack trace:render/selectedStagerender/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33[394][394][394][394][445][394][394][445][394][394][445]mountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72953:16[471]batchedMountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72975:3[416]batchedUpdates@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75831:3[433][433][433]_renderExtension@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7547:17_renderAllExtensions@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7529:25componentDidUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7447:13[361][444][471][471][471][453][453][471][471][416]enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75934:5enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75542:3[452][390]_onScrollHandler@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:12224:17{code} Using Jenkins 2.30 ; Blue Ocean beta 12.
Add Comment
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39770
PipelineRunGraph not rendered
Change By:
Julien Pivotto
Using the Bule Blue Ocean plugin, I see the following traceback:{code}error rendering PipelineRunGraph TypeError: child is undefinedStack trace:render/selectedStagerender/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33[394][394][394][394][445][394][394][445][394][394][445]mountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72953:16[471]batchedMountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72975:3[416]batchedUpdates@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75831:3[433][433][433]_renderExtension@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7547:17_renderAllExtensions@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7529:25componentDidUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7447:13[361][444][471][471][471][453][453][471][471][416]enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75934:5enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75542:3[452][390]_onScrollHandler@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:12224:17{code}Using Jenkins 2.30 ; Blue Ocean beta 12.Disclaimer: I run stages in parallel.
Add Comment
[JIRA] (JENKINS-39418) Throws error when scm syncing
Title: Message Title Marco Nenciarini commented on JENKINS-39418 Re: Throws error when scm syncing The pull request attached to JENKINS-37500 should solve this issue: https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49 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-39769) update to latest config-file-provider
Title: Message Title Dominik Bartholdi commented on JENKINS-39769 Re: update to latest config-file-provider PR is here: https://github.com/jenkinsci/job-dsl-plugin/pull/951 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-35232) Gradle JPI and JenkinsRule loading issues
Title: Message Title Daniel Spilker commented on JENKINS-35232 Re: Gradle JPI and JenkinsRule loading issues Sorry for answering late. I just clone your jpi-plugin-test repo and it builds successfully with `./gradlew build` on my machine. This could be related to JENKINS-35412. When specifying dependencies with an extension (@jar in this case), Gradle does not resolve any transitive dependencies. So currently you need to specify each and every transitive plugin dependency. I would close this as duplicate of JENKINS-35412 because JENKINS-35412 describes the underlying problem. Or is there another problem with your build? 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-38139) scm-sync fails when multibranch pipeline job is automatically deleted
Title: Message Title Marco Nenciarini commented on JENKINS-38139 Re: scm-sync fails when multibranch pipeline job is automatically deleted This is a duplicate of JENKINS-37500 . The pull request https://github.com/jenkinsci/scm-sync-configuration-plugin/pull/49 should solve this issue. 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-39728 Jenkins not able to clone private bitbucket repo Change By: Stephen Connolly Component/s: credentials-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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Stephen Connolly assigned an issue to Mark Waite Jenkins / JENKINS-39728 Jenkins not able to clone private bitbucket repo Change By: Stephen Connolly Assignee: Stephen Connolly 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-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39770
PipelineRunGraph not rendered
Change By:
Julien Pivotto
Using the Blue Ocean plugin, I see the following traceback: FIREFOX: {code}error rendering PipelineRunGraph TypeError: child is undefinedStack trace:render/selectedStagerender/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33[394][394][394][394][445][394][394][445][394][394][445]mountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72953:16[471]batchedMountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72975:3[416]batchedUpdates@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75831:3[433][433][433]_renderExtension@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7547:17_renderAllExtensions@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7529:25componentDidUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7447:13[361][444][471][471][471][453][453][471][471][416]enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75934:5enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75542:3[452][390]_onScrollHandler@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:12224:17{code} CHROMIUM:{code}error rendering PipelineRunGraph TypeError: Cannot read property 'id' of undefinedat http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10705:37at Array.filter (native)at http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:54at Array.filter (native)at PipelineRunGraph.render (http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:44)at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68260:32)at ReactCompositeComponentWrapper._renderValidatedComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68283:34)at ReactCompositeComponentWrapper.performInitialMount (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67825:30)at ReactCompositeComponentWrapper.mountComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67721:21)at Object.mountComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:74734:35){code} Using Jenkins
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered
Title: Message Title
Julien Pivotto updated an issue
Jenkins / JENKINS-39770
PipelineRunGraph not rendered
Change By:
Julien Pivotto
Using the Blue Ocean plugin, I see the following traceback:FIREFOX:{code}error rendering PipelineRunGraph TypeError: child is undefinedStack trace:render/selectedStagerender/selectedStage<@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:40render@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:33[394][394][394][394][445][394][394][445][394][394][445]mountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72953:16[471]batchedMountComponentIntoNode@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:72975:3[416]batchedUpdates@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75831:3[433][433][433]_renderExtension@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7547:17_renderAllExtensions@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7529:25componentDidUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:7447:13[361][444][471][471][471][453][453][471][471][416]enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75934:5enqueueUpdate@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:75542:3[452][390]_onScrollHandler@http://dev018.ant.nmhn.lab:8080/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:12224:17{code}CHROMIUM:{code}error rendering PipelineRunGraph TypeError: Cannot read property 'id' of undefinedat http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10705:37at Array.filter (native)at http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10704:54at Array.filter (native)at PipelineRunGraph.render (http://127.0.0.1:15000/adjuncts/5b1d2830/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:10701:44)at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68260:32)at ReactCompositeComponentWrapper._renderValidatedComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:68283:34)at ReactCompositeComponentWrapper.performInitialMount (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67825:30)at ReactCompositeComponentWrapper.mountComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:67721:21)at Object.mountComponent (http://127.0.0.1:15000/adjuncts/5b1d2830/io/jenkins/blueocean/blueocean.js:74734:35){code}Using Jenkins 2.30
[JIRA] (JENKINS-37072) Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null"
Title: Message Title Magnus Lindstedt commented on JENKINS-37072 Re: Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null" I agree, we have the same problem: "FATAL: Log statements out of sync: current test case was null" This occurs also on XCode plugin 1.4.9 and it doesn't seem fixed on newer versions 1.4.11 There seems to be a person who has made his own fork to solve the problem when the message says: ”DEBUG: Log statements out of sync”, i.e DEBUG instead of FATAL... http://stackoverflow.com/a/15725083 I haven't tested this though, but anyone here on Jenkins support can maybe take a look at the solution. 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-24660) Jenkins master node crashes with SIGSEGV
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce No need to keep a two year old one-time exception open, feel free to reopen if it does reproduce with current versions. Jenkins / JENKINS-24660 Jenkins master node crashes with SIGSEGV Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce 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+
[JIRA] (JENKINS-21937) build broken
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-21937 build broken Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce 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-39771) Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic
Title: Message Title Enrique Sanchez created an issue Jenkins / JENKINS-39771 Failed to load org.jenkinsci.plugins.orgfolder.github.MainLogic Issue Type: Bug Assignee: Matthew DeTullio Attachments: jenkins-error.log Components: multi-branch-project-plugin Created: 2016/Nov/16 9:58 AM Environment: 2.30 Labels: exception pipeline WorkflowMultiBranchProject Priority: Blocker Reporter: Enrique Sanchez After the update I cannot run Jenkins because I got this kind of error in the logs: Add Comment
[JIRA] (JENKINS-37072) Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null"
Title: Message Title Magnus Lindstedt commented on JENKINS-37072 Re: Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null" The problem for us seemed to be that we have two threads doing prints. First we have a logging framework called SwiftyBeaver that printed on background thread, but some other prints in the unittests were done on then main thread and this seems to cause the problem. So by instead logging all prints to a file, instead of printing, we managed to get away from this bug. 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-17277) Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null”
Title: Message Title Magnus Lindstedt commented on JENKINS-17277 Re: Jenkins iOS job broken because “FATAL: Log statements out of sync: current test case was null” My bad... sorry, for adding comment on a closed issue... The discussion seems to be on a new thread nowadays, since the problem still occurs, where we've found a workaround: https://issues.jenkins-ci.org/browse/JENKINS-37072 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-37072) Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null"
Title: Message Title Magnus Lindstedt edited a comment on JENKINS-37072 Re: Jenkins iOS Build Error - FATAL: Log statements out of sync: current test case was null" The problem for us seemed to be that we have two threads doing prints during our unittests . First we have a logging framework called SwiftyBeaver that printed prints on a background thread, but some other prints in the unittests were done are made on then the main thread and this seems to cause the problem.So by instead logging all prints to a file, instead of printing, we managed to get away from this bug. 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-18544) Missing dependency to git
Title: Message Title Sorin Sbarnea closed an issue as Cannot Reproduce Jenkins / JENKINS-18544 Missing dependency to git Change By: Sorin Sbarnea Status: Open Closed Resolution: Cannot Reproduce 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-18542) Make dependency to git plugin optional
Title: Message Title Sorin Sbarnea closed an issue as Won't Fix Git plugin is part of Jenkins basic list of plugins now. Jenkins / JENKINS-18542 Make dependency to git plugin optional Change By: Sorin Sbarnea Status: Open Closed Resolution: Won't Fix 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.co
[JIRA] (JENKINS-16868) Icons are not displayed with a reverse proxy
Title: Message Title Sorin Sbarnea resolved as Cannot Reproduce I am using it (1.16) in the same configuration without problems so I assume this was fixed. Jenkins / JENKINS-16868 Icons are not displayed with a reverse proxy Change By: Sorin Sbarnea Status: Reopened Resolved Resolution: Cannot Reproduce 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.
[JIRA] (JENKINS-39770) PipelineRunGraph not rendered
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered Change By: Julien Pivotto Attachment: undef.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-39770) PipelineRunGraph not rendered
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered Change By: Julien Pivotto Attachment: undef3.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-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.
Title: Message Title Nicolas Nobelis commented on JENKINS-36132 Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed. Hello, We are facing the same issue on a Master since our migration to a more recent version of Jenkins (2.19.1). I think this is because they changed how workspace are organized on the filesystem. In our old version : $JENKINS_HOME/jobs/[job-name]/workspace In the new version : $JENKINS_HOME/workspace/[job-name] I hope this hint helps. Best regards, Nicolas 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-36132) Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed.
Title: Message Title Nicolas Nobelis edited a comment on JENKINS-36132 Re: Failed to display file source for resharper analysis: Copying the source file from the workspace to the build folder on the Jenkins master failed. Hello,We are facing the same issue on a Master since our migration to a more recent version of Jenkins (2.19.1).I think this is because they changed how workspace workspaces are organized on the filesystem.In our old version :$JENKINS_HOME/jobs/[job-name]/workspaceIn the new version :$JENKINS_HOME/workspace/[job-name]I hope this hint helps.Best regards,Nicolas 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-39772) Make BFA compatible with ansible task output log
Title: Message Title Sorin Sbarnea created an issue Jenkins / JENKINS-39772 Make BFA compatible with ansible task output log Issue Type: Improvement Assignee: Tomas Westling Components: build-failure-analyzer-plugin Created: 2016/Nov/16 10:23 AM Environment: 1.6 Priority: Major Reporter: Sorin Sbarnea There are some serious limitation regarding use of BFA plugin when you also use Ansible on Jenkins and this is caused mostly by the way Ansible output the result of executed tasks. Ansible returns the entire command output as a JSON where newlines are transformed into `\n`. This means that some lines can be really huge, even 1MB in some extreme cases. If you do not reach out of memory or serious performance degradation you will discover that BFA will highlight the entire Ansible result if it matches an error. We need to find a way to address these issues: highlight only a portion of the very long line recognize very long lines and eventually skip them recognize ansible output and parse it after splitting it not at a single line.
[JIRA] (JENKINS-39773) Check if script needs approval before executing it
Title: Message Title Max Wahler created an issue Jenkins / JENKINS-39773 Check if script needs approval before executing it Issue Type: Improvement Assignee: Unassigned Components: pipeline Created: 2016/Nov/16 10:24 AM Priority: Major Reporter: Max Wahler It often happens that I modify a pipeline script, it runs for several minutes in Jenkins and then fails because I added a method call that needs approval. Then I approve that method, run it again and have to hope that there's not another method call I have to approve. So IMHO it'd be great if Jenkins did some kind of "dry run" on a script to check if there's any method signature that still needs approval and immediately fails before the script was actually executed. This may also have severe consequences, e.g. if a component was deployed and the script fails afterwards and it's impossible to roll back the deployment. Add Comment
[JIRA] (JENKINS-39773) Check if script needs approval before executing it
Title: Message Title Max Wahler updated an issue Jenkins / JENKINS-39773 Check if script needs approval before executing it Change By: Max Wahler It often happens that I modify a pipeline script, it runs for several minutes in Jenkins and then fails because I added a method call that needs approval. Then I approve that method, run it again and have to hope that there's not another method call I have to approve.So IMHO it'd be great if Jenkins did some kind of "dry run" on a script to check if there's any method signature that still needs approval and immediately fails before the script was actually executed.This may also have severe consequences, e.g. if a component was deployed and the script fails afterwards and it's impossible to roll back the deployment. Also, it's not possible to add script approvals manually using the web interface so I actually have to wait for the script to fail. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are s
[JIRA] (JENKINS-39317) force encryption of credentials
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-39317 force encryption of credentials Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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-39317) force encryption of credentials
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39317 Re: force encryption of credentials Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/UserCredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/76f7838ee36f296ab780e021404d88b1fb3c8dc9 Log: [FIXED JENKINS-39317] Provide a mechanism for forcing a save of all credential store This method will only be available via Groovy scripting 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-39723) BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow)
Title: Message Title Jakub Czaplicki commented on JENKINS-39723 Re: BlueOcean beta v1.0.0-b11 dependency errors (docker-workflow) Possibly. This plugin has so many names that I wouldn't be surprised if the black mirrors got confused: CloudBees Docker Pipeline , docker-workflow, and now just Docker Pipeline Plugin Actually the day I've hit the issue described in this ticket, the docker-workflow plugin changed it name, so that's what probably caused the plugin not to be visible in my repo : Version history Version 1.9.1 (Nov 14, 2016) Name changed to remove word “CloudBees”. btw. I've installed docker-workflow 1.9 via HPI file, today I updated Jenkins to 2.31, and now I see that I have Docker Pipeline 1.9.1. Magic. 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-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39768 Multiple checkout in Pipeline but only one seen in git data Change By: Mark Waite 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-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title Mark Waite commented on JENKINS-39768 Re: Multiple checkout in Pipeline but only one seen in git data Please provide more detailed instructions that will allow others to duplicate the problem on a separate machine. The pictures are certainly helpful, but there are many ways that I could make mistakes or make poor guesses on how you arrived at those pictures. Best would be a pointer to a Dockerfile or a public Docker instance which will show the problem, since then that can be installed and run and used for diagnosis. If that's not feasible, then please provide a numbered series of steps which state how to recreate 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-39770) PipelineRunGraph not rendered
Title: Message Title Julien Pivotto updated an issue Jenkins / JENKINS-39770 PipelineRunGraph not rendered Change By: Julien Pivotto Attachment: undef6.png Attachment: undef7.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-39770) PipelineRunGraph not rendered
Title: Message Title Julien Pivotto commented on JENKINS-39770 Re: PipelineRunGraph not rendered Suggestion is that pipeline does not work when there are more than 100 steps because /run/x/nodes only returns 100 entries. 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-39728 Jenkins not able to clone private bitbucket repo Change By: Mark Waite 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Mark Waite commented on JENKINS-39728 Re: Jenkins not able to clone private bitbucket repo I'm unable to duplicate the problem. I have automated tests which regularly check that I can clone from a private bitbucket repository using the following configurations: Git implementation Repository URL Credential command line git https://markewa...@bitbucket.org/markewaite/bin.git markewaite bitbucket username/password jgit https://markewa...@bitbucket.org/markewaite/bin.git markewaite bitbucket username/password jgitapache https://markewa...@bitbucket.org/markewaite/bin.git markewaite bitbucket username/password command line git g...@bitbucket.org:markewaite/bin.git markewaite bitbucket rsa private key jgit g...@bitbucket.org:markewaite/bin.git markewaite bitbucket rsa private key jgitapache g...@bitbucket.org:markewaite/bin.git markewaite bitbucket rsa private key
[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
Shell script:
cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in 0; do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done
Pipeline:
stage('test'){
node {
checkouts = [:]
for (i=0; i<10; 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
}
}
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
[JIRA] (JENKINS-39768) Multiple checkout in Pipeline but only one seen in git data
Title: Message Title
Julien Pivotto edited a comment on JENKINS-39768
Re: Multiple checkout in Pipeline but only one seen in git data
Shell script:{code}cd /tmp; git init foo;(cd foo; touch a; git add a; git commit -m a); for i in $(seq 0 30) ; do cp -r foo foo$i;(cd foo$i; git commit --amend -m a); done{code}Pipeline:{code}stage('test'){node {checkouts = [:]for (i=0; i< 10 30 ; 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}
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-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.
[JIRA] (JENKINS-35173) jobs not removed when branch gets removed
Title: Message Title Sergey Zhemzhitsky updated an issue Jenkins / JENKINS-35173 jobs not removed when branch gets removed Change By: Sergey Zhemzhitsky Attachment: jenkins_orphaned_strategy_empty_number.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-39716) Adapt docker tests execution when ATH itself runs as docker container
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39716 Re: Adapt docker tests execution when ATH itself runs as docker container Code changed in jenkins User: Manuel Franco Path: src/main/java/org/jenkinsci/test/acceptance/docker/DockerContainer.java http://jenkins-ci.org/commit/acceptance-test-harness/320e758ba8d100ca3deeef623cd8a97234e3461a Log: JENKINS-39716 adapt docker tests execution when ATH itself runs as docker container 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-39716) Adapt docker tests execution when ATH itself runs as docker container
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39716 Re: Adapt docker tests execution when ATH itself runs as docker container Code changed in jenkins User: Oliver Gondža Path: docs/FIXTURES.md src/main/java/org/jenkinsci/test/acceptance/docker/DockerContainer.java http://jenkins-ci.org/commit/acceptance-test-harness/709cb0f40f28204a9ddeba4dd381157ae4673932 Log: Merge pull request #222 from mafraba/JENKINS-39716 JENKINS-39716 adapt docker tests execution when ATH itself runs as docker container Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/39d8337b0702...709cb0f40f28 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-39716) Adapt docker tests execution when ATH itself runs as docker container
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39716 Re: Adapt docker tests execution when ATH itself runs as docker container Code changed in jenkins User: Manuel Franco Path: docs/FIXTURES.md http://jenkins-ci.org/commit/acceptance-test-harness/948236c0ba32baa162b3eeed71b487ec2b2f1093 Log: JENKINS-39716 add docs about SHARED_DOCKER_SERVICE setting 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 a
[JIRA] (JENKINS-35173) jobs not removed when branch gets removed
Title: Message Title Sergey Zhemzhitsky updated an issue Jenkins / JENKINS-35173 jobs not removed when branch gets removed Change By: Sergey Zhemzhitsky Attachment: jenkins_orphaned_strategy_zero_items_to_keep.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-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-39694) Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
Title: Message Title Mark Waite commented on JENKINS-39694 Re: Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false. I don't think @jglick was asking to close the ticket. I think he was giving a brief answer that expresses how I've preferred to maintain the git plugin. A longer answer might be: The git plugin is used by more than 80 000 installations. With that many installations, modifying default behavior is very risky, even if that default behavior seems illogical, has no tests to support it, and seems like a mistake. The current default behaviors, for better or for worse, have implicit dependencies throughout user installations. Past changes to default behaviors have consistently resulted in loud complaints from users who had developed interesting and novel ways to rely on that default behavior. It has been more successful in the past to add a switch which enables a new behavior, and allows the user to optionally choose to enable that switch with the new behavior. A proposal that describes how to do that in this specific case is JENKINS-39250. I'm not willing to discard the `createAccountBasedOnEmail` setting for the same reason. Somewhere in the over 80 000 installations of the git plugin, there are users that depend on the behaviors of each of the settings of that toggle. I'm still open to discussion and persuasion that the behavior of `createAccountBasedOnEmail` has regressed across releases. If that is the case, then I'd need to know when it regressed. That would then allow us to discuss and agree on a judgment call which decides who will be best served, those who prefer the current behavior, or those who prefer the behavior before the regression. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-35173) jobs not removed when branch gets removed
Title: Message Title Sergey Zhemzhitsky commented on JENKINS-35173 Re: jobs not removed when branch gets removed I don't think that the issue is connected with bitbucket only. As I have already mentioned the jobs are not removed until I set Max # of old items to keep to zero. I have the orphan strategy setup like the following... with Max # of old items to keep set to an empty string. Then while reindexing Jenkins says ... Looking up / for pull requests Evaluating orphaned items in » build-multi Will not remove DMC-1234-test as it is only #1 in the list ... If I set Max # of old items to keep to zero directly ... then old items for non-existent branches are removed successfully ... Looking up / for pull requests Evaluating orphaned items in » build-multi Will remove DMC-1234-test as it is only #1 in the list ... 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 receivin
[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-39694) Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
Title: Message Title Mark Waite edited a comment on JENKINS-39694 Re: Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false. I don't think @ [~ jglick ] was asking to close the ticket. I think he was giving a brief answer that expresses how I've preferred to maintain the git plugin. A longer answer might be:The git plugin is used by more than 80 000 installations. With that many installations, modifying default behavior is very risky, even if that default behavior seems illogical, has no tests to support it, and seems like a mistake. The current default behaviors, for better or for worse, have implicit dependencies throughout user installations. Past changes to default behaviors have consistently resulted in loud complaints from users who had developed interesting and novel ways to rely on that default behavior.It has been more successful in the past to add a switch which enables a new behavior, and allows the user to optionally choose to enable that switch with the new behavior. A proposal that describes how to do that in this specific case is JENKINS-39250.I'm not willing to discard the `createAccountBasedOnEmail` setting for the same reason. Somewhere in the over 80 000 installations of the git plugin, there are users that depend on the behaviors of each of the settings of that toggle.I'm still open to discussion and persuasion that the behavior of `createAccountBasedOnEmail` has regressed across releases. If that is the case, then I'd need to know when it regressed. That would then allow us to discuss and agree on a judgment call which decides who will be best served, those who prefer the current behavior, or those who prefer the behavior before the regression. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39694) Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
Title: Message Title
Mark Waite edited a comment on JENKINS-39694
Re: Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
I don't think [~jglick] was asking to close the ticket. I think he was giving a brief answer that expresses how I've preferred to maintain the git plugin. A longer answer might be:The git plugin is used by more than 80 000 installations. With that many installations, modifying default behavior is very risky, even if that default behavior seems illogical, has no tests to support it, and seems like a mistake. The current default behaviors, for better or for worse, have implicit dependencies throughout user installations. Past changes to default behaviors have consistently resulted in loud complaints from users who had developed interesting and novel ways to rely on that default behavior.It has been more successful in the past to add a switch which enables a new behavior, and allows the user to optionally choose to enable that switch with the new behavior. A proposal that describes how to do that in this specific case is JENKINS-39250.I'm not willing to discard the ` {code:java} createAccountBasedOnEmail ` {code} setting for the same reason. Somewhere in the over 80 000 installations of the git plugin, there are users that depend on the behaviors of each of the settings of that toggle.I'm still open to discussion and persuasion that the behavior of ` {code:java} createAccountBasedOnEmail ` {code} has regressed across releases. If that is the case, then I'd need to know when it regressed. That would then allow us to discuss and agree on a judgment call which decides who will be best served, those who prefer the current behavior, or those who prefer the behavior before the regression.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39694) Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
Title: Message Title
Mark Waite edited a comment on JENKINS-39694
Re: Git plugin creates Users for authors regardless if global createAccountBasedOnEmail is false.
I don't think [~jglick] was asking to close the ticket. I think he was giving a brief answer that expresses how I've preferred to maintain the git plugin. A longer answer might be:The git plugin is used by more than 80 000 installations. With that many installations, modifying default behavior is very risky, even if that default behavior seems illogical, has no tests to support it, and seems like a mistake. The current default behaviors, for better or for worse, have implicit dependencies throughout user installations. Past changes to default behaviors have consistently resulted in loud complaints from users who had developed interesting and novel ways to rely on that default behavior.It has been more successful in the past to add a switch which enables a new behavior, and allows the user to optionally choose to enable that switch with the new behavior. A proposal that describes how to do that in this specific case is JENKINS-39250.I'm not willing to discard the {code:java} createAccountBasedOnEmail {code} setting for the same reason. Somewhere in the over 80 000 installations of the git plugin, there are users that depend on the behaviors of each of the settings of that toggle.I'm still open to discussion and persuasion that the behavior of {code:java} createAccountBasedOnEmail {code} has regressed across releases. If that is the case, then I'd need to know when it regressed. That would then allow us to discuss and agree on a judgment call which decides who will be best served, those who prefer the current behavior, or those who prefer the behavior before the regression.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-38875) Git configurations lost in every single job after update to 3.0.0
Title: Message Title Mark Waite closed an issue as Cannot Reproduce I'm closing this report as "Cannot Reproduce" after a month with no response to my request for more information to duplicate the problem. If more information becomes available, please reopen the bug report. Jenkins / JENKINS-38875 Git configurations lost in every single job after update to 3.0.0 Change By: Mark Waite Status: Open Closed Resolution: Cannot Reproduce 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" g
[JIRA] (JENKINS-38875) Git configurations lost in every single job after update to 3.0.0
Title: Message Title Mark Waite edited a comment on JENKINS-38875 Re: Git configurations lost in every single job after update to 3.0.0 I'm closing this report as "Cannot Reproduce" after a month with no response to my request for more information to duplicate the problem. If more information becomes available, please reopenthe bug report. 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-39728) Jenkins not able to clone private bitbucket repo
Title: Message Title Mark Waite edited a comment on JENKINS-39728 Re: Jenkins not able to clone private bitbucket repo I'm unable to duplicate the problem. I have automated tests which regularly check that I can clone from a private bitbucket repository using the following configurations:||Git implementation||Repository URL||Credential|||command line git|https://markewa...@bitbucket.org/markewaite/bin.git|markewaite bitbucket username/password||jgit|https://markewa...@bitbucket.org/markewaite/bin.git|markewaite bitbucket username/password||jgitapache|https://markewa...@bitbucket.org/markewaite/bin.git|markewaite bitbucket username/password||command line git|g...@bitbucket.org:markewaite/bin.git|markewaite bitbucket rsa private key||jgit|g...@bitbucket.org:markewaite/bin.git|markewaite bitbucket rsa private key||jgitapache|g...@bitbucket.org:markewaite/bin.git|markewaite bitbucket rsa private key|I confirmed those all run successfully on my Windows 10 computers using recent versions of command line git (and the jgit installed with the git client plugin and the gitapache jgitapache installed with git client plugin 2.1.0).Does the same failure happen if you use jgit instead of command line git?Does the same failure happen if you use git client plugin 2.1.0 and jgitapache?Have you asked for help on the jenkins users mailing list, since there are many more people reading that list than read bug reports for the 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 recei
[JIRA] (JENKINS-39774) API: export getAllItems() to be accessed from the RestAPI
Title: Message Title Victor Martinez created an issue Jenkins / JENKINS-39774 API: export getAllItems() to be accessed from the RestAPI Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Nov/16 12:26 PM Labels: api Priority: Major Reporter: Victor Martinez Regarding the below thread: https://groups.google.com/forum/#!topic/jenkinsci-users/3drn20pK2Fs I'd like to list all the items in one single rest api access. At the moment, getAllItems is not exported : https://github.com/jenkinsci/jenkins/blob/jenkins-2.31/core/src/main/java/jenkins/model/Jenkins.java#L1761 As getItems is exported https://github.com/jenkinsci/jenkins/blob/jenkins-2.31/core/src/main/java/jenkins/model/Jenkins.java#L1710 Thanks
[JIRA] (JENKINS-39736) Pipeline bug with Trend Graph
Title: Message Title Shayquan Smith updated an issue Jenkins / JENKINS-39736 Pipeline bug with Trend Graph Change By: Shayquan Smith EDIT: I use windows 7 64 bit professional.I updated to jenkins 2.3.0 and it did not solve my problem. Hi,when going for pipeline syntax snippet generator -> step -> msbuild -> more settings -> link to trend graph at the bottom i get this bug:javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) 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$11.dispatch(MetaClass.java:380) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$5.doDispatch(MetaClass.java:233) 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.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 hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:126) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:86) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1652) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.BasicHeaderProcessor.doFilter(BasicHeade
[JIRA] (JENKINS-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title Paul Allen updated JENKINS-39152 fixed in 1.4.9 with changed for JENKINS-38425 Jenkins / JENKINS-39152 Reduce submit delay caused by Perforce triggered build endpoint Change By: Paul Allen Status: In Review Closed Resolution: Fixed 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.
[JIRA] (JENKINS-39278) new pipeline build not started by p4 trigger if existing pipeline already running
Title: Message Title Paul Allen closed an issue as Fixed Fixed in 1.4.9 with changes for JENKINS-39152 Jenkins / JENKINS-39278 new pipeline build not started by p4 trigger if existing pipeline already running Change By: Paul Allen Status: Open Closed Resolution: Fixed 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:/
[JIRA] (JENKINS-39775) EmptyStackException from PipelineNodeGraphVisitor.parallelBranchStart
Title: Message Title Jesse Glick created an issue Jenkins / JENKINS-39775 EmptyStackException from PipelineNodeGraphVisitor.parallelBranchStart Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Nov/16 12:52 PM Environment: BlueOcean 1.0.0-b12 Priority: Critical Reporter: Jesse Glick To reproduce, make -C .../jenkinsci/parallel-test-executor-plugin/demo run Log in as admin and you should soon see pipeline » master #1 building. Install BlueOcean from the update center. Go to the B.O. display and once #1 has finished, click the start button to schedule build #2. You will soon see a lot of exceptions in the console: ... WARNING org.eclipse.jetty.util.log.JavaUtilLog warn Error while serving http://localhost:8080/blue/rest/organizations/jenkins/pipelines/pipeline/branches/master/runs/2/nodes/ java.lang.reflect.InvocationTargetException at ... Caused by: java.util.EmptyStackException at java.util.Stack.peek(Stack.java:102) at java.util.Stack.pop(Stack.java:84) at io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeGraphVisitor.parallelBranchStart(PipelineNodeGraphVisitor.java:158) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(ForkScanner.java:593) at org.jenkinsci.plugins.workflow.graphanalysis.ForkScanner.visitSimpleChunks(F
[JIRA] (JENKINS-38872) integrate with folders plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-38872 Re: integrate with folders plugin Code changed in jenkins User: imod Path: src/main/java/org/jenkinsci/lib/configprovider/ConfigProvider.java src/main/java/org/jenkinsci/plugins/configfiles/GlobalConfigFiles.java src/main/java/org/jenkinsci/plugins/configfiles/folder/FolderConfigFileAction.java http://jenkins-ci.org/commit/config-file-provider-plugin/2698560919cb325a3ede04e7337440e2199924db Log: JENKINS-38872 allow ConfigProviders to backup from folder support 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-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos created an issue Jenkins / JENKINS-39776 Perform test per domain Issue Type: Improvement Assignee: Félix Belzunce Arcos Components: active-directory-plugin Created: 2016/Nov/16 12:56 PM Environment: Instead of using a test domain/test domain controller a test per domain can be easily performed. Priority: Minor Reporter: Félix Belzunce Arcos Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-39776 Perform test per domain Change By: Félix Belzunce Arcos Instead of using having a test domain/test domain controller a test per domain can be easily performed. 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-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos started work on JENKINS-39776 Change By: Félix Belzunce Arcos Status: Open In Progress 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-39776) Perform test per domain
Title: Message Title Félix Belzunce Arcos updated an issue Jenkins / JENKINS-39776 Perform test per domain Change By: Félix Belzunce Arcos Environment: Instead of using a test domain/test domain controller a test per domain can be easily performed. Instead of using a test domain/test domain controller a test per domain can be easily performed. 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-39317) force encryption of credentials
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39317 Re: force encryption of credentials Code changed in jenkins User: Stephen Connolly Path: src/main/java/com/cloudbees/plugins/credentials/CredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/CredentialsStore.java src/main/java/com/cloudbees/plugins/credentials/SystemCredentialsProvider.java src/main/java/com/cloudbees/plugins/credentials/UserCredentialsProvider.java http://jenkins-ci.org/commit/credentials-plugin/aa382a6c3e4971b7696049122293209124157c06 Log: Merge pull request #73 from jenkinsci/jenkins-39317 [FIXED JENKINS-39317] Provide a mechanism for forcing a save of all credential store Compare: https://github.com/jenkinsci/credentials-plugin/compare/2dbde368af34...aa382a6c3e49 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-39758) Artifactory plugin does not publish simple gradle project
Title: Message Title Sud Ramasamy commented on JENKINS-39758 Re: Artifactory plugin does not publish simple gradle project I found JENKINS-39755 and as per that issue, when I downgraded to 2.7.2 the publish from the root project worked. The generated gradle artifactory plugin file does look the same though. So I don't think my original analysis of this issue is valid. 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-35173) jobs not removed when branch gets removed
Title: Message Title Dominik Bartholdi commented on JENKINS-35173 Re: jobs not removed when branch gets removed then I think you have a different issue then the one I originally opened this ticket. Maybe better to create a new one then. (and maybe add a reference to this one) 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-39777) comments in /etc/default/jenkins
Title: Message Title less burgess created an issue Jenkins / JENKINS-39777 comments in /etc/default/jenkins Issue Type: Improvement Assignee: Unassigned Components: core Created: 2016/Nov/16 1:08 PM Environment: debian packages Labels: jenkins configuration Priority: Minor Reporter: less burgess the file /etc/default/jenkins in the debian package has a line with a config value and a comment in the same line: JAVA_ARGS="-Djava.awt.headless=true" # Allow graphs etc. to work even when an X server is present this leads to some problems regarding automation and also makes this harder to read. i would prefer to have all comments in seperate lines, for example: # Allow graphs etc. to work even when an X server is present JAVA_ARGS="-Djava.awt.headless=true" please consider to change this.
[JIRA] (JENKINS-39777) comments in /etc/default/jenkins
Title: Message Title less burgess assigned an issue to Kohsuke Kawaguchi assigned to you, as the maintainer of the deb package. best regards Jenkins / JENKINS-39777 comments in /etc/default/jenkins Change By: less burgess Assignee: Kohsuke Kawaguchi 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-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner reopened an issue I also get this error now from time to time. The ATH test case fails sometimes: seems that the output of the pipeline is not correctly flushed in some circumstances. Jenkins / JENKINS-32191 workflow plugin does not provide console to warnings plugin, sleep required Change By: Ulli Hafner Resolution: Cannot Reproduce Status: Resolved Reopened Assignee: Ulli Hafner Jesse Glick Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-32191 workflow plugin does not provide console to warnings plugin, sleep required Change By: Ulli Hafner Component/s: pipeline 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-12114) Flexible file editing permissions
Title: Message Title Chris Brookes commented on JENKINS-12114 Re: Flexible file editing permissions Being able to add/change config files without having to be an administrator would be useful. Currently, you have to have Overall/Administer permission to edit the files. I don't want to have to give everybody administrator access just so they can create config files when setting up jobs. 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-39152) Reduce submit delay caused by Perforce triggered build endpoint
Title: Message Title Tobias Germer commented on JENKINS-39152 Re: Reduce submit delay caused by Perforce triggered build endpoint Thanks for the fix! We will test the release soon. 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-39743) Improve acceptance tests for javadoc plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39743 Re: Improve acceptance tests for javadoc plugin Code changed in jenkins User: Evaristo Gutiérrez Path: src/main/java/org/jenkinsci/test/acceptance/plugins/javadoc/JavadocPublisher.java src/test/java/plugins/JavadocPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/ecc357d1961e770f1cd9a436955d0737ba99a8f0 Log: JENKINS-39743 Create test to validate Javadoc retention for each build. 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-39743) Improve acceptance tests for javadoc plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39743 Re: Improve acceptance tests for javadoc plugin Code changed in jenkins User: Evaristo Gutiérrez Path: src/test/java/plugins/JavadocPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/f09bb36e86b8670d4dc8afd9984b4fb9e6926160 Log: JENKINS-39743 Add missing import. 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-39743) Improve acceptance tests for javadoc plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39743 Re: Improve acceptance tests for javadoc plugin Code changed in jenkins User: Evaristo Gutiérrez Path: src/test/java/plugins/JavadocPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/483a78da43aa7e1e7cc63ddccd7ae873b4fadade Log: JENKINS-39743 Use not matcher to avoid try block. 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-39743) Improve acceptance tests for javadoc plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-39743 Re: Improve acceptance tests for javadoc plugin Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/plugins/javadoc/JavadocPublisher.java src/test/java/plugins/JavadocPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/4bec627b7c4fb44b0272dd024cc76cedbd0a5257 Log: Merge pull request #223 from varyvol/JENKINS-39743 JENKINS-39743 Create test for the javadoc retention for each build Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/709cb0f40f28...4bec627b7c4f 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-32191) workflow plugin does not provide console to warnings plugin, sleep required
Title: Message Title Ulli Hafner edited a comment on JENKINS-32191 Re: workflow plugin does not provide console to warnings plugin, sleep required I also get this error now from time to time. The ATH test case fails sometimes: seems that the output of the pipeline is not correctly flushed in some circumstances. (I changed the test locally now, seems that I can reproduce it on my machine. I'll push it if I finished a refactoring) 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-39743) Improve acceptance tests for javadoc plugin
Title: Message Title Evaristo Gutierrez updated JENKINS-39743 Jenkins / JENKINS-39743 Improve acceptance tests for javadoc plugin Change By: Evaristo Gutierrez Status: In Review Resolved Resolution: Fixed 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-39778) Wrong parser interpration in XML with pattern QList
Title: Message Title hans bauer created an issue Jenkins / JENKINS-39778 Wrong parser interpration in XML with pattern QList Issue Type: Bug Assignee: Ulli Hafner Components: pmd-plugin Created: 2016/Nov/16 2:03 PM Environment: Jenkins version 2.7.3 PMD-Plugin version 3.45 Labels: plugin Priority: Minor Reporter: hans bauer While parsing an oclint generated xml-file PMD rises an exception on valid content. Apparently the parser interprets the error description with the string " _'QList' _" not as description, but as a XML-tag instead. That is the parser exception: Unable to find source-code formatter for language: bash. Available languages are: actionscript, html, java, _javascript_, none, sql, xhtml, xml [PMD] Parsing of file /var/lib/jenkins/workspace/Manual-Development-oclint/src/oclint.xml failed due to an exception: org.xml.sax.SAXParseException; lineNumber: 2639; columnNumber: 3; The element type "bool" must be terminated by the matching end-tag "". And that are the corresponding lines in /var/lib/jenkins/workspace/Manual-Development-oclint/src/oclint.xml:
[JIRA] (JENKINS-33355) Support Pipeline (Workflow) plugin
Title: Message Title Damien Merenne assigned an issue to Damien Merenne Jenkins / JENKINS-33355 Support Pipeline (Workflow) plugin Change By: Damien Merenne Assignee: Damien Merenne 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.
