-
-
Notifications
You must be signed in to change notification settings - Fork 351
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
Introduce a dynamic Jenkinsfile pipeline script to act similar to Travis CI script #947
Conversation
…ecks case-insensitive
…en if named FS objects are symlinks to dirs
…or the current compiler/ABI version) so whether it should not be required
…stashing (and pre-clean files from earlier builds marked as read-only)
…roceed so we get the full picture
…or the current compiler/ABI version) so whether it should not be required
It seems the Jenkins BlueOcean interface (or the version I have) has a bug about not visibly marking failed steps wrapped into FWIW, the bug situation in https://issues.jenkins.io/browse/JENKINS-64525 looks like this: |
…ox_sh" as a single token
…round Groovy/Java limitation
…issues summary only
This reverts commit e085e75.
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. |
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: