On 10/11/17 15:20, Ewoud Kohl van Wijngaarden wrote:
> On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote:
>> To make this a more "official" policy, I've created a "Foreman" account
>> on Rubygems, and the user can be added
>> to any gem we keep on our namespace. This should minimize a
So, I am looking for some help integrating SaltStack with The
Foreman/Katello. I think I might have bitten off more than I can chew. So
far, I can:
* Install Katello/The Foreman with SaltStack -
https://github.com/jdshewey/slik-installer
* Add GPG Keys
* I have a module/python functions for do
So, I am looking for some help integrating SaltStack with The
Foreman/Katello. I think I might have bitten off more than I can chew. So
far, I can:
* Install Katello/The Foreman with SaltStack -
https://github.com/jdshewey/slik-installer
* Add GPG Keys
* I have a module/python functions for do
Based on the feedback, I have started the repository for this effort [1]
and opened an initial PR [2] that adds tooling and an initial set of
packages in order to ensure that tooling works. My goal is to get the
initial package and tooling reviewed and committed before moving on to
other packages.
On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote:
To make this a more "official" policy, I've created a "Foreman" account
on Rubygems, and the user can be added
to any gem we keep on our namespace. This should minimize any issues
when transferring gems to new owners.
For what it'
On 10/11/17 14:02, Greg Sutcliffe wrote:
> To make this a more "official" policy, I've created a "Foreman" account
> on Rubygems, and the user can be added
> to any gem we keep on our namespace. This should minimize any issues
> when transferring gems to new owners.
That user is now added to ever
On 10/11/17 14:23, Ewoud Kohl van Wijngaarden wrote:
>
> I like this. What are the opinions on deploying gems through Travis like
> voxpupuli does?
>
> https://docs.travis-ci.com/user/deployment/rubygems/
>
> tl;dr: on tags it can deploy the gem to rubygems. It standardizes the
> deploy process
On Fri, Nov 10, 2017 at 02:02:10PM +, Greg Sutcliffe wrote:
A few months ago we added a policy that required 2 gem authors per
plugin. We did, however struggle to actually get two authors on some
plugins.
To make this a more "official" policy, I've created a "Foreman" account
on Rubygems, an
Hi all,
A few months ago we added a policy that required 2 gem authors per
plugin. We did, however struggle to actually get two authors on some
plugins.
To make this a more "official" policy, I've created a "Foreman" account
on Rubygems, and the user can be added
to any gem we keep on our namesp