-
Task
-
Resolution: Fixed
-
Critical
-
-
Evergreen - Milestone 1
We must have some level of automated testing ASAP.
My plan is to introduce at least a third branch to test the AWS flavor locally: the Jenkins master should at least start (which can well be not the case with a missing plugin, or wrong CasC config files).
—
This is important for obvious general reasons, but also more specifically because for instance jglick is about to file a PR for the AWS flavor, and it's currently very hard to test if you are not involved deeply in the project. Some smoke tests should at least be available/done through the now usual make check
- relates to
-
JENKINS-52304 Make the plugin fully configurable via configuration-as-code
-
- Resolved
-
- links to
[JENKINS-52581] Automatically run basic AWS flavor tests in CI
Epic Link |
New:
|
Description |
Original:
We must have some level of automated testing ASAP. My plan is to introduce at least a third branch to test the AWS flavor locally: the Jenkins master should at least start (which can well be not the case with a missing plugin, or wrong CasC config files). |
New:
We must have some level of automated testing ASAP. My plan is to introduce at least a third branch to test the AWS flavor locally: the Jenkins master should at least start (which can well be not the case with a missing plugin, or wrong CasC config files). --- This is important for obvious general reasons, but also more specifically because for instance [~jglick] is about to file a PR for the AWS flavor, and it's currently very hard to test if you are not involved deeply in the project. Some smoke tests should at least be available/done through the now usual {{make check}} |
Link |
New:
This issue relates to |
Assignee | Original: R. Tyler Croy [ rtyler ] | New: Baptiste Mathus [ batmat ] |
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Rank | New: Ranked higher |
Remote Link | New: This issue links to "evergreen PR (Web Link)" [ 21194 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
For example I would expect that a PR introducing a typo in distribution/environments/aws-ec2-cloud/config/as-code/artifact-manager-s3.yaml would be marked as failed.