Re: [foreman-dev] Link to redmine issues using prprocessor
I do it manually although I probably should just write a commit hook to do it. I put it in the message itself because I think it's useful to have there in case anyone is browsing the git log or in case we ever move away from github. Walden On Thu, Apr 6, 2017 at 5:33 PM, Andrew Kofink wrote: > Walden, you have a script that adds it, or do you do it manually for every > issue? If the latter, then wouldn't this save you some time? ;) > > On Thu, Apr 6, 2017 at 5:24 PM, Walden Raines wrote: > >> I like it although I include the links to the issues in my actual commit >> message so it will be doubled up in my case. >> >> >> >> On Thu, Apr 6, 2017 at 4:18 PM, John Mitsch wrote: >> >>> +1 from me :) >>> >>> John Mitsch >>> Red Hat Engineering >>> (860)-967-7285 <(860)%20967-7285> >>> irc: jomitsch >>> >>> On Thu, Apr 6, 2017 at 3:05 PM, Andrew Kofink >>> wrote: >>> I find myself copying/pasting issue numbers from GitHub PRs to a redmine url way too much every day. It takes a bit of time, and it's annoying as well as easy to fix. I've submitted this PR to comment on a newly submitted PR with links to the associated issues in redmine: https://github.com/th eforeman/prprocessor/pull/59 I'd like to hear your thoughts if you have something to say about it. - Andrew -- Andrew Kofink akof...@redhat.com IRC: akofink Associate Software Engineer Red Hat Satellite -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Andrew Kofink > akof...@redhat.com > IRC: akofink > Associate Software Engineer > Red Hat Satellite > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Link to redmine issues using prprocessor
Walden, you have a script that adds it, or do you do it manually for every issue? If the latter, then wouldn't this save you some time? ;) On Thu, Apr 6, 2017 at 5:24 PM, Walden Raines wrote: > I like it although I include the links to the issues in my actual commit > message so it will be doubled up in my case. > > > > On Thu, Apr 6, 2017 at 4:18 PM, John Mitsch wrote: > >> +1 from me :) >> >> John Mitsch >> Red Hat Engineering >> (860)-967-7285 <(860)%20967-7285> >> irc: jomitsch >> >> On Thu, Apr 6, 2017 at 3:05 PM, Andrew Kofink wrote: >> >>> I find myself copying/pasting issue numbers from GitHub PRs to a redmine >>> url way too much every day. It takes a bit of time, and it's annoying as >>> well as easy to fix. >>> >>> I've submitted this PR to comment on a newly submitted PR with links to >>> the associated issues in redmine: https://github.com/th >>> eforeman/prprocessor/pull/59 I'd like to hear your thoughts if you have >>> something to say about it. >>> >>> - Andrew >>> >>> -- >>> Andrew Kofink >>> akof...@redhat.com >>> IRC: akofink >>> Associate Software Engineer >>> Red Hat Satellite >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "foreman-dev" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to foreman-dev+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Andrew Kofink akof...@redhat.com IRC: akofink Associate Software Engineer Red Hat Satellite -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Link to redmine issues using prprocessor
I like it although I include the links to the issues in my actual commit message so it will be doubled up in my case. On Thu, Apr 6, 2017 at 4:18 PM, John Mitsch wrote: > +1 from me :) > > John Mitsch > Red Hat Engineering > (860)-967-7285 <(860)%20967-7285> > irc: jomitsch > > On Thu, Apr 6, 2017 at 3:05 PM, Andrew Kofink wrote: > >> I find myself copying/pasting issue numbers from GitHub PRs to a redmine >> url way too much every day. It takes a bit of time, and it's annoying as >> well as easy to fix. >> >> I've submitted this PR to comment on a newly submitted PR with links to >> the associated issues in redmine: https://github.com/th >> eforeman/prprocessor/pull/59 I'd like to hear your thoughts if you have >> something to say about it. >> >> - Andrew >> >> -- >> Andrew Kofink >> akof...@redhat.com >> IRC: akofink >> Associate Software Engineer >> Red Hat Satellite >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev+unsubscr...@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Link to redmine issues using prprocessor
+1 from me :) John Mitsch Red Hat Engineering (860)-967-7285 irc: jomitsch On Thu, Apr 6, 2017 at 3:05 PM, Andrew Kofink wrote: > I find myself copying/pasting issue numbers from GitHub PRs to a redmine > url way too much every day. It takes a bit of time, and it's annoying as > well as easy to fix. > > I've submitted this PR to comment on a newly submitted PR with links to > the associated issues in redmine: https://github.com/ > theforeman/prprocessor/pull/59 I'd like to hear your thoughts if you have > something to say about it. > > - Andrew > > -- > Andrew Kofink > akof...@redhat.com > IRC: akofink > Associate Software Engineer > Red Hat Satellite > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Link to redmine issues using prprocessor
I find myself copying/pasting issue numbers from GitHub PRs to a redmine url way too much every day. It takes a bit of time, and it's annoying as well as easy to fix. I've submitted this PR to comment on a newly submitted PR with links to the associated issues in redmine: https://github.com/theforeman/prprocessor/pull/59 I'd like to hear your thoughts if you have something to say about it. - Andrew -- Andrew Kofink akof...@redhat.com IRC: akofink Associate Software Engineer Red Hat Satellite -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Proposal/Request for an foreman-ansible-modules repository
On Thu, Apr 6, 2017 at 2:02 PM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote: > > Howdy, > > > > I have a number of Ansible modules that I have developed for managing > > Katello entities and Foreman organizations. An Ansible module can be > > thought of as providing extentsibility and new functionality to Ansible > > roles and playbooks. In this case, by being able to manage entities > within > > Foreman and Katello. There are also a number of modules I have seen upon > > google search that exist for other various Foreman entities. > > > > I would like to share the modules I have written and encourage other > > community users to share theirs in a centralized place for use. Ideally, > > these modules would be offered to and go into Ansible's core set of > modules > > after some time of development. However, I believe they need somewhere > > useful to live during said transition and as a place to harden them > before > > offering them up and awaiting an Ansible release. > > > > Thus, I would like to propose and request a repository on theforeman > Github > > organization named 'foreman-ansible-modules' as a place for these to > live. > > The goals of the repository would be: > > Does this mean that it's one repository for all modules or one > repository per module? I'm fine either way, just want to curious. > I'd prefer one repository for all modules otherwise this could mean a lot of repositories and if a users wants to use them they have to download each and every one vs cloning a single repo. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Proposal/Request for an foreman-ansible-modules repository
On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote: > Howdy, > > I have a number of Ansible modules that I have developed for managing > Katello entities and Foreman organizations. An Ansible module can be > thought of as providing extentsibility and new functionality to Ansible > roles and playbooks. In this case, by being able to manage entities within > Foreman and Katello. There are also a number of modules I have seen upon > google search that exist for other various Foreman entities. > > I would like to share the modules I have written and encourage other > community users to share theirs in a centralized place for use. Ideally, > these modules would be offered to and go into Ansible's core set of modules > after some time of development. However, I believe they need somewhere > useful to live during said transition and as a place to harden them before > offering them up and awaiting an Ansible release. > > Thus, I would like to propose and request a repository on theforeman Github > organization named 'foreman-ansible-modules' as a place for these to live. > The goals of the repository would be: Does this mean that it's one repository for all modules or one repository per module? I'm fine either way, just want to curious. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Proposal/Request for an foreman-ansible-modules repository
I'm +1 for this. We have the same structure for the Puppet modules, in that we maintain them and then release them on the Forge, and I see no reason why we can't do the same for Ansible. It's not like there's an upper limit on how many repos our GitHub organisation can have, so I don't see any downsides ;) Greg -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Puppet 3 support dropped in our puppet modules
We still need to branch the Katello modules so that must happen first. Other than that we haven't really discussed it but I do think we should mirror this for the Katello modules for the same reason the foreman modules dropped it: dependencies are dropping it and pinning on old versions is actively building technical debt. On Thu, Apr 06, 2017 at 09:02:06AM -0400, Eric D Helms wrote: > Ewoud - does this extend to the Katello modules or are you strictly > speaking of the core set for Foreman modules? > > On Thu, Apr 6, 2017 at 8:10 AM, Ewoud Kohl van Wijngaarden < > ew...@kohlvanwijngaarden.nl> wrote: > > > Good news everyone! Puppet 3 support has been dropped in our modules. > > > > As announced earlier we'd continue supporting Puppet 3 for the 1.15 > > release. Now that we've branched, we're starting to use Puppet 4 types > > which syntax is incompatible with Puppet 3. > > > > For the version numbers that support Puppet 3 I'd recommend looking at > > https://github.com/theforeman/foreman-installer/blob/1.15- > > stable/Puppetfile > > Each module has a stable-x.y branch where we accept bugfixes but > > preferably no new features. > > > > With this we follow Puppetlabs and Voxpupuli which are starting to drop > > or have dropped support already. Since we depend on them, we can no > > longer reasonably support more than they do. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [foreman-dev] Puppet 3 support dropped in our puppet modules
Ewoud - does this extend to the Katello modules or are you strictly speaking of the core set for Foreman modules? On Thu, Apr 6, 2017 at 8:10 AM, Ewoud Kohl van Wijngaarden < ew...@kohlvanwijngaarden.nl> wrote: > Good news everyone! Puppet 3 support has been dropped in our modules. > > As announced earlier we'd continue supporting Puppet 3 for the 1.15 > release. Now that we've branched, we're starting to use Puppet 4 types > which syntax is incompatible with Puppet 3. > > For the version numbers that support Puppet 3 I'd recommend looking at > https://github.com/theforeman/foreman-installer/blob/1.15- > stable/Puppetfile > Each module has a stable-x.y branch where we accept bugfixes but > preferably no new features. > > With this we follow Puppetlabs and Voxpupuli which are starting to drop > or have dropped support already. Since we depend on them, we can no > longer reasonably support more than they do. > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Eric D. Helms Red Hat Engineering -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[foreman-dev] Puppet 3 support dropped in our puppet modules
Good news everyone! Puppet 3 support has been dropped in our modules. As announced earlier we'd continue supporting Puppet 3 for the 1.15 release. Now that we've branched, we're starting to use Puppet 4 types which syntax is incompatible with Puppet 3. For the version numbers that support Puppet 3 I'd recommend looking at https://github.com/theforeman/foreman-installer/blob/1.15-stable/Puppetfile Each module has a stable-x.y branch where we accept bugfixes but preferably no new features. With this we follow Puppetlabs and Voxpupuli which are starting to drop or have dropped support already. Since we depend on them, we can no longer reasonably support more than they do. -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
