Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-52581

Automatically run basic AWS flavor tests in CI

    XMLWordPrintable

Details

    • 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

          Activity

            batmat Baptiste Mathus created issue -
            batmat Baptiste Mathus made changes -
            Field Original Value New Value
            Epic Link JENKINS-49853 [ 188837 ]
            batmat Baptiste Mathus made changes -
            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}}
            jglick Jesse Glick added a comment -

            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.

            jglick Jesse Glick added a comment - 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.
            jglick Jesse Glick made changes -
            Link This issue relates to JENKINS-52304 [ JENKINS-52304 ]
            batmat Baptiste Mathus made changes -
            Assignee R. Tyler Croy [ rtyler ] Baptiste Mathus [ batmat ]
            batmat Baptiste Mathus made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            batmat Baptiste Mathus made changes -
            Rank Ranked higher
            batmat Baptiste Mathus made changes -
            Remote Link This issue links to "evergreen PR (Web Link)" [ 21194 ]
            batmat Baptiste Mathus made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            batmat Baptiste Mathus made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            batmat Baptiste Mathus made changes -
            Labels essentials essentials evergreen
            batmat Baptiste Mathus made changes -
            Labels essentials evergreen evergreen

            People

              batmat Baptiste Mathus
              batmat Baptiste Mathus
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: