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

The gitlab module is no longer idempotent #172

Closed
blkperl opened this issue Aug 17, 2014 · 19 comments
Closed

The gitlab module is no longer idempotent #172

blkperl opened this issue Aug 17, 2014 · 19 comments

Comments

@blkperl
Copy link
Collaborator

blkperl commented Aug 17, 2014

Due to alup/puppet-rbenv#80 the rbenv module always triggers an event. There is a proposed patch alup/puppet-rbenv#97 but there has been no action on it.

I'm concerned that alup/puppet-rbenv is no longer maintained and that we should find a way to get in contact with the author, find an altertanitive module or fork our own version that works properly.

@andyleejordan
Copy link
Collaborator

I'm glad you brought that up. At the time of the original work it still seemed maintained and the most popularly used, but I've noticed some issues with it as well. I'm considering an attempted switch to jdowning/rbenv, as its latest release was July and it seems widely used.

@igalic
Copy link
Collaborator

igalic commented Aug 18, 2014

seems to be quite decent.

@ergonlogic
Copy link

The Gitlab maintainers specifically state that they don't support rbenv for production use: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/install/installation.md

That said, the dependency on an rbenv Puppet module ought to be documented in the readme.

@atomaka
Copy link
Collaborator

atomaka commented Aug 20, 2014

@ergonlogic I noted this in the original pull request (#114 (comment)), but support for the change was strong and it does function as expected. I'll take care of the README update this afternoon.

@ergonlogic
Copy link

Thanks @atomaka, I'd just found #114.

If it hasn't already, the working deployment method for rbenv (sourced from .bashrc, or whatever) should probably be communicated and/or documented upstream, to the gitlab maintainers.

@altvnk
Copy link

altvnk commented Aug 27, 2014

Due to some tips with RBENV i'm started using system-wide RVM (binary).

@sbadia
Copy link
Owner

sbadia commented Sep 3, 2014

So? We switch to jdowning/rbenv ?

@blkperl
Copy link
Collaborator Author

blkperl commented Sep 12, 2014

Sounds good to me

@igalic
Copy link
Collaborator

igalic commented Sep 13, 2014

👍, with the caveat: i don't have the cycles to contribute currently :(

@igalic
Copy link
Collaborator

igalic commented Oct 14, 2014

@JimPanic might have some time to fix it ;)

@igalic
Copy link
Collaborator

igalic commented Oct 16, 2014

so, i just looked into replacing alup/rbenv with jdowning/rbenv, however, currently we are compiling three versions of ruby, for three pieces of software:

igalic@levix ~/src/puppet/sbadia-gitlab (git)-[rbenv-new] % ack rbenv::compile manifests
manifests/setup.pp
105:  rbenv::compile { 'gitlab/ruby':

manifests/ci/setup.pp
74:  rbenv::compile { 'gitlabci/ruby':

manifests/ci/runner.pp
57:  rbenv::compile { 'gitlab-ci-runner/ruby':

this works well with alup/rbenv, because it's just a bunch of (defined) types, but in jdowning/rbenv they all have a global configuration.

i pinged @alup on twitter, https://twitter.com/hirojin/status/522713407842443264 / https://twitter.com/hirojin/status/522713524431491072 - hope there'll be a reply on one channel or another.

@alup
Copy link

alup commented Oct 16, 2014

Hi, FYI I am planning to catch up (with puppet/rbenv) next week. I will take a look at this and other problems. Finally, I am going to upload a brand new release to puppetforge.

@igalic
Copy link
Collaborator

igalic commented Oct 17, 2014

\o/

alexcern added a commit to cernops/puppet-gitlab that referenced this issue Jan 13, 2015
This incidently provides a workaround for sbadia#172.
This uses a different method to change ruby path in
gitlab-shell hooks when rbenv is used and hence
fixes sbadia#202 as well.
@lieutdan13
Copy link
Contributor

Still running into this issue today. There has apparently been a better proposed fix for alup/puppet-rbenv#80 being alup/puppet-rbenv/pull/106. But again, the maintainer is unresponsive to the PR.

@alup
Copy link

alup commented Jan 14, 2015

@lieutdan13 just merged

@lieutdan13
Copy link
Contributor

It appears that alup/puppet-rbenv#108 fixes this issue. Not alup/puppet-rbenv#106. I've updated my rbenv module and ran puppet on the affected machine without it producing any rbenv output.

Thanks @alup for the fix!

@igalic
Copy link
Collaborator

igalic commented Jan 27, 2015

@lieutdan13 they are both now merged.

alexcern added a commit to cernops/puppet-gitlab that referenced this issue Jan 30, 2015
This incidently provides a workaround for sbadia#172.
This uses a different method to change ruby path in
gitlab-shell hooks when rbenv is used and hence
fixes sbadia#202 as well.
@sbadia
Copy link
Owner

sbadia commented Mar 19, 2015

108, 106 and 202/204 fixed, thanks all !

@sbadia sbadia closed this as completed Mar 19, 2015
@andyleejordan
Copy link
Collaborator

Nice!

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

9 participants