Skip to content
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

Closed
spuder opened this issue Jun 1, 2015 · 8 comments
Closed

Revision 3.0.x #157

spuder opened this issue Jun 1, 2015 · 8 comments
Assignees

Comments

@spuder
Copy link
Owner

spuder commented Jun 1, 2015

Change the puppet module to use the following:

  • Use ahuffman's changes to use package cloud repos
  • Use elastic/elasticsearch model to dynamically create gitlab.rb based on hash. Reducing the number of parameters down to a dozen.
@spuder spuder self-assigned this Jun 1, 2015
@spuder
Copy link
Owner Author

spuder commented Jun 1, 2015

@ghost
Copy link

ghost commented Jun 3, 2015

Any chance ee will be supported, now that the access scheme has changed?

@spuder
Copy link
Owner Author

spuder commented Jun 3, 2015

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.

https://about.gitlab.com/license-faq/

https://about.gitlab.com/2015/05/22/gitlab-7-11-released/

@ghost
Copy link

ghost commented Jun 3, 2015

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
admin. Here you can upload your .gitlab-license file, which will instantly
unlock GitLab Enterprise Edition.

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
wrote:

Yes, just found out that gitlab finally added gitlab-ee packages to
package cloud. I don't have an enterprise license, so I need to research
how to implement this (is it a serial number, product key) ect..

Do you know how gitlab ee is activated?


Reply to this email directly or view it on GitHub
#157 (comment)
.

Michael Chmielewski* |* Practice Lead, Release Engineering

T 617.478.9368

http://www.bullhorn.com

Twitter https://twitter.com/bullhorn | Linkedin
http://www.linkedin.com/company/bullhorn | Facebook
https://www.facebook.com/Bullhorn

http://www.bullhorn.com/engage/

@ghost
Copy link

ghost commented Jul 8, 2015

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 ?

@spuder
Copy link
Owner Author

spuder commented Jul 8, 2015

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

@ahuffman
Copy link

ahuffman commented Jul 8, 2015

I wouldn't cross your fingers about the packagecloud ever being fixed.
I've been using my forked packagecloud branch since 7.10 with my forked
puppet-gitlab repo and it's been working just fine. Feel free to pull in,
and/or rework anything that I did there as well as the process to install
the newer gitlab packages.

On Wed, Jul 8, 2015 at 11:15 AM, Spencer Owen notifications@github.com
wrote:

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


Reply to this email directly or view it on GitHub
#157 (comment)
.

Regards,

Andrew

@spuder
Copy link
Owner Author

spuder commented Jul 9, 2015

Module transitioned to here: https://github.com/vshn/puppet-gitlab

@spuder spuder closed this as completed Jul 9, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants