[ci] Generate Jenkinsfile from a template #10740
Merged
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
driazati
force-pushed
the
generate_jenkins
branch
from
1352d4d
to
83ead2e
Compare
driazati
added a commit
to driazati/tvm
that referenced
this pull request
Mar 23, 2022
This is needed for apache#10740
driazati
force-pushed
the
generate_jenkins
branch
from
83ead2e
to
120592b
Compare
areusch
pushed a commit
that referenced
this pull request
Mar 24, 2022
This is needed for #10740 Co-authored-by: driazati <driazati@users.noreply.github.com>
This uses `jinja2` to generate the Jenkinsfile. This is useful since it lets us both keep common functionality easy to define (i.e. iterate over all images and do something) while keeping the output easy to debug (you can look at the `Jenkinsfile` directly instead of trying to imagine what the Groovy interpreter will do). This will become more useful as we start to make CI more configurable, such as adding dynamic test sharding. This mostly introduces the infrastructure and makes some token changes to demonstrate the generation process, but already its use is shown since the parameters was missing an entry for the `ci_hexagon` image.
driazati
force-pushed
the
generate_jenkins
branch
2 times, most recently
from
56c0530
to
26ccc62
Compare
driazati
force-pushed
the
generate_jenkins
branch
from
26ccc62
to
3978950
Compare
|
The templated values come from code (https://github.com/apache/tvm/pull/10740/files#diff-670a379669fd3f1cde13bc32dbb2e1ea020fa2ceac1f1c43f4ecf4b6589bfa14R30) the This PR doesn't make too many actual changes so we can land it quickly to avoid having to rebase too much |
areusch
approved these changes
Mar 25, 2022
driazati
added a commit
to driazati/tvm
that referenced
this pull request
Mar 25, 2022
This was referenced Mar 29, 2022
pfk-beta
pushed a commit
to pfk-beta/tvm
that referenced
this pull request
Apr 11, 2022
This is needed for apache#10740 Co-authored-by: driazati <driazati@users.noreply.github.com>
pfk-beta
pushed a commit
to pfk-beta/tvm
that referenced
this pull request
Apr 11, 2022
* [ci] Generate Jenkinsfile from a template This uses `jinja2` to generate the Jenkinsfile. This is useful since it lets us both keep common functionality easy to define (i.e. iterate over all images and do something) while keeping the output easy to debug (you can look at the `Jenkinsfile` directly instead of trying to imagine what the Groovy interpreter will do). This will become more useful as we start to make CI more configurable, such as adding dynamic test sharding. This mostly introduces the infrastructure and makes some token changes to demonstrate the generation process, but already its use is shown since the parameters was missing an entry for the `ci_hexagon` image. * Address comments, fix CI with temporary workaround Co-authored-by: driazati <driazati@users.noreply.github.com>
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.
This uses
jinja2to generate the Jenkinsfile. This is useful since it lets us both keep common functionality easy to define (i.e. iterate over all images and do something) while keeping the output easy to debug (you can look at theJenkinsfiledirectly instead of trying to imagine what the Groovy interpreter will do). This will become more useful as we start to make CI more configurable, such as adding dynamic test sharding.This mostly introduces the infrastructure and makes some token changes to demonstrate the generation process, but already its use is shown since the parameters was missing an entry for the
ci_hexagonimage. This PR intentionally leaves more usage of the templates/variables to follow up PRs in order to keep this PR simple.cc @areusch