On Friday, January 29, 2016 at 2:31:14 AM UTC+11, Steve Traylen wrote:
>
>
> There's another one to consider
> https://github.com/cernops/jens
> it recently got an update to accept hook calls from gitlab. We get
> our git pushes deployed in 0.4s now.
>
Thanks I'll keep it in mind!
>
>
--
On Friday, January 29, 2016 at 6:15:41 AM UTC+11, Garrett Honeycutt wrote:
>
>
> Hi Alex,
>
> I generally implement both for customers. Though I use Dan Bode's
> librarian-puppet-simple which purposely does not handle dependencies. I
> spoke at a couple Puppet Camp's regarding dealing with mod
On 1/28/16 9:40 AM, Alex Harvey wrote:
> Hi all,
>
> I am interested in the future of the Librarian-puppet project - to find
> out how many people are still using it, and if there are people out
> there who actually prefer it over R10K.
>
> I recently looked into R10K for a few projects I was wor
The requirement to "deploy code in complex ways" sounds like an "enterprise"
thing. On the one hand, these companies may have few spare cycles for
synchronizing configurations across disparate customer-facing products. On the
other hand, there can be certain strategically important environments
On Thu, 2016-01-28 at 06:40 -0800, Alex Harvey wrote:
> Hi all,
>
> I am interested in the future of the Librarian-puppet project - to
> find out how many people are still using it, and if there are people
> out there who actually prefer it over R10K.
>
There's another one to consider
https://git
- Original Message -
> From: "Alex Harvey"
> To: "puppet-users"
> Sent: Thursday, January 28, 2016 3:40:15 PM
> Subject: [Puppet Users] librarian-puppet vs R10K
> Hi all,
>
> I am interested in the future of the Librarian-puppet project - to find out
> how many people are still using
Did you install puppet via an RPM? If so, this patch will likely fix your
issue. https://github.com/rodjek/librarian-puppet/issues/38
On Oct 31, 2012, at 2:52 PM, Worker Bee wrote:
> Unless I install puppet vis gems, I get the following error when attempting
> to use librarian-puppet.
>
>
On Mon, Jul 23, 2012 at 8:43 PM, Dan Bode wrote:
>
>
> On Mon, Jul 23, 2012 at 3:43 PM, Ryan Bowlby wrote:
>
>> Can anyone comment on their experiences with librarian-puppet or using
>> git superproject with per puppet module repositories?
>
>
> I tried using git submodules for a long time. I fo
On 24 July 2012 00:43, Ryan Bowlby wrote:
> Can anyone comment on their experiences with librarian-puppet or using git
> superproject with per puppet module repositories? We are in the midst of
> determining which route is optimal for our environment. It seems like using
> git superprojects would
Thanks all, we've decided to stick with git super project and per module
repositories. Some of the modules will be a clone from github, but most are
internal. It seems to suit our needs and we don't see a reason to implement
librarian-puppet.
Ohad, I setup pulp at work and it's pretty good (tas
On Tue, Jul 24, 2012 at 9:49 AM, David Schmitt wrote:
> On 24.07.2012 00:43, Ryan Bowlby wrote:
>
>> Can anyone comment on their experiences with librarian-puppet or using
>> git superproject with per puppet module repositories? We are in the
>> midst of determining which route is optimal for our
On 24.07.2012 00:43, Ryan Bowlby wrote:
Can anyone comment on their experiences with librarian-puppet or using
git superproject with per puppet module repositories? We are in the
midst of determining which route is optimal for our environment. It
seems like using git superprojects would mean one
On Mon, Jul 23, 2012 at 3:43 PM, Ryan Bowlby wrote:
> Can anyone comment on their experiences with librarian-puppet or using git
> superproject with per puppet module repositories?
I tried using git submodules for a long time. I found that I just could not
keep up with updating changed modules
13 matches
Mail list logo