[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title James Dumay assigned an issue to Ivan Meredith Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Assignee: Cliff Meyers 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay resolved as Fixed Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Summary: Run modal to also accommodate queued items (and behaviour does not just runs) work as designed 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay assigned an issue to Cliff Meyers Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Assignee: Ivan Meredith Cliff Meyers 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Issue Type: Bug Improvement Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY reopened an issue Reopening after talking to James Dumay ... he wants to change how this works so that the run details modal also works with only having a queue item (i.e. without a run) and so we get rid of the "Started" toast. So we need to move the "OPEN" link to the "Queued" toast and zap the "Started" toast completely. That part is trivial. I suspect that the hard part is the refactoring of how the run modal works because it needs to be wired to the redux store in such a way as to accommodate the fact that it started life without a run (or with a "fake" run that only has a queueId and does not have a runId) and then morphs once the run actually becomes available. Sounds tricky, but maybe it's not so bad. Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Resolution: Cannot Reproduce Status: Closed Reopened Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed I'd imagine so. I think Ivan Meredith is working in that area at the moment. Michael Neale can you chime in here and clarify if someone is working on making the run modal work off of a queued item? 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed Fair enough. I'm fairly sure the run modal will only work with a run instance, which is not available at this point, so it will require refactoring so that it actually works off the queueId of the run Vs the runId ... I have a feeling it will get messy. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed I think the requirements may have not have been clear (my fault). When the user hits the run button the "Started OPEN" toast should show immediately (on successfully queuing the run). If we click the open link it should show the result details modal - doesn't matter what state it's in (from a users PoV queued is just another status - shouldn't be treated any differently though the backend does). 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed James Dumay that's what we had originally and you guys complained that there wasn't immediate feedback to the user acknowledging that they had pressed the run button. So you want to remove the "Queued" toast again and just have the "Started" one? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Imagine this use case: the queue is very long and my run won't be scheduled for another 10 minutes. I kick off my release build, use the toast to open the run while it is queued so I can monitor its progress as it goes from queued to running then done Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Ok so that's the problem right there - we don't want a queued toast at all. We want to see the run toast with an open link where you can open the queued item in the run modal. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed I just checked on dogfood and the OPEN link is there but, for some reason, doesn't open the run. I tried on a local clean BO and it does open it. My guess ... some issue with the REST API url. I'll create a ticket for that. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed James Dumay no ... please first verify (NOT ON DOGFOOD) that you do not see the OPEN link. I closed this because I'm fairly sure you saw this on a broken dogfood and didn't verify on a clean Jenkins. The OPEN link does/should appear on the "Started" toast popup. There are 2 toasts ... the "Queued" one after the queuing request and the "Started" one as soon as the run actually starts. There's no possible link for queued because there's no run yet. In fact most of the time you don't get to see the queued toast because the started toast comes in over it before you get a chance. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay commented on JENKINS-36424 Re: Run behaviour does not work as designed Tom FENNELLY good to know that this is working! We might want to reopen this - it's not as the designed specified. Missing the "OPEN" link when it says it's queued. 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-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY commented on JENKINS-36424 Re: Run behaviour does not work as designed I'm closing this as I'm quite sure this is an issue that was seen on the dogfood server (how many times have I seen it with out of date plugins etc) and not verified on a clean Jenkins. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY closed an issue as Cannot Reproduce Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-36424) Run behaviour does not work as designed
Title: Message Title Tom FENNELLY updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Tom FENNELLY Sprint: 1.0-beta-1 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Priority: Critical Blocker 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0- m14 m13 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay assigned an issue to Unassigned Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Assignee: Tom FENNELLY 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0- m13 m14 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0- m12 m13 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0-m12 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0-m12 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0-m12 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Sprint: 1.0-m11 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Priority: Blocker 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-36424) Run behaviour does not work as designed
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: Michael Neale *Reproduction steps*# Go to a branch tab# Click the run button of a branch# Toast pops up "queued"*Expected (as per JENKINS-35813)*# Go to a branch tab# Click on the run button of a branch # Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued stateThere is enough [data in the response|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#build-a-pipeline] to open a pipeline result in the queued state. *Additional issue*Also if I click on the run multiple times it will queue multiple times yet I get no feedback. In scope: * Tests to capture this 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay Priority: Major Blocker 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Change By: James Dumay * Reproduction steps * # Go to a branch tab# Click the run button of a branch# Toast pops up "queued" * Expected (as per JENKINS-35813) * # Go to a branch tab# Click on the run button of a branch # Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued stateThere is enough [data in the response|https://github.com/jenkinsci/blueocean-plugin/tree/master/blueocean-rest#build-a-pipeline] to open a pipeline result in the queued state. * Additional issue * Also if I click on the run multiple times it will queue multiple times yet I get no feedback. 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-36424) Run behaviour does not work as designed
Title: Message Title James Dumay created an issue Jenkins / JENKINS-36424 Run behaviour does not work as designed Issue Type: Bug Assignee: Tom FENNELLY Components: blueocean-plugin Created: 2016/Jul/05 12:11 AM Priority: Major Reporter: James Dumay Reproduction steps Go to a branch tab Click the run button of a branch Toast pops up "queued" Expected (as per JENKINS-35813) Go to a branch tab Click on the run button of a branch Toast pops up "OPEN" where clicking open will open the result modal for the run in the queued state There is enough data in the response to open a pipeline result in the queued state. Additional issue Also if I click on the run multiple times it will queue multiple times yet I get no feedback.
