-
Task
-
Resolution: Done
-
Minor
-
-
Evergreen - Milestone 1
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies
Acceptance criteria
- For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies
- The run has to be against a TBD version of Jenkins core
- Latest one
- The one included in essentials
- Latest LTS
- What are the versions of the git-plugin dependencies to use? TBD cc jglick rarabaolaza oleg_nenashev
- For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from essentials.yml a war file generated from the new custom war packager tool using essentials.yml as source...
- depends on
-
JENKINS-50539 Determine critical plugins that depend on git-plugin
-
- Resolved
-
- is duplicated by
-
JENKINS-50516 Add the run PCT step to run on a PR basis to essentials
-
- Closed
-
- relates to
-
JENKINS-47498 Select compatible plugin versions using a BOM
-
- Resolved
-
-
JENKINS-51008 Complete the PCT flow started in JENKINS-50540 for git plugin
-
- In Progress
-
-
JENKINS-50598 Add support of running JTH with custom WAR
-
- Resolved
-
- links to
(3 links to)
[JENKINS-50540] add the runPCT step to the git-plugin on a PR basis
Epic Link |
New:
|
Link |
New:
This issue depends on |
Description |
Original:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] |
New:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] ** For example the ones included in essentials, the latest ones? |
Description |
Original:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] ** For example the ones included in essentials, the latest ones? |
New:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source |
Description |
Original:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source |
New:
We need to modify the git-plugin flow so it runs the PCT on PR basis for git-plugin and all the critical upstream dependencies *Acceptance criteria* * For every PR to the git-plugin there is a run of the PCT exercising all git-plugin upstream dependencies * The run has to be against a TBD version of Jenkins core ** Latest one ** The one included in essentials ** Latest LTS * What are the versions of the git-plugin dependencies to use? TBD cc [~jglick] [~rarabaolaza] [~oleg_nenashev] ** For example the ones included in essentials, the latest ones? Or more generally, what environment are we going to use for this PCT run? The UC, a custom UC generated from {{essentials.yml}} a war file generated from the new custom war packager tool using {{essentials.yml}} as source... |
Assignee | Original: R. Tyler Croy [ rtyler ] |
Link |
New:
This issue relates to |
Link |
New:
This issue relates to |
Remote Link | New: This issue links to "https://github.com/jenkinsci/jenkins-test-harness/pull/99 (Web Link)" [ 20378 ] |
Sprint | New: Essentials - Milestone 1 [ 511 ] |