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.
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
Improve nightly build and deployment logic #3164
Improve nightly build and deployment logic #3164
Changes from 29 commits
06fda97
97a6089
e83334e
7cc0f18
ebb594b
b0f218e
9c597e9
1171321
f42e951
736476e
afc25af
273d173
fa0c044
fe5e224
b68bb63
eef0c62
c0f1be7
bf02f01
f225532
8892f39
85e9449
16445d4
ddfb861
9f98de6
b3b3f52
f989635
5f1228b
b457942
03f6e19
f409d8d
ac31f1e
2e6097c
de58851
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is doing what we want it to now. It's a tag, it's applied to the branch that we're going to build (not
main
which is checked out here).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sweet! Just to get this straight: we are tagging whatever this build gets kicked off on. Since this only triggers on
schedule
, andGITHUB_REF
gets munged todev
in that case, we will always be tagging whatever the latestdev
is withnightly-build-202x-xx-xx
.And then, when the nightly build succeeds, we can tell the
nightly
branch to point atnightly-build-202x-xx-xx
and everyone who downloads the most recent nightly build off AWS will know that that corresponds to thenightly
branch. But if they want to downloadnightly-build-202x-xx-xx
from AWS they will also be able to associate that with thenightly-build-202x-xx-xx
tag.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that's close, except that we only distribute the most recent nightly build and tagged releases to AWS. I imagine we would also have a copy of the most recent release in a
stable/
directory. So if you want to refer tonightly-202x-xx-xx
you would need to look at thegs://builds.catalyst.coop/nightly-202x-xx-xx
path where the last 30 days of nightly build outputs are stashed, regardless of whether they were successful or not. So if you want to look at nightly build outputs + the code that generated them, you can look at the GCS output, and the tagged commit that matches its name.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, right - that makes sense! Are there any barriers to distributing a few recent nightly builds on AWS as well as GCS?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have a limited storage quota on AWS, and I don't think we actually want the public looking at our nightly build outputs, which may or or may not correspond to successful runs.