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

Automatically run AWS flavor tests in CI

    Details

    • Sprint:
      Evergreen - Milestone 2
    • Similar Issues:

      Description

      Problem statement

      JENKINS-52581 has introduced some basic smoke testing for the AWS flavor, but we can (and do) still miss a bunch of errors that will only ever be seen when spawning an actual instance and trying to trigger a build.

      Expected

      We must run an actual AWS flavor provisioning during each PR build. We must then trigger a build and check the agent does provision and the build succeeds.

        Attachments

          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 -
          Assignee Baptiste Mathus [ batmat ]
          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).

          ---

          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}}
          h3. Problem statement

          JENKINS-52581 has introduced some basic smoke testing for the AWS flavor, but we can (and do) still miss a bunch of errors that will only ever be seen when spawning an actual instance and trying to trigger a build.

          h3. Expected

          We must run an actual AWS flavor provisioning during each PR build. We must then trigger a build and check the agent does provision and the build succeeds.
          batmat Baptiste Mathus made changes -
          Sprint Evergreen - Milestone 2 [ 516 ]
          batmat Baptiste Mathus made changes -
          Labels evergreen evergreen technical-debt
          batmat Baptiste Mathus made changes -
          Labels evergreen technical-debt evergreen technical-debt testing

            People

            • Assignee:
              Unassigned
              Reporter:
              batmat Baptiste Mathus
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: