Repository navigation
ci: move the deploy job to the private ops repository - #23
Merged
Merged
Conversation
A self-hosted runner writes the machine name and the workspace path into its job log, and this repository's logs are public. The deploy scripts moved with it; this workflow only triggers the pipeline now.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The deploy job ran on a self-hosted runner. A self-hosted runner writes its own
name, the machine name and the workspace path into the job log, and the logs of
a public repository are readable by anyone. The first real deploy confirmed it.
The deploy now runs in a private repository. This workflow keeps the same
triggers and the promote option, and only sends the pipeline a dispatch. The
deploy scripts moved with the job.
Needs the
OPS_DISPATCH_TOKENsecret before the dispatch can work.