c443e5e·Author: Joseph Parker·Closed by: Joseph Parker·2019-02-07
Description
This adds automated testing of pull requests using STFC’s Anvil Jenkins server.
When a pull request is created or updated, the tests do the following:
Checkout the repo and attempt to merge the source branch into the target branch.
If successful, build and run the test suite on the merged code.
There are currently five tests covering a couple of different configurations and compilers:
gfortran 7.2
gfortran 7.2, built with no library dependencies (no fftw, netcdf, etc)
gfortran 7.2, built without mpi
gfortran 4.8.5
Intel 17
The results of the tests are reported on the Pull Request page, and also in the Slack channel.
Note: We’ve actually had Jenkins testing for some time. However, since the Jenkins files were not in next, the tests checked-out the source branch, the target branch and the Jenkins branch. This meant that the repo wasn’t in a “clean” state, so that the merge test wasn’t exactly testing what would happen when the PR was merged.
This adds automated testing of pull requests using STFC’s Anvil Jenkins server.
When a pull request is created or updated, the tests do the following:
Checkout the repo and attempt to merge the source branch into the target branch.
If successful, build and run the test suite on the merged code.
There are currently five tests covering a couple of different configurations and compilers:
gfortran 7.2
gfortran 7.2, built with no library dependencies (no fftw, netcdf, etc)
gfortran 7.2, built without mpi
gfortran 4.8.5
Intel 17
The results of the tests are reported on the Pull Request page, and also in the Slack channel.
Note: We’ve actually had Jenkins testing for some time. However, since the Jenkins files were not in next, the tests checked-out the source branch, the target branch and the Jenkins branch. This meant that the repo wasn’t in a “clean” state, so that the merge test wasn’t exactly testing what would happen when the PR was merged.