fix: make review app URLs predictable #806
Draft
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.
Tip
This is a draft PR because the
--ephemeral-id
argument has not been added to Hako yet. We'll need that work to happen and then we'll also need to update the Hako version as part of this PR.Description
We now generate a hash based on the branch name and use this as a suffix on review app names. This means a couple of things:
This is good for a couple of reasons:
We can now hand the review app URL off to future jobs. This is important for the n-test and cyprus plugins which expect a URL in the
review
orstaging
state.We will stop creating a new review app for every commit, we're already seeing way too many review apps get created which is a problem while we don't have automatic deletion of old review apps.
Changes to a PR will deploy faster because most of the review app CloudFormation stack will have been created already - we'll be doing updates instead of fully creating a new stack on each commit.
See-also: CPREL-1300
Checklist:
feat(circleci): add support for nightly workflows
,fix: set Heroku app name for staging apps too