[SPARK-2912] Jenkins should include the commit hash in his messages

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: Build
• Assignee: Nicholas Chammas
• Reporter: Nicholas Chammas
• Created: 07/Aug/14 23:28
• Updated: 15/Aug/14 05:06
• Resolved: 15/Aug/14 05:06

Description

When there are multiple test cycles within a PR, it is not obvious what cycle applies to what set of changes. This makes it more likely for committers to merge a PR that has had new commits added since the last PR.

Requirements:

• Add the commit hash to Jenkins's messages so it's clear what the test cycle corresponds to.
• While you're at it, polish the formatting a bit.

Issue Links

• links to: [WIP] Open PR to have Jenkins include commit hash in GitHub messages
• links to: Example of current style of Jenkins QA messages
• links to: Example of new debug output when API call fails