[
https://issues.apache.org/jira/browse/YETUS-681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16649741#comment-16649741
]
Allen Wittenauer commented on YETUS-681:
----------------------------------------
-001:
* This is a major reworking of how test-patch starts up and how Jenkins works
out of the box.
* Originally this was going to be broken up into multiple patches, but since it
was easier to test as a single unit that's how I'm patching it.
* One of the big goals I had in mind was to make test-patch as
"configuration-less" as possible.
The highlights:
- There is significantly less configuration required for known CI systems. To
prove that point:
- bundled control files for Jenkins, Travis CI, Gitlab CI, and Circle CI.
- New documentation section for CI systems
- New plug-in section for CI systems
- Several new hooks for CI systems
- New API to add environment variables to the docker run
- test-patch now makes an attempt to detect the build tool in use
Low lights:
- Dockerfile now sets JAVA_HOME
- github/gitlab _breakup_url supports another format
- github/gitlab bug fix for command line URLs
- gitlab needed a few other minor tweaks
- The --jenkins flag and a few other Jenkins-specific things have been either
removed or moved
- A bit of re-arranging how the BUILDMODE is determined since the CI systems
provide some hints. One nit here is that Gitlab CI is configured to always test
patches. Further work needs to get done to get it to know how to differentiate
full builds.
> Add robots plugin type
> ----------------------
>
> Key: YETUS-681
> URL: https://issues.apache.org/jira/browse/YETUS-681
> Project: Yetus
> Issue Type: New Feature
> Components: Test Patch
> Reporter: Allen Wittenauer
> Assignee: Allen Wittenauer
> Priority: Major
> Fix For: 0.9.0
>
> Attachments: YETUS-681.00.patch, YETUS-681.YETUS-15.001.patch
>
>
> Umbrella JIRA to rework how robots are used in the system
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
