Joshua Hoblitt

Does PuppetX::Jenkins::Provider::Cli need to handle more exception types?

2

At present, `PX::J::P::Cli` only retries the CLI jar if the exception script matches one of the known authentication error strings. However, I occasionally see other exception messages which I suspect...

experimental types not catching all cli jar auth errors`

1

The `missing the Job/ExtendedRead permission` error message is not presently being handled. ``` $ /usr/bin/java -jar /usr/lib/jenkins/jenkins-cli.jar -s http://localhost:8080 get-job citest anonymous is missing the Job/ExtendedRead permission ``` ``` Debug:...

with and without auth. related to #710 #714 #715

The stderr/stdout of the swarm client is showing up in the journal but it is not listed as part of the service unit logs. Eg., `journalctl -u jenkins-slave`

In stead of forcing a jenkins daemon restart, it would be useful in some situations to block new builds from being started and to restart after currently running jobs finish...

The current logic for plugin management will not add or remove `.pinned` and `.disabled` files unless the declared and installed versions are out of sync.

Specifically, the management of nodes via `hudson.plugins.sshslaves.SSHLauncher`.