[JIRA] [mercurial] (JENKINS-15806) Exit code of `hg pull` not checked

Tue, 25 Mar 2014 11:14:02 -0700

Since upgrading to 1.50, when my jobs get triggered for any reason other than a commit to the repository (e.g. an upstream trigger or a manual build) they get failed by the Mercurial plugin because the hg pull found no changes:

Started by user Andrew Johnson
[EnvInject] - Loading node environment variables.
Building on master in workspace /var/lib/jenkins/jobs/epics-pvaPy/workspace
[workspace] $ hg showconfig paths.default
[workspace] $ hg pull --rev default
pulling from http://hg.code.sf.net/p/epics-pvdata/pvaPy
no changes found
ERROR: Failed to pull
ERROR: Failed to pull
[WARNINGS] Skipping publisher since build result is FAILURE
Sending e-mails to: a...@aps.anl.gov
Notifying upstream projects of job completion
Finished: FAILURE



To get them to build in this state I have to wipe out the work-space so they get cloned again. This is a major problem which I'm pretty sure this change was responsible for, so I will be reverting to 1.49.
Change By: Andrew Johnson (25/Mar/14 6:11 PM)
Resolution: Fixed
Status: Resolved Reopened
Assignee: Rene Kroon Jesse Glick
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to