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

Automatically run basic AWS flavor tests in CI


    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Critical Critical
    • evergreen
    • 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

            batmat Baptiste Mathus
            batmat Baptiste Mathus
            1 Vote for this issue
            2 Start watching this issue