[JIRA] (JENKINS-40469) Manage and Assign Roles - Plugin doesn't work as intended
Title: Message Title Shamanth Kumar commented on JENKINS-40469 Re: Manage and Assign Roles - Plugin doesn't work as intended Hi Oleg, Thanks for the quick reply I use "Jenkins’ own user database" as Security realm. Ok, users use the proper case only while logging in but even then it was not working but right now it works. If it doesn't work again, i will get back here Regards, Shamanth 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-40463) Show more buttons not correct on branch page.
Title: Message Title James Dumay commented on JENKINS-40463 Re: Show more buttons not correct on branch page. Sweet 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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak edited a comment on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown I've downgraded analysis-core to version 1.79. The graphs show up again.* https://issues.jenkins-ci.org/secure/attachment/ 35183 35184 /JENKINS-40251_static-analysis-179.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-40463) Show more buttons not correct on branch page.
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-40463 Show more buttons not correct on branch page. Change By: James Dumay Assignee: Ivan Meredith 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-40463) Show more buttons not correct on branch page.
Title: Message Title Michael Neale closed an issue as Fixed Jenkins / JENKINS-40463 Show more buttons not correct on branch page. Change By: Michael Neale 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://groups.google.com/d/optout.
[JIRA] (JENKINS-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak updated an issue Jenkins / JENKINS-40251 Dependency Check trend graphs and related values are not shown Change By: Tilmann Haak Attachment: JENKINS-40251_static-analysis-179.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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak updated an issue Jenkins / JENKINS-40251 Dependency Check trend graphs and related values are not shown Change By: Tilmann Haak Attachment: JENKINS-40251_static-analysis-179.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-40463) Show more buttons not correct on branch page.
Title: Message Title Michael Neale commented on JENKINS-40463 Re: Show more buttons not correct on branch page. oh - this was fixed in: https://github.com/jenkinsci/blueocean-plugin/pull/659 will close this. There is another ticket to track the non trivial work of improving the ATH to cover all cases of pagination: https://issues.jenkins-ci.org/browse/JENKINS-40434 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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak edited a comment on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown I've downgraded analysis-core to version 1.79. The graphs show up again.* https://issues.jenkins-ci.org/secure/ thumbnail attachment /35183/ _thumb_35183 JENKINS-40251_static-analysis-179 .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-40080) All pages make multiple /classes requests
Title: Message Title Michael Neale commented on JENKINS-40080 Re: All pages make multiple /classes requests ah, in that case.. carry on. I was thinking something scoped to document or window as a "Cache" which would be blown away. 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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak edited a comment on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown I've downgraded analysis-core to version 1.79. The graphs show up again. !JENKINS * https://issues.jenkins - 40251_static-analysis-179 ci . png| org/secure/ thumbnail ! /35183/_thumb_35183.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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak commented on JENKINS-40251 Re: Dependency Check trend graphs and related values are not shown I've downgraded analysis-core to version 1.79. The graphs show up again. Unable to render embedded object: File (JENKINS-40251_static-analysis-179.png) not found. 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-40251) Dependency Check trend graphs and related values are not shown
Title: Message Title Tilmann Haak updated an issue Jenkins / JENKINS-40251 Dependency Check trend graphs and related values are not shown Change By: Tilmann Haak Attachment: JENKINS-40251_static-analysis-179.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-40469) Manage and Assign Roles - Plugin doesn't work as intended
Title: Message Title Oleg Nenashev commented on JENKINS-40469 Re: Manage and Assign Roles - Plugin doesn't work as intended Seems you use Active Directory as a Security realm, right? If yes, I'd guess users use different case when they enter their username to login. The plugin is case-sensitive 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-40439) Move parsers into external library
Title: Message Title Tomas Bjerre commented on JENKINS-40439 Re: Move parsers into external library 1a I use the library also in Gradle and Maven plugins. Others may use it in whatever application they want, perhaps another CI server. Having a dependency to Jenins just does not make sense for a library whose only task is to read and parse text-files. 1b I prefer to make it Java 7 compatible because its still used by alot of people. Unnecessary libraries on the classpath will be a problem for users of the library. For example, they may already have another version of Apache commons already on the classpath. It may be there because of another dependency or because they need it themselves. They would have to exclude dependencies and sometimes it will be impossible to resolve the situation and find a version that is compatible with all libraries using it. I have been able to implement alot of parsers this way, the library is very clean, very easy to work with and understand for anyone familiar with Java. I'd like to keep it that way. 2 That to me sounds like something other then reading and parsing text files. Not a problem that should be solved by the library. 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-40467) Failure on Preparing Scenario step when using jenkins with loadrunner controller
Title: Message Title Pallavi Shinde updated an issue Jenkins / JENKINS-40467 Failure on Preparing Scenario step when using jenkins with loadrunner controller Change By: Pallavi Shinde Issue Type: Task 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title James Dumay edited a comment on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly [~svanoort] [~vivek] is there some way we could have this show up as if it was wrapped in a stage? not sure if we should do this in the frontend code, Blue Oceam Ocean or bismuth level. 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title James Dumay commented on JENKINS-39464 Re: Pipeline with parallel and no stages does not get visualised correctly Sam Van Oort Vivek Pandey is there some way we could have this show up as if it was wrapped in a stage? not sure if we should do this in the frontend code, Blue Oceam or bismuth level. 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-39464) Pipeline with parallel and no stages does not get visualised correctly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39464 Pipeline with parallel and no stages does not get visualised correctly Change By: James Dumay Summary: pipeline Pipeline with parallel but not and no stages shows up only first branch does not get visualised correctly 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-40080) All pages make multiple /classes requests
Title: Message Title James Dumay commented on JENKINS-40080 Re: All pages make multiple /classes requests Michael Neale a client side cache has no notion of the server being restarted. 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-40224) Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly
Title: Message Title James Dumay assigned an issue to James Dumay Jenkins / JENKINS-40224 Mailer links of failed jobs are broken with BlueOcean plugin, not redirecting properly Change By: James Dumay Assignee: James Dumay 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-40463) Show more buttons not correct on branch page.
Title: Message Title James Dumay commented on JENKINS-40463 Re: Show more buttons not correct on branch page. Ivan Meredith Michael Neale what is the problem here? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39703) API to read/write a single file from/to the repository
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39703 API to read/write a single file from/to the repository Change By: James Dumay Sprint: frank 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-40469) Manage and Assign Roles - Plugin doesn't work as intended
Title: Message Title Shamanth Kumar created an issue Jenkins / JENKINS-40469 Manage and Assign Roles - Plugin doesn't work as intended Issue Type: Bug Assignee: Oleg Nenashev Attachments: Page1.PNG, Page2.PNG, Page3.PNG Components: role-strategy-plugin Created: 2016/Dec/15 6:38 AM Environment: Jenkins version. 2.7.2 Role-based Authorization Strategy - 2.3.2 Priority: Critical Reporter: Shamanth Kumar Hi, I have created Global and Project Roles based on my requirement. Assigned roles to different user. The user who has the Admin access only get the access intended to perform. For Other users, sometimes they get access to build and sometimes they don't. And this issue is also not consistant. Kindly look into it and resolve. Regards, Shamanth Add Comment
[JIRA] (JENKINS-40392) Improving developer experience for blue ocean core developers and extenders
Title: Message Title Michael Neale edited a comment on JENKINS-40392 Re: Improving developer experience for blue ocean core developers and extenders Some of those tickets seem a little too "prescriptive" (ie leaping to the solution). I think there needs to be some problem statements of things that should be solved (otherwise this is just moving aroubd pieces for no point). Off the top of my head: 1) A developer should easily be able to update a shared js dependency during development that is used across a multi module project without messing with package.json files and versions2) A developer should be able to open a pull request for review without having to publish beta versions of shared js libs (related to #1)3) A developer shouldn't need to worry about updating shrinkwrap 4) Clean build speed should be faster , or changing branches should not require a full clean 5) A developer shouldn't have to worry about where watch is run, changes should be picked up automatically during hpi:run6) A developer should be able to easily "link" in a js lib that is outside the blueocean-plugin dir at development time to make co-ordinated changes. 7) A plugin developer shouldn't worry about matching versions with what blueocean-web/dashboard requires, but just depend on blueocean (for plugins outside of the blueocean-plugin dir)8) A plugin developer should not worry about inadvertently bundling a dependency which blueocean should deliver 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
[JIRA] (JENKINS-40468) Ability to force clone
Title: Message Title cowwoc commented on JENKINS-40468 Re: Ability to force clone No need. Users can simply invoke "deleteDir()" before "checkout()" and this will have the desired effect. Also, this design scales better than stuffing this functionality in the SCM 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-40468) Ability to force clone
Title: Message Title cowwoc closed an issue as Not A Defect Jenkins / JENKINS-40468 Ability to force clone Change By: cowwoc Status: Open Closed Resolution: Not A Defect 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-40392) Improving developer experience for blue ocean core developers and extenders
Title: Message Title Michael Neale edited a comment on JENKINS-40392 Re: Improving developer experience for blue ocean core developers and extenders Some of those tickets seem a little too "prescriptive" (ie leaping to the solution). I think there needs to be some problem statements of things that should be solved (otherwise this is just moving aroubd pieces for no point). Off the top of my head: 1) A developer should easily be able to update a shared js dependency during development that is used across a multi module project without messing with package.json files and versions2) A developer should be able to open a pull request for review without having to publish beta versions of shared js libs (related to #1)3) A developer shouldn't need to worry about updating shrinkwrap 4) Clean build speed should be faster5) A developer shouldn't have to worry about where watch is run, changes should be picked up automatically during hpi:run 6) A developer should be able to easily "link" in a js lib that is outside the blueocean-plugin dir at development time to make co-ordinated changes.7) A plugin developer shouldn't worry about matching versions with what blueocean-web/dashboard requires, but just depend on blueocean (for plugins outside of the blueocean-plugin dir)8) A plugin developer should not worry about inadvertently bundling a dependency which blueocean should deliver 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
[JIRA] (JENKINS-40392) Improving developer experience for blue ocean core developers and extenders
Title: Message Title Michael Neale edited a comment on JENKINS-40392 Re: Improving developer experience for blue ocean core developers and extenders Some of those tickets seem a little too "prescriptive" (ie leaping to the solution). I think there needs to be some problem statements of things that should be solved (otherwise this is just moving aroubd pieces for no point). Off the top of my head: 1) A developer should easily be able to update a shared js dependency during development that is used across a multi module project without messing with package.json files and versions2) A developer should be able to open a pull request for review without having to publish beta versions of shared js libs (related to #1)3) A developer shouldn't need to worry about updating shrinkwrap 4) Clean build speed should be faster5) A developer shouldn't have to worry about where watch is run, changes should be picked up automatically 6) A developer should be able to easily "link" in a js lib that is outside the blueocean-plugin dir at development time to make co-ordinated changes. 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-40080) All pages make multiple /classes requests
Title: Message Title Michael Neale commented on JENKINS-40080 Re: All pages make multiple /classes requests I think the cache is a non issue as the web app is reloaded on server restart in all cases anyway 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-40080) All pages make multiple /classes requests
Title: Message Title Michael Neale edited a comment on JENKINS-40080 Re: All pages make multiple /classes requests I think the cache Cache invalidation is a non issue as the web app is reloaded on server restart in all cases anyway 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-40392) Improving developer experience for blue ocean core developers and extenders
Title: Message Title Michael Neale commented on JENKINS-40392 Re: Improving developer experience for blue ocean core developers and extenders Some of those tickets seem a little too "prescriptive" (ie leaping to the solution). I think there needs to be some problem statements of things that should be solved (otherwise this is just moving aroubd pieces for no point). Off the top of my head: 1) A developer should easily be able to update a shared js dependency that is used across a multi module project without messing with package.json files and versions 2) A developer should be able to open a pull request for review without having to publish beta versions of shared js libs (related to #1) 3) A developer shouldn't need to worry about updating shrinkwrap 4) Clean build speed should be faster 5) A developer shouldn't have to worry about where watch is run, changes should be picked up automatically 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-40468) Ability to force clone
Title: Message Title cowwoc created an issue Jenkins / JENKINS-40468 Ability to force clone Issue Type: Bug Assignee: Unassigned Components: mercurial-plugin Created: 2016/Dec/15 6:16 AM Priority: Minor Reporter: cowwoc Unlike git, the Mercurial "checkout" command only offers a "Clean Build" option which is used to purge the working directory. We need an equivalent of the "Wipe workspace and force clone" functionality available to the git plugin. Specifically, I am running into problems where the local repository contains more commits than the remote which is causing problems. I need to force a re-clone; otherwise, the script will need to be able to recover from a partially-updated repository after a failed build. Add Comment
[JIRA] (JENKINS-16151) Maven "release:perform" cannot find hg
Title: Message Title cowwoc commented on JENKINS-16151 Re: Maven "release:perform" cannot find hg I believe we can close this issue because in the new Pipeline design users will need to add HG to the PATH anyway (to interact with it from a shell, etc). 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-40466) Developer wants to see a message when execution is blocked waiting for a node
Title: Message Title Michael Neale commented on JENKINS-40466 Re: Developer wants to see a message when execution is blocked waiting for a node Can we extend this to report provisioning problems (they would show up as a failed build, but currently the detail is lost generally) 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-39703) API to read/write a single file from/to the repository
Title: Message Title James Dumay assigned an issue to Stephen Connolly Jenkins / JENKINS-39703 API to read/write a single file from/to the repository Change By: James Dumay Assignee: James Dumay Stephen Connolly 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-40441) multibranch fails indexing on ATH for strange pipeline names
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40441 multibranch fails indexing on ATH for strange pipeline names Change By: James Dumay Sprint: frank 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-40298) Include automatically extracted licenses in plugin(s)
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40298 Include automatically extracted licenses in plugin(s) Change By: James Dumay Sprint: kraken 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-40463) Show more buttons not correct on branch page.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40463 Show more buttons not correct on branch page. Change By: James Dumay Sprint: frank 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-40467) Failure on Preparing Scenario step when using jenkins with loadrunner controller
Title: Message Title Pallavi Shinde created an issue Jenkins / JENKINS-40467 Failure on Preparing Scenario step when using jenkins with loadrunner controller Issue Type: Task Assignee: Ofir Shaked Attachments: Jenkins_Issue.png Components: hp-application-automation-tools-plugin Created: 2016/Dec/15 5:56 AM Environment: Jenkins 2.19.4, Windows 7 Enterprise OS, 64 bit, HP-application automation tools plugin version 4.5 Labels: jenkins plugin Priority: Major Reporter: Pallavi Shinde I am getting build failure error on "Preparing Scenario" step when executing tests through HP loadrunner controller. However the scenario runs just fine on loadrunner controller. Before initial 2 builds were successful but next day same scenario same settings started causing error. Also the error message displayed on console is just "Error". I am unable to understand the exact error. Please refer following screenshot for error details.
[JIRA] (JENKINS-40466) Developer wants to see a message when execution is blocked waiting for a node
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-40466
Developer wants to see a message when execution is blocked waiting for a node
Issue Type:
Task
Assignee:
Unassigned
Attachments:
blocked.png
Components:
blueocean-plugin
Created:
2016/Dec/15 5:55 AM
Priority:
Critical
Reporter:
James Dumay
Problem When a pipeline is waiting for a node we display a generic "Waiting for run to start" message. What we want to see We want to show an appropriate message when a Pipeline is waiting for a node "Waiting for a node labeled XYZ to become available"
node ('does not exist or busy') {
sh 'echo hello world'
}
Add Comment
[JIRA] (JENKINS-40080) All pages make multiple /classes requests
Title: Message Title James Dumay commented on JENKINS-40080 Re: All pages make multiple /classes requests Tom FENNELLY classes could be different across reboots of a Jenkins server so are not cacheable on the client without a cache invalidation scheme. The problem with classes as designed is that we need to make these requests at all which is why I want to take this back to Vivek. 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-40465) PR are not build if read access is not available on the Source branch
Title: Message Title Abishek Manoharan created an issue Jenkins / JENKINS-40465 PR are not build if read access is not available on the Source branch Issue Type: Bug Assignee: Antonio Muñiz Components: bitbucket-branch-source-plugin Created: 2016/Dec/15 5:19 AM Priority: Critical Reporter: Abishek Manoharan When I try to initiate a build for the PR request, it shows Looking up MI/apis for branches Checking branch master from MI/apis Met criteria Looking up MI/apis for pull requests Checking PR from ~ABISHEK_MANOHARAN/apis and branch master Does not meet criteria Now, the credentials used in Jenkins for Bitbucket does not have permission to read "~ABISHEK_MANOHARAN/apis" repository, but it has the permissions to read/write on "MI/apis" repository. It's not possible to provide the credentials read access to all the repositories from which a pull request might come. Using the credentials I am able to view and approve the PR on the Bitbucket Server Web interface, so I think it should be possible to build with the PR from Jenkins as well. If, I give read access to "~ABISHEK_MANOHARAN/apis" repo, then it's building fine.
[JIRA] (JENKINS-38179) Authentication Error with GIT Client version 2.0.0
Title: Message Title Benjamin Goldman commented on JENKINS-38179 Re: Authentication Error with GIT Client version 2.0.0 your workaround worked. Thanks. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40455) Global Environment Variables are no accessible outside of node { }
Title: Message Title
Patrick Wolf edited a comment on JENKINS-40455
Re: Global Environment Variables are no accessible outside of node { }
If you run this without the {{env}} prefix you get a stack trace because the Groovy variable is not defined.{code:java}Started by user Admin[Pipeline] node Running on master in /Users/pwolf/.jenkins/workspace/env [Pipeline] {[Pipeline] sh[env] Running shell script+ grep -i foo+ printenvFOO_PIPELINE=BARRR[Pipeline] echoFOO_PIPELINE is: BARRR[Pipeline] }[Pipeline] // node[Pipeline] End of Pipelinegroovy.lang.MissingPropertyException: No such property: FOO_PIPELINE for class: groovy.lang.Binding at groovy.lang.Binding.getVariable(Binding.java:63) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224) at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241) at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238) at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28) at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20) at WorkflowScript.run(WorkflowScript:6) at ___cps.transform___(Native Method) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74) at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30) at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66) at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72) at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21) at com.cloudbees.groovy.cps.Next.step(Next.java:58) at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30) at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108) at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30) at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236) at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)Finished: FAILURE{code}
[JIRA] (JENKINS-40455) Global Environment Variables are no accessible outside of node { }
Title: Message Title
Patrick Wolf commented on JENKINS-40455
Re: Global Environment Variables are no accessible outside of node { }
If you run this without the env prefix you get a stack trace because the Groovy variable is not defined.
Started by user Admin
[Pipeline] node
Running on master in /Users/pwolf/.jenkins/workspace/env
[Pipeline] {
[Pipeline] sh
[env] Running shell script
+ grep -i foo
+ printenv
FOO_PIPELINE=BARRR
[Pipeline] echo
FOO_PIPELINE is: BARRR
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
groovy.lang.MissingPropertyException: No such property: FOO_PIPELINE for class: groovy.lang.Binding
at groovy.lang.Binding.getVariable(Binding.java:63)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.SandboxInterceptor.onGetProperty(SandboxInterceptor.java:224)
at org.kohsuke.groovy.sandbox.impl.Checker$4.call(Checker.java:241)
at org.kohsuke.groovy.sandbox.impl.Checker.checkedGetProperty(Checker.java:238)
at com.cloudbees.groovy.cps.sandbox.SandboxInvoker.getProperty(SandboxInvoker.java:28)
at com.cloudbees.groovy.cps.impl.PropertyAccessBlock.rawGet(PropertyAccessBlock.java:20)
at WorkflowScript.run(WorkflowScript:6)
at ___cps.transform___(Native Method)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.get(PropertyishBlock.java:74)
at com.cloudbees.groovy.cps.LValueBlock$GetAdapter.receive(LValueBlock.java:30)
at com.cloudbees.groovy.cps.impl.PropertyishBlock$ContinuationImpl.fixName(PropertyishBlock.java:66)
at sun.reflect.GeneratedMethodAccessor473.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.cloudbees.groovy.cps.impl.ContinuationPtr$ContinuationImpl.receive(ContinuationPtr.java:72)
at com.cloudbees.groovy.cps.impl.ConstantBlock.eval(ConstantBlock.java:21)
at com.cloudbees.groovy.cps.Next.step(Next.java:58)
at com.cloudbees.groovy.cps.Continuable.run0(Continuable.java:154)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.access$001(SandboxContinuable.java:18)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:33)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable$1.call(SandboxContinuable.java:30)
at org.jenkinsci.plugins.scriptsecurity.sandbox.groovy.GroovySandbox.runInSandbox(GroovySandbox.java:108)
at org.jenkinsci.plugins.workflow.cps.SandboxContinuable.run0(SandboxContinuable.java:30)
at org.jenkinsci.plugins.workflow.cps.CpsThread.runNextChunk(CpsThread.java:163)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.run(CpsThreadGroup.java:324)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup.access$100(CpsThreadGroup.java:78)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:236)
at org.jenkinsci.plugins.workflow.cps.CpsThreadGroup$2.call(CpsThreadGroup.java:224)
at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$2.call(CpsVmExecutorService.java:63)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:112)
at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
[JIRA] (JENKINS-38707) Scheduled builds in the GitHub Org folder shouldn't fail if the rate limit is exceeded
Title: Message Title Patrick Wolf started work on JENKINS-38707 Change By: Patrick Wolf 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-26486) Workspace fails to update when Replace missing/modified files is checked
Title: Message Title yury nedelin edited a comment on JENKINS-26486 Re: Workspace fails to update when Replace missing/modified files is checked This is still an issue in 2.19.4, This is Java memory allocation issue, Look for file jenkins.xml or Jenkins-slave.xml if its a slave machine in your Jenkins install directory. look for -Xmx parameter mine was set to -Xmx256m, change it to higher number. If number is too high it Jenkins might fail to start service on 32 bit java . -Xmx1024m worked for me. If you have 64 bit java installed on your machine but you still can not start Service with -Xmx bigger then 1024m you might have to update jre inside Jenkins. So if you run >java -version and it shows Java HotSpot(TM) 64-Bit Server VM (build 24.60-b09, mixed mode)but Jenkins still would not start, you can replace everything inside Jenkins/jre with contents of 64 bit installation from something like "C:\Program Files\Java\jre1.8.0_111".A bit hacky but seem to work. -Xrs -Xmx1024m -Dhudson.lifecycle=hudson.lifecycle.WindowsServiceLifecycle -jar "%BASE%\jenkins.war" --httpPort=8080 --webroot="%BASE%\war"look here for reference on the syntax for memory amounthttp://www.wikihow.com/Increase-Java-Memory-in-Windows-7 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-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title Michael Neale commented on JENKINS-39464 Re: pipeline with parallel but not stages shows up only first branch yeah this comes up again and again... so worth catering to IMO 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-40464) Support settings Quiet Period in multibranch pipeline builds
Title: Message Title Chance Zibolski updated an issue Jenkins / JENKINS-40464 Support settings Quiet Period in multibranch pipeline builds Change By: Chance Zibolski Currently only normal pipelines, and non-pipeline job types support setting the quiet period within build triggers. Having this functionality is even more important for multi-branch pipelines because of the way reindexing after a merge occurs. If I want to merge a large number of branches into master, then than for each one merge, jenkins will trigger a rebuild of all open pull-requests. It would be great if we could merge everything quickly, and only trigger a single rebuild of each pull-request we have open. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-40464) Support settings Quiet Period in multibranch pipeline builds
Title: Message Title Chance Zibolski created an issue Jenkins / JENKINS-40464 Support settings Quiet Period in multibranch pipeline builds Issue Type: New Feature Assignee: Unassigned Components: pipeline, workflow-multibranch-plugin Created: 2016/Dec/15 2:43 AM Priority: Major Reporter: Chance Zibolski Currently only normal pipelines, and non-pipeline job types support setting the quiet period within build triggers. Having this functionality is even more important for multi-branch pipelines because of the way reindexing after a merge occurs. If I want to merge a large number of branches into master, then each one will trigger a rebuild of all open pull-requests. It would be great if we could merge everything quickly, and only trigger a single rebuild of each pull-request we have open. Add Comment
[JIRA] (JENKINS-30053) REST ApI support in the claim plugin
Title: Message Title Shagen Ogandzhanian commented on JENKINS-30053 Re: REST ApI support in the claim plugin I'm actually want to have REST (or any) API for claiming jobs but as of you comment - why you should check all the jobs - not only broken ones? 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-40341) Can not view stack trace for NUnit tests
Title: Message Title James Dumay commented on JENKINS-40341 Re: Can not view stack trace for NUnit tests Thanks Yogesh Bhole. I am going to have someone look into test reporting plugin compatibility in the new year so this is really helpful 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-38493) Add a new status indicator for "waiting for input"
Title: Message Title James Dumay commented on JENKINS-38493 Re: Add a new status indicator for "waiting for input" Looking good Thor! 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-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39464
pipeline with parallel but not stages shows up only first branch
Change By:
James Dumay
*Problem*If you have a parallel declaration, but no stages, in classic stage view nothing shows up (you just have to look at log). In blue ocean, you get a single node (stage) which shows only the first branch. Expected behavior: should show 3 parallel branches (ideally) *Example*{noformat}parallel 'branch1': {node('node1') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}, 'branch2': {node('node2') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}{noformat}*Workaround*Simply wrap the parallels in a {{stage}} and it will work correctly.{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code} It will then be visualised like: !snap.png|thumbnail!
Add Comment
[JIRA] (JENKINS-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39464
pipeline with parallel but not stages shows up only first branch
Change By:
James Dumay
*Problem*If you have a parallel declaration, but no stages, in classic stage view nothing shows up (you just have to look at log). In blue ocean, you get a single node (stage) which shows only the first branch. Expected behavior: should show 3 parallel branches (ideally) *Example*{noformat}parallel 'branch1': {node('node1') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}, 'branch2': {node('node2') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}{noformat}*Workaround*Simply wrap the parallels in a {{stage}} and it will work correctly.{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}It will then be visualised like: !snap.png |thumbnail !
Add Comment
[JIRA] (JENKINS-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-39464 pipeline with parallel but not stages shows up only first branch Change By: James Dumay Attachment: snap.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-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-39464 pipeline with parallel but not stages shows up only first branch Change By: James Dumay Assignee: Josh McDonald 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-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39464
pipeline with parallel but not stages shows up only first branch
Change By:
James Dumay
*Problem*If you have a parallel declaration, but no stages, in classic stage view nothing shows up (you just have to look at log). In blue ocean, you get a single node (stage) which shows only the first branch. Expected behavior: should show 3 parallel branches (ideally) * Visualisation*The pipeline below results in this visualisation: !Screen Shot 2016-11-03 at 12.24.11 pm.png! * Example*{noformat}parallel (lint 'branch1' : {node ('node1') { echo "yeah" stage('Setup') { } checkout([details removed]) } , verifyZoneFiles: stage('Unit and Integration Tests') { node {echo bat ' " yeah my command to execute tests " ' } } }, rspec 'branch2' : {node ('node2') { echo stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat ' " yeah my command to execute tests " ' } } } , ) {noformat}*Workaround*Simply wrap the parallels in a {{stage}} and it will work corr correctly.{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}
Add Comment
[JIRA] (JENKINS-39464) pipeline with parallel but not stages shows up only first branch
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-39464
pipeline with parallel but not stages shows up only first branch
Change By:
James Dumay
*Problem* If you have a parallel declaration, but no stages, in classic stage view nothing shows up (you just have to look at log). In blue ocean, you get a single node (stage) which shows only the first branch. Expected behavior: should show 3 parallel branches (ideally) *Visualisation* The pipeline below results in this visualisation:!Screen Shot 2016-11-03 at 12.24.11 pm.png |thumbnail ! The pipeline: *Example* {noformat}parallel(lint: {node {echo "yeah"}},verifyZoneFiles: {node {echo "yeah"}},rspec: {node {echo "yeah"}},){noformat} *Workaround*Simply wrap the parallels in a {{stage}} and it will work corr
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay updated JENKINS-40446 There is a fix in the next version of the plugin. Release is a week away. Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Change By: James Dumay 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
[JIRA] (JENKINS-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay started work on JENKINS-40446 Change By: James Dumay 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay updated JENKINS-40446 Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Change By: James Dumay Status: In Progress Review 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Change By: James Dumay Sprint: frank 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay edited a comment on JENKINS-40446 Re: Links broken in GitHub status for matrix projects [~michaelneale] working on a fix for the blueocean display URL plugin that will not generate a blue URL to matrix projects.But yes, there is an option to disable the behaviour on the user profile coming 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title James Dumay commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects Michael Neale working on a fix for the blueocean display URL plugin that will not generate a blue URL to matrix projects. But yes, there is an option to disable the behaviour on the user profile. 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-40434) Pagination for branches and ATH coverage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40434 Pagination for branches and ATH coverage Change By: Michael Neale Priority: Major Critical 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-40434) Pagination for branches and ATH coverage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-40434
Pagination for branches and ATH coverage
Change By:
Michael Neale
Paging currently has some problems. 1) broken on activity (PR has been merged, see below)2) Branches hides show more button erroneously * In Scope** Write an ATH for branches and activity pagination* Fix the bug with activity button: ttps://github.com/jenkinsci/blueocean-plugin/pull/658* Fix branches* Remove fetchMore and test case if it isn't needed (from smart-fetch.js) - is smart-fetch.js actually used now? confirm with test coverage* Steps to reproduce broken pagination on activity *# Go to https://ci.blueocean.io/blue/organizations/jenkins/blueocean/activity/# Click {{show more}}*Console error*{noformat}Uncaught TypeError: _this2.pager.fetchMore is not a functionat onClick (https://ci.blueocean.io/adjuncts/8c0ace04/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:31655:53)at Object.invokeGuardedCallback (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:85069:12)at executeDispatch (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:77193:21)at Object.executeDispatchesInOrder (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:77216:5)at executeDispatchesAndRelease (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76670:22)at executeDispatchesAndReleaseTopLevel (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76681:10)at Array.forEach (native)at forEachAccumulated (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:91338:9)at Object.processEventQueue (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76857:7)at runEventQueueInBatch (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:85127:18){noformat} *In Scope* * Fix the bug: ttps://github.com/jenkinsci/blueocean-plugin/pull/658* Write an ATH* Remove fetchMore and test case if it isn't needed (from smart-fetch.js) - is smart-fetch.js actually used now? confirm with test coverage cc [~imeredith]
Add Comment
[JIRA] (JENKINS-40434) Pagination for branches and ATH coverage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40434 Pagination for branches and ATH coverage Change By: Michael Neale Summary: Pagination needs for branches and ATH coverage 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Michael Neale commented on JENKINS-40446 Re: Links broken in GitHub status for matrix projects Leandro Lucarella as an immediate measure, if you remove the plugin called "BlueOcean Display URL plugin" then it should revert to the normal behavior. There is an update to that plugin that lets it be configured to. (it won't be re-installed automatically). Or disable it - up to you. there is also a related ticket: https://issues.jenkins-ci.org/browse/JENKINS-37427 which will make blue ocean do the right thing with matrix, which would make this kind of moot, but you need to solve this now - so I recommend the above. James Dumay do I have this right? 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-40446) Links broken in GitHub status for matrix projects
Title: Message Title Michael Neale assigned an issue to James Dumay Jenkins / JENKINS-40446 Links broken in GitHub status for matrix projects Change By: Michael Neale Assignee: James Dumay 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-40463) Show more buttons not correct on branch page.
Title: Message Title Ivan Meredith updated an issue Jenkins / JENKINS-40463 Show more buttons not correct on branch page. Change By: Ivan Meredith Summary: Show more buttons not correct on acitivity and branch page. 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-40463) Show more buttons not correct on acitivity and branch page.
Title: Message Title Ivan Meredith created an issue Jenkins / JENKINS-40463 Show more buttons not correct on acitivity and branch page. Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2016/Dec/15 12:17 AM Priority: Blocker Reporter: Ivan Meredith 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
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly with the introduction of {{branch}}. Ideally we could tell from BO if the user has skipped via {{when}} or via {{branch}}.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy to staging ') {agent label:'some-node' when { branch "master"} steps {sh './ deploy deploy_pr .sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}.{code}stage('deploy to staging') {agent label:'some-node' when { branch "feature/*"} steps {sh './deploy_pr.sh'}}{code}
Add Comment
This message was sent by Atlassian JIRA
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly with the introduction of {{branch}}. Ideally we could tell from BO if the user has skipped via {{when}} or via {{branch}}.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy to staging') {agent label:'some-node'when { branch "master" }steps {sh './deploy_pr.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}.{code}stage('deploy to staging') {agent label:'some-node'when { branch "feature/*" }steps {sh './deploy_pr.sh'}}{code}*Example - _expression_*You can use an {{_expression_}} to achieve the same thing by:{code}stage('deploy to staging') {agent label:'some-node'when { _expression_ { return BRANCH == 'master';}}steps {sh './deploy_pr.sh'}}{code}
Add Comment
[JIRA] (JENKINS-40370) Run stage when branch name matches
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40370
Run stage when branch name matches
Change By:
James Dumay
*Motivation*Commonly people want to run particular stages when they match a specific branch name(s). We would like to make this pattern accessible in the editor.Declarative allows the use of {{when}} to condition the stage execution like:{code}stage('second') {agent label:'some-node'branch "master" when {env.BRANCH == 'master'}}{code}However, this isn't exactly what we would consider "friendly" for an editor accessible feature (though {{when}} will be supported via a text area) and the developer would have to learn the Script syntax to use it correctly.*Solution*We would like to formalise the pattern in a way that is more Editor and user friendly with the introduction of {{branch}}. Ideally we could tell from BO if the user has skipped via {{when}} or via {{branch}}.*Example - match single branch*This stage would only be executed if {{master}} was the name of the current branch.{code}stage('deploy to staging') {agent label:'some-node'when { branch "master" }steps {sh './deploy_pr.sh'}}{code}*Example - match branch name pattern*This stage would only be executed if the branch name started with {{feature/}}.{code}stage('deploy to staging') {agent label:'some-node'when { branch "feature/*" }steps {sh './deploy_pr.sh'}}{code} *Example - _expression_*You can use an {{_expression_}} to achieve the same thing by:{code}stage('deploy to staging') {agent label:'some-node'when { _expression_ { return BRANCH == 'master';}}steps {sh './deploy_pr.sh'}}{code}
Add Comment
[JIRA] (JENKINS-40462) Wrappers in options
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40462
Wrappers in options
Change By:
James Dumay
We don't want to have change wrappers from: {code}pipeline {agent nonewrappers {timeout(time: 5, unit: 'MINUTES')colorize()}stages {stage("foo") {steps {echo "hello"}}}}{code}To look like this :{code}pipeline {agent noneoptions { timeout(time: 5, unit: 'MINUTES') colorize()}stages {stage("foo") {steps {echo "hello"}}}}{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-40462) Wrappers in options
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-40462
Wrappers in options
Issue Type:
Task
Assignee:
Andrew Bayer
Components:
pipeline-model-definition-plugin
Created:
2016/Dec/14 11:27 PM
Priority:
Minor
Reporter:
James Dumay
We don't want to have
pipeline {
agent none
wrappers {
timeout(time: 5, unit: 'MINUTES')
colorize()
}
stages {
stage("foo") {
steps {
echo "hello"
}
}
}
}
To:
pipeline {
agent none
options {
timeout(time: 5, unit: 'MINUTES')
colorize()
}
stages {
stage("foo") {
steps {
echo "hello"
}
}
}
}
[JIRA] (JENKINS-40080) All pages make multiple /classes requests
Title: Message Title Michael Neale commented on JENKINS-40080 Re: All pages make multiple /classes requests Tom FENNELLY was only referring to fetching via a POST 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-40458) Parallel pipeline not rendering properly
Title: Message Title Ching-Hwa Yu commented on JENKINS-40458 Re: Parallel pipeline not rendering properly Oh, I see... thanks for the quick response! I've followed JENKINS-39464 and hopefully that'll get tackled soonish 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-40434) REGRESSION: pagination is broken on activity
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40434 REGRESSION: pagination is broken on activity Change By: Michael Neale Priority: Blocker 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-40434) Pagination needs ATH coverage
Title: Message Title
Michael Neale updated an issue
Jenkins / JENKINS-40434
Pagination needs ATH coverage
Change By:
Michael Neale
*Steps to reproduce*# Go to https://ci.blueocean.io/blue/organizations/jenkins/blueocean/activity/# Click {{show more}}*Console error*{noformat}Uncaught TypeError: _this2.pager.fetchMore is not a functionat onClick (https://ci.blueocean.io/adjuncts/8c0ace04/org/jenkins/ui/jsmodules/blueocean-dashboard/jenkins-js-extension.js:31655:53)at Object.invokeGuardedCallback (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:85069:12)at executeDispatch (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:77193:21)at Object.executeDispatchesInOrder (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:77216:5)at executeDispatchesAndRelease (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76670:22)at executeDispatchesAndReleaseTopLevel (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76681:10)at Array.forEach (native)at forEachAccumulated (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:91338:9)at Object.processEventQueue (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:76857:7)at runEventQueueInBatch (https://ci.blueocean.io/adjuncts/8c0ace04/io/jenkins/blueocean/blueocean.js:85127:18){noformat}*In Scope** Fix the bug: ttps://github.com/jenkinsci/blueocean-plugin/pull/658* Write an ATH* Remove fetchMore and test case if it isn't needed (from smart-fetch.js) - is smart-fetch.js actually used now?confirm with test coverage cc [~imeredith]
Add Comment
[JIRA] (JENKINS-40434) Pagination needs ATH coverage
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-40434 Pagination needs ATH coverage Change By: Michael Neale Summary: REGRESSION: pagination is broken on activity Pagination needs ATH coverage 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-40458) Parallel pipeline not rendering properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40458 Parallel pipeline not rendering properly Change By: James Dumay Attachment: JENKINS-40458 #5 2016-12-15 10-04-01.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-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay edited a comment on JENKINS-40458
Re: Parallel pipeline not rendering properly
Thanks for reporting this problem. It is a duplicate of JENKINS-39464.The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}That will make your Pipeline look like: !snap.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay edited a comment on JENKINS-40458
Re: Parallel pipeline not rendering properly
Thanks for reporting this problem. It is a duplicate of JENKINS-39464.The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}That will make your Pipeline look like: !snap.png |thumbnail !
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40458 Parallel pipeline not rendering properly Change By: James Dumay Attachment: snap.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-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay edited a comment on JENKINS-40458
Re: Parallel pipeline not rendering properly
Thanks for reporting this problem. It is a duplicate of JENKINS-39464.The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}That will make your Pipeline look like: ! JENKINS-40458 #5 2016-12-15 10-04-01.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-40458 Parallel pipeline not rendering properly Change By: James Dumay Attachment: JENKINS-40458 #5 2016-12-15 10-04-01.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-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay edited a comment on JENKINS-40458
Re: Parallel pipeline not rendering properly
Thanks for reporting this problem. It is a duplicate of JENKINS-39464.The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code}That will make your Pipeline look like: ! JENKINS-40458 #5 2016-12-15 10-04-01.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay edited a comment on JENKINS-40458
Re: Parallel pipeline not rendering properly
Thanks for reporting this problem. It is a duplicate of JENKINS-39464.The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:{code}stage('Build and Test') { parallel 'branch1': { node('node1') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }, 'branch2': { node('node2') { stage('Setup') { checkout([details removed]) } stage('Unit and Integration Tests') { bat '"my command to execute tests"' } } }}{code} That will make your Pipeline look like:
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-40137) Open in blue ocean button does not work for runs when the branch name contains a /
Title: Message Title Michael Neale commented on JENKINS-40137 Re: Open in blue ocean button does not work for runs when the branch name contains a / Tom FENNELLY right didn't see that. In that case, its just missing some extra cases. 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-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay resolved as Duplicate
Thanks for reporting this problem. It is a duplicate of JENKINS-39464. The easiest way to avoid this misrendering is to wrap your parallels in a single stage like so:
stage('Build and Test') {
parallel 'branch1': {
node('node1') {
stage('Setup') {
checkout([details removed])
}
stage('Unit and Integration Tests') {
bat '"my command to execute tests"'
}
}
}, 'branch2': {
node('node2') {
stage('Setup') {
checkout([details removed])
}
stage('Unit and Integration Tests') {
bat '"my command to execute tests"'
}
}
}
}
Jenkins / JENKINS-40458
Parallel pipeline not rendering properly
Change By:
James Dumay
Status:
Open Resolved
Resolution:
Duplicate
Add Comment
[JIRA] (JENKINS-40461) ${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Title: Message Title
Nick Jones created an issue
Jenkins / JENKINS-40461
${DURATION} template contains "and counting" even at job conclusion, for pipeline builds
Issue Type:
Bug
Assignee:
Unassigned
Components:
hipchat-plugin
Created:
2016/Dec/14 10:31 PM
Environment:
Jenkins 2.19.4 LTS, HipChat Plugin 2.0.0
Priority:
Minor
Reporter:
Nick Jones
I'm doing HipChat notifications in a Pipeline build (via Jenkinsfile) and even at job conclusion – as the very last step in a Jenkinsfile script – the DURATION template's value contains the string "and counting", e.g., "36 sec and counting". I can see this being appropriate while the job is in progress but it's awkward when it's done. The default templates sent by the HipChat plugin in a non-pipeline (e.g., freestyle) scenario show job success messages like "Build successful after 36 sec". An example of my usage:
hipchatSend (
color: 'GREEN',
credentialId: 'HipChatToken',
message: 'Done in ${DURATION}',
room: '12456',
server: 'hipchat.company.com',
v2enabled: true)
This generates a message like this:
Done in 0.7 sec and counting
Given that this is a notification-time template evaluation, I don't have
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-40458
Parallel pipeline not rendering properly
Change By:
James Dumay
I have a fairly simple pipeline: {code} parallel 'branch1': {node('node1') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}, 'branch2': {node('node2') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}} {code} It doesn't seem to render the branches properly and the first stage uses the first branch's name.Please see attachments. The blackouts are the branch names. I also removed the emailext step from the pipeline .
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
[JIRA] (JENKINS-38998) Cannot trigger pipeline job
Title: Message Title Simon Weber commented on JENKINS-38998 Re: Cannot trigger pipeline job This is a blocker for us as well. I'm happy to try and fix this if a maintainer can point me in the right direction. 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-40460) Null Pointer Exception when polling P4
Title: Message Title Pete McNab created an issue Jenkins / JENKINS-40460 Null Pointer Exception when polling P4 Issue Type: Bug Assignee: Unassigned Components: p4-plugin Created: 2016/Dec/14 10:23 PM Environment: Jenkins 2.19.4 P4 Plugin 1.4.11 Priority: Critical Reporter: Pete McNab I have a pipeline job and when I turned on SCM polling, My P4 Polling log reports an NPE: (some internal strings replaced by <>) Started on Dec 14, 2016 2:08:00 PM P4: Polling on: master with: Found last change 1468074 on client ... p4 client -o + ... p4 info + P4 Task: establishing connection. ... server: perforce:1666 ... node: P4: Polling with range: 1468074,now ... p4 changes ///...@1468074,now + P4: Polling on: master with:jenkins-master---BUILD_NUMBER-- ... p4 client -o jenkins-master---BUILD_NUMBER--___ + ... p4 info + P4 Task: establishing connection. ... server: perforce:1666 ... node: P4 Task: attempt: 1 P4 Task: failed: java.lang.NullPointerException ERROR: polling failed in /var/tmp/workspace// on : P4 Task: failed: java.lang.NullPointerException Done. Took 3.3 sec No changes The jenkins.log reports: Dec 14, 2016 2:13:00 PM org.jenkinsci.plugins.p4.tasks.AbstractTask tryTask SEVERE: P4 Task: attempt: 1 java.lang.NullPointerException at
[JIRA] (JENKINS-40459) SeleniumHQ Plugin driver system error
Title: Message Title
Boris Tuman created an issue
Jenkins / JENKINS-40459
SeleniumHQ Plugin driver system error
Issue Type:
Bug
Assignee:
pascal_martin
Components:
seleniumhq-plugin
Created:
2016/Dec/14 10:14 PM
Priority:
Major
Reporter:
Boris Tuman
When using the seleniumhq plugin, this error comes up {{ "java.lang.IllegalStateException: The path to the driver executable must be set by the webdriver.gecko.driver system property; for more information, see https://github.com/mozilla/geckodriver. The latest version can be downloaded from https://github.com/mozilla/geckodriver/releases"}} There is no where to place this configuration.
Add Comment
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title
Ching-Hwa Yu updated an issue
Jenkins / JENKINS-40458
Parallel pipeline not rendering properly
Change By:
Ching-Hwa Yu
I have a fairly simple pipeline:parallel 'branch1': {node('node1') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}, 'branch2': {node('node2') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}It doesn't seem to render the branches properly and the first stage uses the first branch's name.Please see attachments. The blackouts are the branch names. I also removed the extemail step from the 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
[JIRA] (JENKINS-40458) Parallel pipeline not rendering properly
Title: Message Title
Ching-Hwa Yu updated an issue
Jenkins / JENKINS-40458
Parallel pipeline not rendering properly
Change By:
Ching-Hwa Yu
I have a fairly simple pipeline:parallel 'branch1': {node('node1') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}, 'branch2': {node('node2') {stage('Setup') {checkout([details removed])}stage('Unit and Integration Tests') {bat '"my command to execute tests"'}}}It doesn't seem to render the branches properly and the first stage uses the first branch's name.Please see attachments. The blackouts are the branch names. I also removed the extemail emailext step from the pipeline.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are
