| Re: [mdt-papyrus.dev] Papyrus HIPP back to normal (Hopefully!) |
|
Hi Camille, I don’t think that the SysML jobs have this kind of problem since the repository is smaller.
But in any case we have 2 jobs on the daily basis : Should we change them ?
By the way, I added the planning to the view description [1]. ð
It may be interesting to do that for all views ?
There is a Jenkins plugin that can show the cron trigger [2]. Does anyone know if there is a similar Hudson one that can display the git trigger ? Regards, Benoit 1 :
https://hudson.eclipse.org/papyrus/view/Sysml/ 2 :
https://wiki.jenkins-ci.org/display/JENKINS/Cron+Column+Plugin De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all, As you probably have noticed, we’ve had some trouble with our Hudson instance for the past weeks, which became completely unresponsive and required frequent restarts. It seemed to be related to a deadlock in SCM polling for Hudson 3.2.x. We can’t update to Hudson 3.3.x yet, so I’ve changed the SCM polling timers to avoid having 2 jobs polling Git at the same time (Thus avoid any deadlock). Note that this is just a workaround, so please be careful when configuring new jobs: if you use SCM polling as a job trigger, choose a time that is not already used by another job (Be extra-careful when copy-pasting jobs
for specific feature branches) Thanks, |