I’ve been switching the Jenkins jobs over to pipelines. There are a few things that are changing now as a result from a user interface perspective.
Repo build status
You can now see a repo’s build status split out among branches and PRs:
Please ignore the “downstream tests” job status - this is the job that is triggered by downstream builds that want to test that e.g. a commit to the math repo works upstream with both CmdStan and Stan.
Job stages are now shown in the new pipeline UI like so:
(You get to this page by clicking on the
from the previous page)
You can see the logs here by clicking on a stage:
For debugging I also really like the pipeline steps view:
In this view you can click on the individual steps for just their console output:
The general job’s console output sometimes also has additional error messages, found here:
Retrying a job
Before, we would try to figure out the correct incantation to ask Jenkins to retest from the comments. While convenient if one remembered the correct incantation, often you had to click through and make sure it triggered anyway. Now the only way to retrigger a job is to go to the job page and click Build:
This will bring up a screen where you can input parameters. You only need to adjust these if you’re trying to test a specific branch combination across repos; otherwise leave them as their default values.
(I’ll add more text on this screen soon).
This will trigger the build and automatically update the PR’s status on github.
If there are any questions please ask them here! Thanks everyone.