Why would I choose to install Jenkins as a WAR file instead of using a
package installer?
--
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 jenkinsci-users+unsu
My opinion and Linux centric -
If you need a Jenkins installation that starts easily, runs easily, and
upgrades easily, and don't care as much about being able to repeatably
create that exact same installation and all its configuration on another
machine, use the package installer, especially the
The short answer is not with that API, we have the same issue several months
ago, this API exposes the message that it show in the logs, it is completely
useless to grab the labels. We initially try to parse the message but it has
several different patterns so we decided that way was error prone
Do you do that remotely? Like injecting a script using the jenkins-cli.jar?
I considered using the REST API to fetch the labels of the node referenced in
the "why" message, but that would be meaningful only if the node had a single
label.
For multiple labels, again, I would be unable to tell whi
You didn't mention the type of job you're using.
If you're using a Freestyle job, it should work exactly as you desire,
detecting changes on all the branches that match the wildcard. It works
that way for me on several jobs that I use. A Freestyle job processing
multiple branches tends to confus
Hi,
for the Bitbucket Branch Source plugin it´s straight-forward - but in
Bitbucket Server we have an old plugin (version 4.0.0) which is not
supporting multiple Jenkins right now :-(
How would you register other (legacy) jobs, like Freestyle jobs or standard
pipeline jobs? I haven´t found any
