I think you would want to restore the Jenkins home directory from a backup
you made prior to the upgrade.
On Thursday, November 3, 2016 at 5:15:13 AM UTC-5, MI wrote:
>
> How could we downgrade to earlier version in case of something went wrong
> after upgraded to newer version of Jenkins?
>
I've run a groovy script to disable all jobs before. Then, I just enable
the jobs I want to run. The problem with that, though is that Pipeline jobs
can't be disabled. So, I normally have to go into the test instance and
manually remove the triggers on the Pipeline jobs to keep them from
I think you can have the job run the "net use" command to tie credentials
to a fileshare, and then just copy like it's a regular file. Not sure how
you'd secure the credentials, though. Ansible, Puppet, or Windows DSC might
be other options to pursue.
On Tuesday, November 8, 2016 at 5:13:17
Sounds like the ssh command is failing. Maybe the password or private key
is wrong?
On Monday, November 14, 2016 at 10:28:20 AM UTC-6, Peter Berghold wrote:
>
> I have Jenkins running merrily on an Ubuntu box and want to set up a slave
> on an RHEL box.
>
> Created a script on the RHEL box
Maybe try setting it at 100 threads? That is the max it will do. Not sure
if setting it blank does the same thing or not.
On Monday, November 14, 2016 at 3:11:27 PM UTC-6, Josh Santangelo wrote:
>
> I’d love to stop polling, but with Jenkins behind our firewall and git
> outside of it, the
Here are some references for you:
https://support.cloudbees.com/hc/en-us/articles/230612967-Pipeline-The-pipeline-even-if-successful-ends-with-java-io-NotSerializableException
https://github.com/jenkinsci/pipeline-plugin/blob/master/TUTORIAL.md#serializing-local-variables
