[JIRA] (JENKINS-51050) Blueocean paused for Input requested, but never asks for it
Title: Message Title James Dumay commented on JENKINS-51050 Re: Blueocean paused for Input requested, but never asks for it Miguel C could you please post a simplified example Jenkinsfile that demonstrates this problem? cc Jenn Briden Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46809) Allow sequential stages inside parallel in Declarative syntax
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-46809 Allow sequential stages inside parallel in Declarative syntax Change By: James Dumay Summary: Allow sequencial sequential stages inside parallel in Declarative syntax Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: James Dumay Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43148) Support native Git for pipeline creation and editing
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43148 Support native Git for pipeline creation and editing Change By: James Dumay Sprint: Blue Ocean 1.0-rc4, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.3 , Blue Ocean 1.5 - beta 3 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title James Dumay commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues Mind if we spend 20 talking about the solution here tomorrow? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-39203) All stages show up as UNSTABLE when only one stage should
Title: Message Title James Dumay commented on JENKINS-39203 Re: All stages show up as UNSTABLE when only one stage should Helmi BEDOUI we still plan on fixing this but no ETA yet. Requires a big rework of how statuses are reporting in Pipeline, so its not as simple as it might seem. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title James Dumay commented on JENKINS-46571 Re: Update URL scheme to remove URL encoding issues Ivan Meredith how does moving to query params fix the problem we have? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43892) Developer would like to see all successful test results
Title: Message Title James Dumay commented on JENKINS-43892 Re: Developer would like to see all successful test results Successful test display is shipping in the next release. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43892) Developer would like to see all successful test results
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-43892 Developer would like to see all successful test results Change By: James Dumay Attachment: successful-tests.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-46336) Sidecar docker containers for declarative
Title: Message Title James Dumay commented on JENKINS-46336 Re: Sidecar docker containers for declarative Christopher Orr good eye Thank you! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41581) Declarative: Support for multiple docker agents run in parallel and communicating
Title: Message Title James Dumay resolved as Duplicate Jenkins / JENKINS-41581 Declarative: Support for multiple docker agents run in parallel and communicating Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-33846) Restart pipeline from specific stage, after failure
Title: Message Title James Dumay commented on JENKINS-33846 Re: Restart pipeline from specific stage, after failure The plan is to allow this to work for any previously executed stage Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43995) Individual Pipeline steps and stages/blocks should have Result statuses
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43995
Individual Pipeline steps and stages/blocks should have Result statuses
Change By:
James Dumay
*Problem* Currently, the only status we have for an individual {{FlowNode}} (be it representing an atomic {{Step}} or a block) is whether it has an {{ErrorAction}}. Blue Ocean would like to be able to visualize other {{Result}} types (such as {{UNSTABLE}} and {{ABORTED}}) distinctly, as well as to be able to have all steps/blocks get marked as {{UNSTABLE}} or {{ABORTED}} if only one step/block actually is unstable or was aborted. *Approach*We want to have a shared understanding of how the status system should work before we attempt a long refactor of the Pipeline status system. The first goal is to build a throwaway simulator that we can use to describe a Pipeline, the status of its steps and what the resulting stage, parallel and pipeline status should be. This is used to develop a set of scenarios that will be used to define the specification for the refactor. Before moving onto the real changes there must be consensus among the team that this is the desired behaviour.
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-47464) Prettier autoformating
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-47464 Prettier autoformating Change By: James Dumay Issue Type: Improvement Task Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-49774 NPE in Autofavorite plugin Change By: James Dumay Assignee: James Dumay Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49774) NPE in Autofavorite plugin
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49774 NPE in Autofavorite plugin Vivek Pandey this one looks reasonably serious - perhaps the code needs to be more defensive for null user properties? Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title James Dumay commented on JENKINS-48588 Re: Artifacts uploaded to S3 does not show up in Blue Ocean Ilya Kulakov we query the run for its artifacts, transform them to a BlueArtifact model and display them. In order to get S3 plugin to display, you would need something like what I wrote in PR-113. I won't be implementing this but it should be a start for someone here who wants to. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49630) Unable to view configuration of some projects after upgrade to 2.107
Title: Message Title James Dumay commented on JENKINS-49630 Re: Unable to view configuration of some projects after upgrade to 2.107 Vivek Pandey not sure why our Blue Ocean preloader is running in this case - this appears to be rendering a classic jelly page. Something strange going on? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-47584 Result screen not refreshing with error "Cannot read property 'self' of undefined" Change By: James Dumay Sprint: Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2 , Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47584) Result screen not refreshing with error "Cannot read property 'self' of undefined"
Title: Message Title James Dumay commented on JENKINS-47584 Re: Result screen not refreshing with error "Cannot read property 'self' of undefined" Vivek Pandey the last report by Jesús Lunar Pérez looks like a SSE problem. An event is coming in, updating the run information but we might not have a reference... perhaps the bunker here needs to be more resiliant to those problems? WDYT Josh McDonald? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47897) Blue Ocean pipeline view shows stages and steps from previous build, until given step starts
Title: Message Title James Dumay commented on JENKINS-47897 Re: Blue Ocean pipeline view shows stages and steps from previous build, until given step starts John Hus theres nothing like that right now. We'd be happy to accept a PR for that if you or someone else had the time. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title James Dumay reopened an issue Vivek Pandey - Jim Klimov has provided some HARs and a support bundle, so it should be possible to see the problem he is experiencing now. Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: James Dumay Resolution: Duplicate Status: Resolved Reopened Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title James Dumay edited a comment on JENKINS-41488 Re: Pipeline view automatically scrolls down [~kordzik] yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour. Also, hello - great to see that you're a Blue Ocean user now :) Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41488) Pipeline view automatically scrolls down
Title: Message Title James Dumay commented on JENKINS-41488 Re: Pipeline view automatically scrolls down Dariusz Kordonski yes, it automatically scrolls there on a failed run by design. I'd need to get some more feedback from users before we went ahead and changed this behaviour. Also, hello Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title James Dumay commented on JENKINS-48588 Re: Artifacts uploaded to S3 does not show up in Blue Ocean Ben Dean I stand corrected then We use the standard API for retrieving the artifacts, perhaps the display of the S3 artifacts is custom somehow? Would be worth someone investigating. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: James Dumay Priority: Critical Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45334) REGRESSION "input parameter not support go to classic link" does not work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-45334 REGRESSION "input parameter not support go to classic link" does not work Change By: James Dumay Priority: Critical Major *Scope** Fix so that the link is valid* Add a test*Original request* In case BO does not support some parameters you will be redirected to classic. That redirect does not work. The href is empty.You can test with https://github.com/scherler/jenkins-testfiles the `JENKINS-40617` branch provides an example for input in a pipeline. When you go into the detail view of the pipeline you will see the link on a paused for input biuild. !Screenshot from 2017-07-06 12-33-52.png|thumbnail! BTW the parametrized unsupported like `JENKINS-40617-param` branch still works as expected. !Screenshot from 2017-07-06 12-44-33.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-46571) Update URL scheme to remove URL encoding issues
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-46571 Update URL scheme to remove URL encoding issues Change By: James Dumay Sprint: Blue Ocean 1.5 - Candidates beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45334) REGRESSION "input parameter not support go to classic link" does not work
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-45334 REGRESSION "input parameter not support go to classic link" does not work Change By: James Dumay Sprint: Blue Ocean 1.5 - Candidates beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45614) Activity tab is really slow
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-45614 Activity tab is really slow Change By: James Dumay Sprint: Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.2, Blue Ocean 1.5 - Candidates beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: James Dumay Sprint: Blue Ocean 1.5 - Candidates beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49297) input step in post directive is never prompted within Blue Ocean
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49297 input step in post directive is never prompted within Blue Ocean Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49189) Invalid pipelines cannot be edited and fail to show errors
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49189 Invalid pipelines cannot be edited and fail to show errors Change By: James Dumay Sprint: Blue Ocean - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49298) Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page
Title: Message Title James Dumay assigned an issue to Nicolae Pascu Jenkins / JENKINS-49298 Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page Change By: James Dumay Assignee: Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49298) Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49298 Using "t" key switches focus to search box, when running a build with param entry field on blue ocean home page Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 2 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49477) Javadoc generation is failing in master
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49477 Javadoc generation is failing in master Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48879) User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages.
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-48879 User is trapped if a parallel stage is skipped. Blueocean shows "Waiting for run to start" instead of log messages. Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 2 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49477) Javadoc generation is failing in master
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49477 Javadoc generation is failing in master Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build
Title: Message Title James Dumay commented on JENKINS-49348 Re: BlueOcean misses a button to re-run a build Jim Klimov is this for Pipeline jobs or other kinds of jobs? A Jenkinsfile example would help here if its a Pipeline job. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49286) The Pipeline view is not showing the runs or the stages most of the times in Blue Ocean
Title: Message Title James Dumay resolved as Cannot Reproduce Sourajyoti Bose are there any errors in the console that you could show us? We don't have any information on this ticket that can help us diagnose. Please reopen when you have provided additional formation. Thanks James Jenkins / JENKINS-49286 The Pipeline view is not showing the runs or the stages most of the times in Blue Ocean Change By: James Dumay Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to
[JIRA] (JENKINS-48849) No downstream links in Blue Ocean with Bitbucket Multibranch
Title: Message Title James Dumay resolved as Duplicate Duplicate of JENKINS-38339 which is in progress. Jenkins / JENKINS-48849 No downstream links in Blue Ocean with Bitbucket Multibranch Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-48673) Nodes status are not displayed correctly after aborting an input step
Title: Message Title James Dumay resolved as Duplicate Darío Villadiego at the moment we are unable to accurately reflect the correct status of some stages and nodes. JENKINS-39203 is the umbrella ticket for all of these issues and is on our roadmap to solve. Jenkins / JENKINS-48673 Nodes status are not displayed correctly after aborting an input step Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-48588 Artifacts uploaded to S3 does not show up in Blue Ocean Change By: James Dumay Component/s: blueocean-plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48588) Artifacts uploaded to S3 does not show up in Blue Ocean
Title: Message Title James Dumay commented on JENKINS-48588 Re: Artifacts uploaded to S3 does not show up in Blue Ocean Ilya Kulakov I see though I don't think thats the intent of the S3 plugin to display uploaded artifacts. There is an extension point to do that in Blue Ocean (BlueArtifact and BlueArtifactFactory) but it would have to be provided by the S3 plugin. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: James Dumay Sprint: Blue Ocean - Candidates Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48820) Blue Ocean plug-in causes stack overflow for big pipeline jobs
Title: Message Title James Dumay assigned an issue to Vivek Pandey Vivek Pandey small one that would be good to fix. Jenkins / JENKINS-48820 Blue Ocean plug-in causes stack overflow for big pipeline jobs Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48393) Blue Ocean's 'Tests' tab does not show archived test results (generated by py.test) from a Pipeline's 'junit' step
Title: Message Title James Dumay resolved as Cannot Reproduce Giles Gaskell I was unable to reproduce this one. Perhaps next time you are in the office you can show me? Jenkins / JENKINS-48393 Blue Ocean's 'Tests' tab does not show archived test results (generated by py.test) from a Pipeline's 'junit' step Change By: James Dumay Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop
[JIRA] (JENKINS-47897) Blue Ocean pipeline view shows stages and steps from previous build, until given step starts
Title: Message Title James Dumay resolved as Won't Do Greg Dubicki yes, what you are seeing is desired behaviour for most users as many have reasonably static Pipeline elements (e.g. stages stay the same name, are not dynamically created). As we used a scripted language, we can't "read ahead" of the Pipeline without first executing the Pipeline, so we make assumptions that the Pipeline hasn't really changed since the previous run. In your case, we can't make that assumption due to the very dynamic nature of your Pipeline. Ill be marking this ticket as "wont' do" because I am hesitant of changing this behaviour today as this has an unknown impact on other users. However, I would like to look at this again if we receive a few more reports of this issue. We can reopen this ticket when the time comes. Thanks for reporting and sorry I was unable to help this time. Jenkins / JENKINS-47897 Blue Ocean pipeline view shows stages and steps from previous build, until given step starts Change By: James Dumay Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA
[JIRA] (JENKINS-47423) Problem with adding/removing github repositories after upgrade to BlueOcean 1.3
Title: Message Title James Dumay resolved as Not A Defect Hai Nguyen we decided to remove theautomatic scanning of Github organizations in 1.3. They were removed because: Inflexibility - Developers cannot change settings for an individual Pipeline that is contained in an Organization Folder. To change any setting related to the Pipeline the user must change this at an Organization Folder level and this will apply the change to all Pipelines contained within it. This means that individual projects cannot have their own project settings and puts severe practical limits on the utility of this feature. Utility jobs that are not linked to a repository within the organization cannot be placed with an organization folder which limits its use as an Pipeline categorisation structure. Inconsistency - Blue Ocean is attempting to walk back from large hierarchies of nested folders which are proven to be a user experience problem in Jenkins Classic. Organization Folders show as legacy folders in the Blue Ocean dashboard and we've been unable to come up with a design that correctly rationalises this usage of folders. This means Organization Folders are inherently inconsistent with the way that Blue Ocean works today. There needs to be more user experience research here to rationalise this inconsistency. Low usage - There is little evidence to suggest that there is usage of this feature among adopters of Blue Ocean that use Github. However, creating singular Pipelines is well used. It will require a high level of investment to support Bitbucket and Gitlab organization folders for very little usage upside. This is not surprising as the organization folders feature is built for advanced users and the majority of users being on-boarded on to Pipeline through Blue Ocean are at the beginning of their Pipeline adoption journey. I think we could have communicated this much better and you have my sincere apologies for the confusion. Thanks James Jenkins / JENKINS-47423 Problem with adding/removing github repositories after upgrade to BlueOcean 1.3 Change By: James Dumay Status: Open Resolved Resolution: Not A Defect
[JIRA] (JENKINS-46532) Got "Error rendering PipelineRunGraph: TypeError: nodeStage is undefined" when removed steps from previous run
Title: Message Title
James Dumay commented on JENKINS-46532
Re: Got "Error rendering PipelineRunGraph: TypeError: nodeStage is undefined" when removed steps from previous run
Nat Sr dont use the script block to do things like setting the current build result. Try something like this instead:
// Good practice to split your scripts out into functions, improves readability
def sendEmail() {
mail body: "unable to open",
from: "t...@aloha.com",
replyTo: "",
subject: "CANNOT OPEN GOOGLE PHOTOS!!!",
to: "t...@aloha.com"
}
stages {
stage('1) Test') {
steps {
input 'Test open google Photots\n\n' +
'1) Open https://www.google.com/search?q=photo+test=lnms=isch=X=0ahUKEwiK172Zp_PUAhUHrVQKHeD4CREQ_AUICigB=1421=895\n' +
'2) Please open one of these photos and see which one you like\n\n\n\n' +
'Click "Proceed" to continue'
}
post {
failure {
sendEmail()
}
}
}
}
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49347) BlueOcean unusably slow, maybe related to having a lot of builds stored in history
Title: Message Title James Dumay resolved as Duplicate Jim Klimov Ill close this against the issues quoted by Vivek Pandey (likely to be the cause). However, would be great to capture a HAR file of specific page loads and capture a support bundle to help us diagnose these problems. We know there are optimizations to be make but we need specific info Jenkins / JENKINS-49347 BlueOcean unusably slow, maybe related to having a lot of builds stored in history Change By: James Dumay Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) --
[JIRA] (JENKINS-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title James Dumay commented on JENKINS-49569 Re: Pipeline archives artifacts with weird untraceable folder name It uses double encoding of the URL to escape non-URL safe characters as these characters may not be compatible with all filesystems. The best practice here would be to create an archive (zip/tar/etc) and publish it directly to an artifact repository like SonaType Nexus or JFrog Artifactory. If you just want to use plain old Jenkins, I'd use a archive (zip/tar/etc) with a well known name. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49569) Pipeline archives artifacts with weird untraceable folder name
Title: Message Title James Dumay resolved as Not A Defect Jenkins / JENKINS-49569 Pipeline archives artifacts with weird untraceable folder name Change By: James Dumay Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49605) Add BLUE_OCEAN_BUILD_URL environment variable to builds
Title: Message Title James Dumay resolved as Not A Defect Adam Dougal you can use RUN_DISPLAY_URL or JOB_DISPLAY_URL to point to the users preferred setting of UI - Blue Ocean or Classic Jenkins / JENKINS-49605 Add BLUE_OCEAN_BUILD_URL environment variable to builds Change By: James Dumay Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-49519) Limit the amount of analytics data being collected
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-49519
Limit the amount of analytics data being collected
Issue Type:
New Feature
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2018-02-12 23:05
Priority:
Minor
Reporter:
James Dumay
We need a method to limit the amount of analytics data being collected. This config kept on jenkins.io. It expresses that there are 1000 cohorts, of which 10 are active (1% of the Jenkins server install base).
{
"cohorts": 1000,
"activeCohorts": [
"0-9"
]
}
The server will decide based on its server identity if it is enrolled into the range 0-9 or not
Add Comment
[JIRA] (JENKINS-49519) Limit the amount of analytics data being collected
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49519 Limit the amount of analytics data being collected Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45634) Table action buttons hidden until hover
Title: Message Title James Dumay assigned an issue to Nicolae Pascu Jenkins / JENKINS-45634 Table action buttons hidden until hover Change By: James Dumay Assignee: James Dumay Nicolae Pascu Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48119) editing the existing declarative jenkinsfile in pipeline editor
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48119 editing the existing declarative jenkinsfile in pipeline editor Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48027) Blue Ocean dashboard showing no Pipelines
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48027 Blue Ocean dashboard showing no Pipelines Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48277) Clicking on a pipeline name should default to branch tab instead of activity
Title: Message Title James Dumay resolved as Won't Do Jenkins / JENKINS-48277 Clicking on a pipeline name should default to branch tab instead of activity Change By: James Dumay Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49419) Avoid detached head on checkout
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-49419 Avoid detached head on checkout Change By: James Dumay Sprint: Blue Ocean 1.5 - beta 1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48204) NPE in BlueOcean REST API / JIRA interaction
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-48204 NPE in BlueOcean REST API / JIRA interaction Change By: James Dumay Assignee: James Dumay Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42994) In some situations, the 're-run' button will not trigger a build and not give any feedback of failure.
Title: Message Title James Dumay commented on JENKINS-42994 Re: In some situations, the 're-run' button will not trigger a build and not give any feedback of failure. Hurrah! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43259) Parameterised form is sometimes unstyled
Title: Message Title James Dumay commented on JENKINS-43259 Re: Parameterised form is sometimes unstyled Thorsten Scherler Cliff Meyers would either of you know whats going on here? A contributor sent in a fix but I think there is something odd going on here that isn't a missing style... https://github.com/jenkinsci/blueocean-plugin/pull/937 ? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43259) Parameterised form is sometimes unstyled
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43259 Parameterised form is sometimes unstyled Issue Type: Bug Assignee: Unassigned Attachments: problem.png Components: blueocean-plugin Created: 2017/Mar/31 5:03 AM Priority: Major Reporter: James Dumay Problem Steps to reproduce Create a new project. In my case it's Pipeline one, but shouldn't matter. Make build parameterized. Add any parameter with a text description. The rest options are irrelevant. Make sure there were no builds for this project made. Otherwise form will inherit right styles from build log. Open project in Blue Ocean and hit the button Run. You should see no description text in dialog form, but you can select it to make visible for you. Found by Alexander Shorin
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI* * Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter.** Creation*** New Pipeline button*** credential API needs to be re-scoped under {{/rest/organizations/$org}}*** SCM API needs to be re-scoped under {{/rest/organizations/$org}}* Update ATH to run blue ocean with a random organization name*Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI** Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter.** Creation*** New Pipeline button*** credential API needs to be re-scoped under {{/rest/organizations/$org}}*** SCM API needs to be re-scoped under {{/rest/organizations/$org}} * Update ATH to run blue ocean with a random organization name *Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI** Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter.** Creation*** New Pipeline button*** credential API needs to be re-scoped under {{/rest/organizations/$org}}*** SCM API needs to be re-scoped under {{/rest/organizations/$org}}*Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43256) SSE should be organization aware
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43256 SSE should be organization aware Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:45 AM Labels: techical-debt cloudbees-internal-steel Priority: Minor Reporter: James Dumay TBD Vivek to fill in Add Comment
[JIRA] (JENKINS-37841) Unable to open log due to missing JWT token
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37841 Unable to open log due to missing JWT token Change By: James Dumay Summary: Inable Unable to open log due to missing JWT token Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37841) Inable to open log due to missing JWT token
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37841 Inable to open log due to missing JWT token Change By: James Dumay Summary: REGRESSION: unable Inable to open log due to missing JWT token Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Error handling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Error handling Change By: James Dumay Sprint: 1.0-m10, 1.0-b05/b-06, Blue Ocean up next 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Error handling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Error handling Change By: James Dumay Priority: Critical Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36083) Error handling
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36083 Error handling Change By: James Dumay *Design Brief*Blue Ocean makes a lot of asynchronous rest calls and any of them could fail at any time.There are two cases here I think we need to handle:* When a whole page fails to render* When one of the AJAX calls fails with 500/503/502 we should show the error screen *In Scope** Design for both the cases above* Decide what our error reporting should look like across the app.* Out of scope** 404 pages as they are already handled* Design** Whole page fails to render** Invision https://invis.io/648R3HVAV#/213891534_Error_-_500** Zeplin https://zpl.io/Z1hPPwx** AJAX Fail* Invision https://invis.io/648R3HVAV#/213891533_Error_-_AJAX_Fail* Zeplin https://zpl.io/21YQPC Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails
[JIRA] (JENKINS-43255) Make refresh behaviour organization specific
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43255 Make refresh behaviour organization specific Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:31 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Scope Introduce a new header to identify the organization used then have the UI honor the combination for refresh behaviour X-BLUE-REFRESH-TOKEN should be honoured to refresh the UI even in situations where X-BLUE-ORGANIZATION isn't sent For pages that are not org specific Example X-BLUE-ORGANIZATION: blueocean-team X-BLUE-REFRESH-TOKEN: $unique-token-for-blueocean-team
[JIRA] (JENKINS-43254) After login, sometimes the UI does not get updated when the token is provided
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43254 After login, sometimes the UI does not get updated when the token is provided Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:28 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Problem After login redirection, BO UI doesn't update Login button to Logout. Either it doesn't call get token API, or it doesn't update Login to Logout. Refresh of page display Logout button correctly. Add Comment
[JIRA] (JENKINS-43253) When JWT token cannot be issued or is invalid the screen is blank
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43253 When JWT token cannot be issued or is invalid the screen is blank Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:25 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Problem When JWT token cannot be issued or is invalid the screen is blank What should happen The UI should redirect to the login screen Add Comment
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI** Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter.** Creation*** credential API needs to be re-scoped under {{/rest/organizations/$org}}*** SCM API needs to be re-scoped under {{/rest/organizations/$org}} *** *Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-37841) REGRESSION: unable to open log due to missing JWT token
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37841 REGRESSION: unable to open log due to missing JWT token Change By: James Dumay Sprint: pacific, 1.0-b05/b-06 , Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37841) REGRESSION: unable to open log due to missing JWT token
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-37841 REGRESSION: unable to open log due to missing JWT token Change By: James Dumay *Scope** Ensure when getting the raw log or an artifact that we are able to download it when JWT is enabled*Problem* Go to any job, and try to download or view the log in a new tab. You will see a missing JWT token error. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43252) lastSuccessfulRun URL should be relative
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43252 lastSuccessfulRun URL should be relative Issue Type: Bug Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/31 1:19 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Scope lastSuccessfulRun URL is absolute "lastSuccessfulRun": "https://ci.blueocean.io/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/815..." Make it relative: "lastSuccessfulRun": "/blue/rest/organizations/jenkins/pipelines/blueocean/branches/master/runs/815/", Notes There may be frontend help needed to fullfil this ticket.
[JIRA] (JENKINS-43252) lastSuccessfulRun URL should be relative
Title: Message Title James Dumay assigned an issue to Vivek Pandey Jenkins / JENKINS-43252 lastSuccessfulRun URL should be relative Change By: James Dumay Assignee: Vivek Pandey Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43251) All links to the dashboard should link to the organization dashboard
Title: Message Title
James Dumay created an issue
Jenkins / JENKINS-43251
All links to the dashboard should link to the organization dashboard
Issue Type:
Bug
Assignee:
Unassigned
Components:
blueocean-plugin
Created:
2017/Mar/31 1:17 AM
Labels:
technical-debt cloudbees-internal-steel
Priority:
Major
Reporter:
James Dumay
There are two "dashboards"
The global dashboard at {{/blue/pipelines}
The organization dashboard /blue/organizations/jenkins/pipelines
We should remove the global dashboard and ensure that all links to the dashboard to link to / and let the redirect handle this correctly. The extension point introduced in JENKINS-43250 will handle redirection to the correct location. In Scope
Remove the code for the global dashboard completely
Update all the links to the deleted dashboard to point to root /
[JIRA] (JENKINS-43250) Landing page route is made extensible
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43250 Landing page route is made extensible Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:13 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Scope Landing page route is made extensible Blue Ocean implements that extension point to redirect to /blue/organizations/jenkins/pipelines Today we redirect to /blue/pipelines but we should redirect to /blue/organizations/jenkins/pipelines Notes The default landing page (redirect form / to /pipelines) is hard coded and not extensible. BO needs to allow landing page to be changed to a different component by BS Add Comment
[JIRA] (JENKINS-43249) Requesting classes that don't exist on the classpath should return empty array
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43249 Requesting classes that don't exist on the classpath should return empty array Issue Type: Bug Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:09 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Scope If a type is not found via /classes then it should return with an empty array instead of failing with a 404 Notes BO classes API shouldn’t fail hard if it sees a class that it cannot load. Instead it reports empty array or something so that frontend can gracefully ignore that type Add Comment
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI** Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter.** Creation – *** credential API needs to be re-scoped under {{/rest/organizations/ $org }}** * SCM API needs to be re-scoped under {{/rest/organizations/$org}}*** *Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title
James Dumay updated an issue
Jenkins / JENKINS-43248
Remove hardcoding of the jenkins organization from the UI
Change By:
James Dumay
*Scope** Remove hardcoding of the "jenkins" organization from the UI** Known places that hardcode:** Loading user info - Deprecate the root user API {{/rest/users}} and update references to use {{/rest/organizations/$org/users/}}** Dashboard - Make {{/rest/search/}} require organization as a parameter. ** Creation – credential API needs to be re-scoped under {{/rest/organizations/}} * * * Notes*This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources.*Discovering hard coded organizations*# Update the default organization name to be "blue-ocean"# Run the tests and ATH against the branch and find test failures
Add Comment
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
[JIRA] (JENKINS-43248) Remove hardcoding of the jenkins organization from the UI
Title: Message Title James Dumay created an issue Jenkins / JENKINS-43248 Remove hardcoding of the jenkins organization from the UI Issue Type: Task Assignee: Vivek Pandey Components: blueocean-plugin Created: 2017/Mar/31 1:06 AM Labels: technical-debt cloudbees-internal-steel Priority: Major Reporter: James Dumay Scope Remove hardcoding of the "jenkins" organization from the UI Known places that hardcode: Loading user info - Deprecate the root user API /rest/users and update references to use /rest/organizations/$org/users/ Dashboard - Make /rest/search/ require organization as a parameter. Notes This ticket may uncover frontend work. The UI needs to remove all uses of hardcoded 'jenkins' organization and work with HAL links. This is extremely important and goes long way to make UI work with whatever backend says in terms of where to find resources. Discovering hard coded organizations Update the default organization name to be "blue-ocean" Run the tests and ATH against the branch and find test failures
[JIRA] (JENKINS-42173) Blue Ocean SDK design document - extensibility improvements
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42173 Blue Ocean SDK design document - extensibility improvements Change By: James Dumay We want an SDK experience for developing Blue Ocean plugins, should document/research aims and goals*Goals* * Public API * Typed extension points * Improved module resolution * Improved module versioning (e.g. we don't have to keep bundling common libraries into Blue Ocean) * Write "_javascript_ only" plugins without maven * Integration with maven-hpi-plugin * Typescript investigation * Use of tree API to avoid fetching unwanted actions Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay Attachment: #1 2017-03-31 10-14-15.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay Attachment: #1 2017-03-31 10-14-53.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay *Problem*Blue Ocean should display information about which node it executed the stage on.*Design brief*A stage is always executing on a node and it is useful for developers to know what particular node is being executed on. There are a few options here:* Add a synthetic step to say where the stage is executing* Add this information to the step header on the result summary * !node.png|thumbnail! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay Attachment: node.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay Attachment: #1 2017-03-31 10-14-53.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay *Problem* Blue Ocean UI should display information about which node it executed the stage on. *Design brief*A stage is always executing on a node and it is useful for developers to know what particular node is being executed on. There are a few options here:* Add a synthetic step to say where the stage is executing* Add this information to the step header on the result summary* Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-41829) Developer can see the node the stage is being executed on
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-41829 Developer can see the node the stage is being executed on Change By: James Dumay Attachment: #1 2017-03-31 10-14-15.png Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35836) Steps outside a stage or within a stage but outside a parallel do not get visualized
Title: Message Title James Dumay closed an issue as Won't Do Jenkins / JENKINS-35836 Steps outside a stage or within a stage but outside a parallel do not get visualized Change By: James Dumay Status: Resolved Closed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43231) Running on message not present in Blueocean log
Title: Message Title James Dumay edited a comment on JENKINS-43231 Re: Running on message not present in Blueocean log Hi [~msieger],Unfortunately there is no good heuristic for us to show steps that happen outside a stage (see JENKINS-35836). However we are planning to surface this information a bit better where possible - for example, we might be able to display somewhere at the stage level on which node is executing. We are tracking that ticket work as JENKINS-41829.ThanksJames Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43231) Running on message not present in Blueocean log
Title: Message Title James Dumay commented on JENKINS-43231 Re: Running on message not present in Blueocean log Hi Marc Sieger, Unfortunately there is no good heuristic for us to show steps that happen outside a stage (see JENKINS-35836). However we are planning to surface this information a bit better where possible - for example, we might be able to display somewhere at the stage level on which node is executing. We are tracking that ticket as JENKINS-41829. Thanks James Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
