feat: gitlab, gitlab runners and web host playbooks #4
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
|
configs for gitlab runners are also simplified and use a different mechanism, they require much less effort to configure. |
k4black
changed the title
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.
I've added new roles for installing gitlab and latest version of runners with new authorization flow.
Playbooks will work on next version of gitlab server/runners automatically - they get latest version of the server/runners.
Documentation for automatic rollout on GCP is added in additional document.
Currently CI for checking of playbooks and for GitHub runners is not ready, but should be less work and will add this week.