[geeklog-devel] FYI: Known Mercurial/Jenkins problem on project.geeklog.net
dirk at haun-online.de
Tue Aug 5 04:33:08 EDT 2014
- Mercurial on the server has been updated for version 3.1
- all the Jenkins jobs are green again and seem to be working
I haven't had the time to do any more tests or implement the
autostart. But at least we should be operational again.
Quoting Dirk Haun <dirk at haun-online.de>:
> Just an FYI:
> 1) Our Jenkins was down since the recent security update of the
> server. There’s no automated restart of it (yet), and I forgot to
> start it manually. Will look into this ASAP.
> 2) Even before that, I noticed that there’s a problem with the
> automated checkouts that the Jenkins jobs are doing. The checkout
> (hg pull, etc.) seems to go through, but then Mercurial returns an
> error code, which aborts the job. This also happens when doing the
> same steps from the command line.
> My guess is that the current version of the Mercurial plugin for
> Jenkins is no longer compatible with the rather old Mercurial
> version that’s running on the server. I’ve asked pair.com support to
> upgrade it and will check if that fixes the problem.
> Until then, all the Jenkins jobs may report errors and probably
> won’t work. The Mercurial repository itself is not affected.
> I’ll keep you posted on the progress.
> geeklog-devel mailing list
> geeklog-devel at lists.geeklog.net
More information about the geeklog-devel