You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UQCSBot has a fairly simple Jenkins setup right now, it's just "run a bunch of shell commands in sequence". Unfortunately, the way it's set up means tests passing with a linting failure won't correctly write coverage reports and so it goes kaput.
We can do a lot of far more nuanced things WRT how to handle error cases in Jenkins features (rather than in shell scripts we write) if we use Jenkins Pipelines, and this would also fully document how our Jenkins job is configured.
The text was updated successfully, but these errors were encountered:
UQCSBot has a fairly simple Jenkins setup right now, it's just "run a bunch of shell commands in sequence". Unfortunately, the way it's set up means tests passing with a linting failure won't correctly write coverage reports and so it goes kaput.
We can do a lot of far more nuanced things WRT how to handle error cases in Jenkins features (rather than in shell scripts we write) if we use Jenkins Pipelines, and this would also fully document how our Jenkins job is configured.
The text was updated successfully, but these errors were encountered: