[YETUS-229] split --jenkins up

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.2.0
• Component/s: Precommit

Release Note

<!-- markdown -->
User-impacting:
* Docker 1.6.0 or higher is now required.
* --robot has been added to provide the same functionality as the older --jenkins flags, but without the assumptions of actually running underneath Jenkins.
* --jenkins is now effectively --robot + some specific handling in messages and instances when running under Jenkins.
* --sentinel has been added to provide cleaning of non-Yetus-based Docker containers and images. It automatically enables --robot.
* --dockerdelrep has been added to only print what would be cleaned in --robot, --jenkins, and --sentinel.
* Options have been added to override the Jenkins-specific defaults for various settings:
  * --build-url to provide the base URL of the robot's web server
  * --build-url-console to provide the relative URL to the console for this run
  * --build-url-patchdir to provide the relative URL to the patch directory
  * --instance to provide a string for parallelization differentiation
* --console-urls option has been added to print locations using the --build-url on the console instead of absolute file system locations. This is useful when looking at the test-patch console via something like the Jenkins console so that locations become clickable.
* In rare situations, Docker images may not have been unique per run. This should now be fixed.
* The time reported for switching execution modes (reexec and docker) were missing. This should now be fixed.
* If --docker was the last option on the command line, it was not being removed when test-patch was being re-invoked inside the container. This should now be fixed.
* test-patch is now much better about telling you what options have been turned on. This is useful when looking at test-patch's console when the actual command line options may not be visible.
* Hadoop personality no longer has special options to run outside of it's Dockerfile on the ASF Jenkins.
* The default project is now set to 'unknown'.

Dev-impacting:
* A ton of Docker-specific arg handling has been moved out of test-patch and into docker.sh, where it really belongs.
* This removes a lot more hard-coded, ASF-specific Jenkins setup bits. In some cases it was simply removed and in others, configurable.
* New EXEC_MODES may be manipulated via the standard yetus_add_entry to list additional modes that test-patch may be running under. Note that this gets printed to the screen *very* soon in the bootstrap process.

• Flags: Important
• Assignee: Allen Wittenauer
• Reporter: Allen Wittenauer
• Created: 10/Dec/15 18:59
• Updated: 04/Feb/16 21:15
• Resolved: 04/Feb/16 21:15

Description

Really, --jenkins is keyed towards the ASF. It should really be split up into two or more chunks, one that is still specific to the ASF and at least one more that enables certain functionality independent of being on an ASF box (e.g., a --robot or --automated or whatever).

Issue Links

• contains: YETUS-224 dockermode timestamp isn't showing up properly in vote table