Skip to main content

Timeline for How to safe restart Jenkins?

Current License: CC BY-SA 3.0

14 events
when toggle format what by license comment
Nov 19, 2021 at 19:43 comment added Cody "a pickle was not being rehydrated" o_O
Jan 20, 2021 at 3:21 answer added Kyle Taylor timeline score: 2
Feb 20, 2019 at 23:46 comment added Gi0rgi0s Jenkins is designed to not be affected by restarts. From my experience, it's possible that a build might fail due to a restart, but they are rare. Where I work we used to have to restart Jenkins regularly. We have every kind of job you can imagine, some small, some huge. Only once did we see a build fail where a pickle was not being rehydrated. After that, we always do safe restarts now.
Jan 11, 2019 at 9:47 answer added Subhash timeline score: 5
Jul 17, 2018 at 11:01 answer added Karthik Venkatesan timeline score: 2
Apr 18, 2018 at 9:57 answer added Muhammad Faizan-Ul-Haq timeline score: 1
Jan 26, 2018 at 9:26 history edited Pierre.Vriens CC BY-SA 3.0
Improve title
Jan 18, 2018 at 18:58 comment added jayhendren In theory, with a properly configured Jenkins instance running Pipeline jobs, you can restart the master or slave nodes whenever you would like. My experience says otherwise, however.
Jan 18, 2018 at 17:50 vote accept Alex
Jan 18, 2018 at 17:32 answer added Nakilon timeline score: 35
Jan 17, 2018 at 16:54 answer added Preston Martin timeline score: 12
Jan 17, 2018 at 16:47 comment added Tensibai Guess from the top of my head, but isn't disabling the slaves an option ? (as far as I remember it doesn't stop ongoing jobs but prevent additional jobs in the queue to be launched)
Jan 17, 2018 at 16:22 answer added eyalzek timeline score: 23
Jan 17, 2018 at 15:22 history asked Alex CC BY-SA 3.0