-
Notifications
You must be signed in to change notification settings - Fork 44
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
Revision 3.0.x #157
Comments
Any chance ee will be supported, now that the access scheme has changed? |
Yes, just found out that gitlab finally added gitlab-ee packages to package cloud. I don't have an enterprise license. It appears that there is a key, that needs to be placed in a specific directory. |
The release blog post: https://about.gitlab.com/2015/05/22/gitlab-7-11-released/ To install the license, vist /admin/license in your GitLab instance as an Basically, you upload the license you get from gitlab itself into the app. On Wed, Jun 3, 2015 at 4:41 PM, Spencer Owen notifications@github.com
Michael Chmielewski* |* Practice Lead, Release Engineering T 617.478.9368 Twitter https://twitter.com/bullhorn | Linkedin |
Have you published a branch for this? I'd love to look at it, and maybe even help here and there. Also have you talked to the author of https://github.com/vshn/puppet-gitlab ? |
I haven't pushed a branch yet because of the problem with the packagerepo puppet module. Thanks for letting me know about vshn's module. This does look exactly like what I was wanting to do with branch 3.x |
I wouldn't cross your fingers about the packagecloud ever being fixed. On Wed, Jul 8, 2015 at 11:15 AM, Spencer Owen notifications@github.com
Regards, Andrew |
Module transitioned to here: https://github.com/vshn/puppet-gitlab |
Change the puppet module to use the following:
The text was updated successfully, but these errors were encountered: