[YETUS-648] Robot Improvement Project

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Implemented
• Component/s: Precommit
• Assignee: Allen Wittenauer
• Reporter: Allen Wittenauer
• Created: 29/Jul/18 19:57
• Updated: 14/Dec/18 17:37
• Resolved: 14/Dec/18 17:37

Description

Upon deploying Yetus outside the ASF, it becomes obvious that there are a bunch of inter-related things that make the --jenkins and --robot flags way more powerful than they should be. They need to get broken apart and clarified as what they do. Proposal:

• potentially remove --jenkins from a required flag into something yetus auto-determines (e.g., JENKINS_URL is defined)
• remove --reset-repo from --robot
• remove --run-tests from --robot
• potentially remove --run-tests flag altogether given that unit/-unit in plugins should do the same thing
• change -robot and --sentinel checks from docker.sh into --docker something

In addition, YETUS-643 is part of this mess. It isn't viable to assume that ${HOME} is writable under a --robot or --jenkins universe.

Issue Links

• is part of: YETUS-681 Add robots plugin type
• is related to: YETUS-643 default custom maven repo should use workspace when in jenkins mode