ci_build.sh/Jenkinsfile-dynamatrix: constrain the sprawl of build cases (doc/distcheck) #1092
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lementations and refactor into a loop and case Should be helftul for networkupstools/jenkins-dynamatrix#4 eventually
…ot include docs and distcheck
… other scenarios) and withdocs:man (redundant) from "various builds"
…not yet run a witdocs:all (and are declared capable of man)
…eline.slowBuild goals and trade-offs
…iterate compiler variants, only OSes
…uilds without SSL
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Our two most expensive build types are distchecks and especially builds with docs. Notably, these are less about code quality and more about recipe quality vs. available non-compiler tools provided on the build workers (make implementation, asciidoc and friends) so we do not need to run them as many times as we have various compiler versions.
This PR aims to reign them in, reducing the redundant builds and those that bring little value for much CPU churn, and revising/documenting what different BUILD_TYPE scenario names do.
At the moment of posting, it does not yet address the calling of (docs-included) builds once per target OS, which is a separate goal that may come later in this or future PR.
Partially helps address networkupstools/jenkins-dynamatrix#4 as well, by refactoring ci_build.sh with that needed direction in mind. This does however bring in some more churn to BUILD_TYPE=default-all-errors by building not only openssl and/or nss implementations, but also without-ssl which exposed some minor faults fixed below.