[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build

[devyn.goet...@code42.com (JIRA)]

Title: Message Title

Devyn Goetsch commented on JENKINS-49348   Re: BlueOcean misses a button to re-run a build The Replay button has caused mass confusion in my company. We've gone through a couple of iterations of jenkinsfiles.  The first iteration had many load commands, and upon replay the pipeline would never run properly On our current iteration we are generating jenkinsfiles on every run, and then loading a (possibly different) declarative pipeline into jenkins. In the simplest terms, something like: node('label') {   checkout scm   sh("./gradlew generate")   load("generated/Jenkinsfile") } This is problematic because when replay is kicked, load uses the script from the previous run, but it might be different due to state stored in external systems (namely artifact repositories) From the blue ocean UI users click the little button that looks like rebuild, but it replays and doesn't do what our users expect.  At this point we are sending out warnings to our users to never click replay, and never click the rerun button from blue ocean.  We are directing users to go back to te classic view and Rebuild or Build with Parameters.  However, that isn't a real solution.  What we really need is an ability to 1). disable replay and 2). instruct blue ocean to user "Rebuild" instead of "Replay". Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188213.1517590814000.5437.1572451380355%40Atlassian.JIRA.