Yes Daniel, when configured properly with "agent none" pipeline is not
occupying any executor and as you said it is not occupying notable
resources.
My Suggestions in this regard are below:
1. Adding a new status to the build called "Paused" besides to the
existing statuses Success, Failure, Aborted, Unstable.
2. In Blue Ocean theme, Status icon showing as Paused and where as if we
see the in the build history of the Job's placeholder the icon is blinking
forever until some one acted.
Blue Ocean it shows Pause icon
Build History it shows InProgress icon
May be above suggestions might be in your future active development list,
but just wanted to bring up now my observations.
-Suresh
On Friday, March 17, 2017 at 7:32:43 PM UTC+5:30, Daniel Beck wrote:
>
>
> > On 17.03.2017, at 11:40, Turbo Fredriksson <[email protected]
> <javascript:>> wrote:
> >
> > And with _a lot_ of commits (at the moment), there's going to be a lot
> of waiting...
>
> This doesn't cost notable resources if you do it right, i.e. outside node
> blocks.
>
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/d8cce40c-6b5a-4529-80f5-7317ebd4be57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
