On Tue, Dec 2, 2014 at 12:15 PM, Jeff McCune wrote:
> I plan to release rspec-puppet 1.1.0 today as per the discussion at
>> https://github.com/rodjek/rspec-puppet/issues/213
>>
>
>
> Scratch that, looks like Tim is the only person who can push new releases
> to rubygems.org. I've tagged the re
Is it possible to work in a change to rspec-puppet for PUP-3336?
Maybe as simple as modifying the LOAD_PATH as shown in my example above?
Cheers
Gav
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and sto
On Tue, Dec 2, 2014 at 9:28 AM, Jeff McCune wrote:
> On Fri, Nov 28, 2014 at 3:08 PM, Kylo Ginsberg
> wrote:
>>
>> As an FYI, I did attempt to modify that code from rspec-puppet to set
>>> libdir as an array instead of a ':' delim string, and it led to failures
>>> from Puppet
>>>
>>
>> There's
On 12/02/2014 10:28 AM, Jeff McCune wrote:
> It's been a long time since the last release, so if anyone has been working
> with the rspec-puppet "master" branch, please let me know if you've run
> into backwards-compatibility issues in master that would motivate a 2.0.0
> release, or pulling out th
On Fri, Nov 28, 2014 at 3:08 PM, Kylo Ginsberg wrote:
>
> As an FYI, I did attempt to modify that code from rspec-puppet to set
>> libdir as an array instead of a ':' delim string, and it led to failures
>> from Puppet
>>
>
> There's been some work/conversation around libdir being split/not-split
I think that this should go in rspec-puppet since it is core to custom
functions and types functioning in many cases. Also, users may, or may not,
be using the other testing components.
Thanks,
Trevor
On Tue, Dec 2, 2014 at 2:13 AM, Josh Cooper wrote:
>
>
> On Mon, Dec 1, 2014 at 11:44 AM, Tre
On Mon, Dec 1, 2014 at 11:44 AM, Trevor Vaughan
wrote:
> Well that makes a ridiculous amount of sense.
>
> Thanks for posting, I'll check it out tomorrow.
>
> Trevor
>
> On Mon, Dec 1, 2014 at 4:20 AM, Gavin Williams wrote:
>
>> The code I've added to work-around the Puppet issue is here[1].
>>
Well that makes a ridiculous amount of sense.
Thanks for posting, I'll check it out tomorrow.
Trevor
On Mon, Dec 1, 2014 at 4:20 AM, Gavin Williams wrote:
> The code I've added to work-around the Puppet issue is here[1].
>
> HTH.
>
> Gav
>
> [1]https://gist.github.com/fatmcgav/aa7295798502d660
The code I've added to work-around the Puppet issue is here[1].
HTH.
Gav
[1]https://gist.github.com/fatmcgav/aa7295798502d660c6a3
On Saturday, 29 November 2014 23:50:23 UTC, Trevor Vaughan wrote:
>
> It would indeed and I appreciate the info.
>
> Trevor
> On Nov 29, 2014 5:28 AM, "Gavin Willia
It would indeed and I appreciate the info.
Trevor
On Nov 29, 2014 5:28 AM, "Gavin Williams" wrote:
> Yeh, I hit the same issue with the LOAD_PATH which lead to that PR and
> raising PUP-3663.
>
> I've worked around it by modifying the LOAD_PATH in spec_helper.rb.
> Can post it when in work on Mo
Yeh, I hit the same issue with the LOAD_PATH which lead to that PR and raising
PUP-3663.
I've worked around it by modifying the LOAD_PATH in spec_helper.rb.
Can post it when in work on Monday if that helps.
Cheers
Gav
--
You received this message because you are subscribed to the Google Gr
On Fri, Nov 28, 2014 at 3:08 PM, Kylo Ginsberg wrote:
> On Fri, Nov 28, 2014 at 8:30 AM, Dan Bode wrote:
>
>> On Tue, Nov 25, 2014 at 5:25 PM, Trevor Vaughan
>> wrote:
>>
>>> Hi All,
>>>
>>> I've got a couple of issues running rspec-puppet tests under Ruby 2 that
>>> I was hoping someone could
On Fri, Nov 28, 2014 at 8:30 AM, Dan Bode wrote:
> On Tue, Nov 25, 2014 at 5:25 PM, Trevor Vaughan
> wrote:
>
>> Hi All,
>>
>> I've got a couple of issues running rspec-puppet tests under Ruby 2 that
>> I was hoping someone could shed some light on.
>>
>> First, under Ruby 2, any validation func
How bizarre. This does seem like a bit of a show stopper to me in terms of
testing in multiple environments.
Hopefully, we can figure it out at some point.
On Fri, Nov 28, 2014 at 11:30 AM, Dan Bode wrote:
>
>
> On Tue, Nov 25, 2014 at 5:25 PM, Trevor Vaughan
> wrote:
>
>> Hi All,
>>
>> I've g
On Tue, Nov 25, 2014 at 5:25 PM, Trevor Vaughan
wrote:
> Hi All,
>
> I've got a couple of issues running rspec-puppet tests under Ruby 2 that I
> was hoping someone could shed some light on.
>
> First, under Ruby 2, any validation functions in the code appear to be
> getting parsed *after* the in
Hi All,
I've got a couple of issues running rspec-puppet tests under Ruby 2 that I
was hoping someone could shed some light on.
First, under Ruby 2, any validation functions in the code appear to be
getting parsed *after* the inline templates. I like to stick my validation
at the bottom of the fi
16 matches
Mail list logo
