> On 6. Dec 2019, at 21:02, Matt Sicker wrote:
>
> A low tech workaround for this would be using node labels to define
> which nodes have the graphical environment and which ones don't.
I wonder whether this is something that could be done automatically in
platformlabeler plugin. Probably
A low tech workaround for this would be using node labels to define
which nodes have the graphical environment and which ones don't.
On Fri, Dec 6, 2019 at 4:05 AM Adakar wrote:
>
> Hi Daniel,
>
> Thanks for the explanation and pointing this out :)
>
> Bingo! The access to a display is mandatory
Τη Δευτέρα, 4 Νοεμβρίου 2019 - 5:54:07 μ.μ. UTC+2, ο χρήστης Denis Mone
έγραψε:
>
> Hello.
> We have build-blocker plugin installed on our Jenkins installation in my
> company, and we discovered that the node level blocking does not work.
> Scheduling two mutually excluded jobs on the same
Very good post!
I reviewed it (approved) and will wait for one more review on the team before
it gets merged. Please note it may be a day or a few with a lot of people at
Jenkins World, please don’t think it’s getting ignored for a negative reason.
Thank kindly!
> On Dec 6, 2019, at 5:29 AM,
Cool, PR submitted: https://github.com/jenkins-infra/jenkins.io/pull/2700
Chris
On Thu, 5 Dec 2019, at 5:01 PM, Marky Jackson wrote:
> That is all you would need to do
>
> > On Dec 5, 2019, at 9:00 AM, Chris Kilding
> > wrote:
> >
> > Hello,
> >
> > My company has suggested I write a post
Hi Daniel,
Thanks for the explanation and pointing this out :)
Bingo! The access to a display is mandatory for the plugin to be executed
succesfully. That's exactly the reason why I wanted the plugin to stop the
execution if the agent is running as a service. Although information if it
is a
