Details
-
Task
-
Status: Resolved (View Workflow)
-
Critical
-
Resolution: Fixed
-
-
Evergreen - Milestone 1
Description
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
Attachments
Issue Links
- relates to
-
JENKINS-52304 Make the plugin fully configurable via configuration-as-code
-
- Resolved
-
- links to
Activity
Field | Original Value | New Value |
---|---|---|
Epic Link |
|
Description |
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). |
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 |
This issue relates to |
Assignee | R. Tyler Croy [ rtyler ] | Baptiste Mathus [ batmat ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Rank | Ranked higher |
Remote Link | This issue links to "evergreen PR (Web Link)" [ 21194 ] |
Status | In Progress [ 3 ] | In Review [ 10005 ] |
Resolution | Fixed [ 1 ] | |
Status | In Review [ 10005 ] | Resolved [ 5 ] |
Labels | essentials | essentials evergreen |
Labels | essentials evergreen | evergreen |
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.