Indicate 'merge conflict' in launchpad comments when ci/autolanding fails

Bug #1192265 reported by Francis Ginther
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
jenkins-launchpad-plugin
Triaged
Wishlist
Unassigned

Bug Description

This is a feature request to indicate when a ci or autolanding job fails due to a merge conflict directly in the launchpad comment posted by jenkins.

This would require some analysis of the console logs, which the tool does not do, but should be simple enough that we could report this error with high accuracy. Something like this:

FAILED: Autolanding
Reason: Detected merge conflict
More details in the following jenkins job:
http://jenkins.qa.ubuntu.com/job/libunity-autolanding/16/
Executed test runs:
    FAILURE: http://s-jenkins:8080/job/generic-cleanup-mbs/324/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/libunity-saucy-amd64-autolanding/11/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/libunity-saucy-armhf-autolanding/11/console
    FAILURE: http://jenkins.qa.ubuntu.com/job/libunity-saucy-i386-autolanding/11/console

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.