-
Task
-
Resolution: Unresolved
-
Minor
-
None
-
-
Evergreen - Milestone 1
As discussed in JENKINS-50540 The tooling for the complete flow of the PCT testing for essentials plugins is not yet complete, this ticket is to modify the testing flow of git plugin once all the tooling is in place.
The complete flow to implement is:
- Use the work on Custom war packager and JEP-305 to generate a war file that contains the SUT and the essentials plugins in the proper versions that means the ones defined in essentials BOM which as jglick stated before should be deployed to Artifactory on every production change.
- That war file is then fed into ATH and PCT
And apart from the plugins in the essentials umbrella we need to run the PCT for the plugins specified in JENKINS-50539
- is blocked by
-
JENKINS-47498 Select compatible plugin versions using a BOM
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
- relates to
-
-
- Fixed but Unreleased
-
-
-
- Resolved
-
-
-
- Closed
-
[JENKINS-51008] Complete the PCT flow started in JENKINS-50540 for git plugin
So, it seems there are some unstability on git-plugin current builds, so first step here will be to help with that if necessary as I do not want to change the current flow until is stable
Unstability has been solved apparently, also there are new facilities in pipeline-library provided by the always amazing oleg_nenashev that mostly implement all the desired flow, so starting with this again.
It seems the PCT docker image is not able to deal with multimodule plugins like BO, need to fix that, also there are a bunch of plugins not passing the PCT due to various reasons, I will create tickets to fix them (or I will remove from the list)
rarabaolaza vilacides I have created a PR for
JENKINS-51093with basic Incrementals support. Please let me know whether it's enough for you. Or do you needJENKINS-51094(automatic picking of latest releases)?