You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@yetus.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2018/12/14 17:38:00 UTC
[jira] [Resolved] (YETUS-648) Robot Improvement Project
[ https://issues.apache.org/jira/browse/YETUS-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Allen Wittenauer resolved YETUS-648.
------------------------------------
Resolution: Implemented
I think all of this was done as part of YETUS-681. Closing.
> Robot Improvement Project
> -------------------------
>
> Key: YETUS-648
> URL: https://issues.apache.org/jira/browse/YETUS-648
> Project: Yetus
> Issue Type: Improvement
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
>
> 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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)