This is a bit of bike shedding perhaps, but as I start to re-write some of
our jobs into Jenkins pipeline in my spare time I'd like to establish and
follow some conventions along the way since this is a bit of a fresh start.
Two example PRs for those curious are at [1] [2].
The topic for this question is around job naming conventions. I see it as
two options:
My vote would be #2, as it groups things by entity a bit nicer. I don't
normally care to look at the release job across all projects, but would
want to look at all jobs across a particular project.
···
On 09/01/2017 08:43 AM, Eric D Helms wrote:
> Howdy,
>
> This is a bit of bike shedding perhaps, but as I start to re-write
> some of our jobs into Jenkins pipeline in my spare time I'd like to
> establish and follow some conventions along the way since this is a
> bit of a fresh start. Two example PRs for those curious are at [1] [2].
>
> The topic for this question is around job naming conventions. I see it
> as two options:
>
> 1) functionality - entity
> -- test-katello
> -- test-foreman
> -- release-katello
> -- test-foreman-pull-request
> -- test-foreman-tasks
> 2) entity - functionality
> -- katello-test
> -- katello-release
> -- foreman-test
> -- foreman-release
> -- foreman-pull-request-test
> -- foreman-tasks-test
>
>
> [1] https://github.com/theforeman/foreman-infra/pull/321
> [2] https://github.com/theforeman/foreman-infra/pull/323
>
>
> --
> 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+unsubscribe@googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.
Another vote for #2 as you can scan quickly and group by project.
John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch
···
On Fri, Sep 1, 2017 at 8:56 AM, Justin Sherrill wrote:
My vote would be #2, as it groups things by entity a bit nicer. I don’t
normally care to look at the release job across all projects, but would
want to look at all jobs across a particular project.
On 09/01/2017 08:43 AM, Eric D Helms wrote:
Howdy,
This is a bit of bike shedding perhaps, but as I start to re-write some of
our jobs into Jenkins pipeline in my spare time I’d like to establish and
follow some conventions along the way since this is a bit of a fresh start.
Two example PRs for those curious are at [1] [2].
The topic for this question is around job naming conventions. I see it as
two options:
···
On Fri, Sep 01, 2017 at 09:29:17AM -0400, John Mitsch wrote:
>Another vote for #2 as you can scan quickly and group by project.
>
>John Mitsch
>Red Hat Engineering
>(860)-967-7285
>irc: jomitsch
>
>On Fri, Sep 1, 2017 at 8:56 AM, Justin Sherrill wrote:
>
>> My vote would be #2, as it groups things by entity a bit nicer. I don't
>> normally care to look at the release job across all projects, but would
>> want to look at all jobs across a particular project.
>>
>> On 09/01/2017 08:43 AM, Eric D Helms wrote:
>>
>> Howdy,
>>
>> This is a bit of bike shedding perhaps, but as I start to re-write some of
>> our jobs into Jenkins pipeline in my spare time I'd like to establish and
>> follow some conventions along the way since this is a bit of a fresh start.
>> Two example PRs for those curious are at [1] [2].
>>
>> The topic for this question is around job naming conventions. I see it as
>> two options:
>>
>> 1) functionality - entity
>> -- test-katello
>> -- test-foreman
>> -- release-katello
>> -- test-foreman-pull-request
>> -- test-foreman-tasks
>> 2) entity - functionality
>> -- katello-test
>> -- katello-release
>> -- foreman-test
>> -- foreman-release
>> -- foreman-pull-request-test
>> -- foreman-tasks-test
>>
>>
>> [1] https://github.com/theforeman/foreman-infra/pull/321
>> [2] https://github.com/theforeman/foreman-infra/pull/323
>>
>>
>> --
>> 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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.
···
> Joining in on the party: +1 for #2
>
> On Fri, Sep 01, 2017 at 09:29:17AM -0400, John Mitsch wrote:
> >Another vote for #2 as you can scan quickly and group by project.
> >
> >John Mitsch
> >Red Hat Engineering
> >(860)-967-7285
> >irc: jomitsch
> >
> >On Fri, Sep 1, 2017 at 8:56 AM, Justin Sherrill > wrote:
> >
> >> My vote would be #2, as it groups things by entity a bit nicer. I don't
> >> normally care to look at the release job across all projects, but would
> >> want to look at all jobs across a particular project.
> >>
> >> On 09/01/2017 08:43 AM, Eric D Helms wrote:
> >>
> >> Howdy,
> >>
> >> This is a bit of bike shedding perhaps, but as I start to re-write some
> of
> >> our jobs into Jenkins pipeline in my spare time I'd like to establish
> and
> >> follow some conventions along the way since this is a bit of a fresh
> start.
> >> Two example PRs for those curious are at [1] [2].
> >>
> >> The topic for this question is around job naming conventions. I see it
> as
> >> two options:
> >>
> >> 1) functionality - entity
> >> -- test-katello
> >> -- test-foreman
> >> -- release-katello
> >> -- test-foreman-pull-request
> >> -- test-foreman-tasks
> >> 2) entity - functionality
> >> -- katello-test
> >> -- katello-release
> >> -- foreman-test
> >> -- foreman-release
> >> -- foreman-pull-request-test
> >> -- foreman-tasks-test
> >>
> >>
> >> [1] https://github.com/theforeman/foreman-infra/pull/321
> >> [2] https://github.com/theforeman/foreman-infra/pull/323
> >>
> >>
> >> --
> >> 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+unsubscribe@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+unsubscribe@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+unsubscribe@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+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
for