New runner and docker recipes #123
Open
Conversation
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
|
Just changed it to use the "default" Docker service instance of a "gitlab" instance. The per-instance stuff seems a bit broken and it's just counter-productive in this case. |
packages.gitlab.com actually runs on packagecloud.
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.
We're setting up some CI stuff here. We haven't put it into production yet but thought I'd put this out there now anyhow. There's a lot less to these recipes than I thought there would be, thanks largely to the packagecloud and docker cookbooks.
We're using docker-compose as well but I gather that isn't the standard approach under GitLab CI and our own recipe for installing that does nothing GitLab-related anyway.