Hello,
I recently upgraded a Jenkins CI server from 1.516 (or so) to 1.553. For
some reason on this new Jenkins build my git SCM puller sees a 'new change'
about every hour or so. This causes a job to be triggered for each of the
projects throughout the hour.
There are no obvious messages in t
Hi ...
I need to run a job which might cause slave to disconnect from Jenkins
server for a while- currently if slave is disconnected job is immediately
marked as failed or aborted, is there a way to do this, I was thinking
about something like the follow:
1. send job to slave
2. go offline
3. r
Hi,
We're experiencing the same problem. Same symptoms.
In the attached image, you can see the memory start to increase immediately
following Jenkins' update. It OOMs two days later, then immediately starts
grabbing memory again. This is: Jenkins ver. 1.553.
Note that this instance is not runn