[JIRA] (JENKINS-49348) BlueOcean misses a button to re-run a build
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
[JIRA] (JENKINS-56773) High master CPU usage introduced by Blue Ocean 1.14.0
Title: Message Title Devyn Goetsch commented on JENKINS-56773 Re: High master CPU usage introduced by Blue Ocean 1.14.0 This impacted our company and we had to do the same rollback. we went from 1.6.x to 1.14.0, the next work day jenkins became unresponsive under load, and our jvm monitoring told us that the blue ocean rest computers endpoint was using most of the cpu time. We rolled back to 1.13.2 and disabled the Blue Ocean Executor Info plugin and our Jenkins master is far more responsive and page loads for blue ocean are much lower. Our builds have 3 stages, the first one is a single stage, the second one has 3 parallel stages, and the third one has 50 parallel stages, 32 of which are computed dynamically and launched with the "node" step. Please revert the change to make the Blue Ocean Executor Info plugin a required dependency. I'm sure it would be okay on a smaller system, but for a system like ours it is untenable. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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.
