Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce a dynamic Jenkinsfile pipeline script to act similar to Travis CI script #947

Closed

Conversation

jimklimov
Copy link
Member

@jimklimov jimklimov commented Dec 28, 2020

This is a rough-draft setup that works in my local laptop-based testing across several VMs. On one hand this includes a fair bit of hardcoding to automate in the future, but on another already can serve to illustrate what we can achieve in this direction for addressing issue #869 if need arises (follows up from #946 in that regard, and from #823 overall)...

The resulting run in Jenkins new BlueOcean interface looks like this:

nut-jenkinsfile-869-screenshot

@jimklimov
Copy link
Member Author

jimklimov commented Dec 29, 2020

It seems the Jenkins BlueOcean interface (or the version I have) has a bug about not visibly marking failed steps wrapped into catchError() clauses (so that the whole matrix gets tested anyway). Marking with warnError() clauses works better:

nut-jenkinsfile-869-screenshot-warnError

FWIW, the bug situation in https://issues.jenkins.io/browse/JENKINS-64525 looks like this:

nut-jenkinsfile-869-screenshot-catchError-cropped

@jimklimov
Copy link
Member Author

This effort taught me quite a bit about limitations of the standard Matrix in Jenkins Pipelines, and led to development of our own hopefully-generic dynamatrix and a pipeline for NUT based on it. Parts of this PR went there.

@jimklimov jimklimov closed this Sep 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant