Only redeploy the metadata tester on repo dispatch #4094
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
HebaruSan
added a commit
to HebaruSan/NetKAN-Infra
that referenced
this pull request
May 21, 2024
HebaruSan
added a commit
to KSP-CKAN/NetKAN-Infra
that referenced
this pull request
May 21, 2024
Trivial workflow edits to test KSP-CKAN/CKAN#4094
|
|
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.
Background
#3575, KSP-CKAN/NetKAN-Infra#267, and KSP-CKAN/xKAN-meta_testing#86 made it so the main CKAN repo would run its
deploy.ymlworkflow anytime we pushed changes to the Python code from the other two repos.Motivation
Currently the entire
deploy.ymlworklow is run, including some unnecessary jobs:ckan.exeandnetkan.exeto S3This takes a little more time and may unnecessarily mark some files as changed when they really aren't.
Changes
Now when
deploy.ymlis triggered fromNetKAN-InfraorxKAN-meta_testing, we only rebuild and push the metadata tester image (and run its dependencies). This is the only job that depends on the Python code from those other repos.