Prerequisites
Make sure you have a version of git installed and have a GitHub account.
Setup
Fork the repository https://github.com/rhaas80/spin2020 into a repository of your own and clone your forked repository to your laptop.
Exercise
Add a new "Simple workflow" using the Action tab of you repository page on GitHub (this would be https://github.com/rhaas80/spin2020/actions/new for the demo repo).
Configure an action that outputs the commit hash of HEAD using the command git rev-parse and whose output it if a form similar to
HEAD is bb8c42de11e171e22a7df0615981608faf35ea4d
Once the action is in place on GitHub, add a line consisting of your name to README.md and commit it to trigger the workflow. Check that the workflow triggered and produced output on the Actions pane. You should see output similar to this:
Sending in results
Once done, please send me the URL of your repository on GitHub using my rhaas@illinois.edu email address.
Current Jenkins setup
As part of the project we would like to implement as much of the current functionality currently offered by Jenkins as feasible. You can have a look at a sample Jenkins report for a test run the resulted in some failures on: https://Albert:Einstein@build-test.barrywardell.net/job/EinsteinToolkit/1562/ using the user name Albert and password Einstein .
Items to replicate:
- identifying the updates to submodules that triggered each test run
- capture log output
- capture information which test failed and keep track of changes in the number of failing tests
- send email to Einstein Toolkit mailing list when tests start to fail and are no longer failing