You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Matt Sicker <bo...@gmail.com> on 2019/09/01 04:08:45 UTC
Re: [bcel][all] GitHub Actions for Maven builds
If you enable the project authorization setting on Jenkins, you can store
credentials in a specific user who the build runs as. It’s somewhat
primitive at the moment, but I’ve been working on related features lately
to improve the situation there for more complex CICD scenarios. Jenkins
pipelines aren’t going away anytime soon unlike SaaS fads sometimes do. ;)
On Sat, Aug 31, 2019 at 18:37, Gilles Sadowski <gi...@gmail.com> wrote:
> Le sam. 31 août 2019 à 19:22, Gary Gregory <ga...@gmail.com> a
> écrit :
> >
> > That is what I thinking, using GitHub actions we can keep builds and
> > sources in one place. Well two places: sources+builds in Apache and
> GitHub.
> > It feels like we can remove Travis.
>
> I can see this page
> https://travis-ci.org/apache/commons-bcel
> without being logged in.
> Concluding to the opposite.
>
> Moreover, not having any control over the evolution of one or the other's
> policy, why put all one's eggs in one basket?
>
> Gilles
>
> >
> > Gary
> >
> > On Sat, Aug 31, 2019, 12:53 Matt Sicker <bo...@gmail.com> wrote:
> >
> > > GitHub Actions are more of a replacement for Travis currently. Provided
> > > you’re not doing anything fancy in your pipelines, it might not require
> > > Jenkins, either.
> > >
> > > On Sat, Aug 31, 2019 at 11:17, Stefan Bodewig <bo...@apache.org>
> wrote:
> > >
> > > > On 2019-08-31, Gary Gregory wrote:
> > > >
> > > > > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski <
> gilleseran@gmail.com
> > > >
> > > > > wrote:
> > > >
> > > > >> Links returns "404".
> > > >
> > > > > Works for me, anyone else?
> > > >
> > > > Only works if you are logged in - an probably a member of the apache
> > > > organization. github returns 404 for links you are not allowed to
> see.
> > > >
> > > > Stefan
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> > > > For additional commands, e-mail: dev-help@commons.apache.org
> > > >
> > > > --
> > > Matt Sicker <bo...@gmail.com>
> > >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
> --
Matt Sicker <bo...@gmail.com>
Re: [bcel][all] GitHub Actions for Maven builds
Posted by Matt Sicker <bo...@gmail.com>.
I think I replied to the wrong email.
On Sun, Sep 1, 2019 at 04:53, Gilles Sadowski <gi...@gmail.com> wrote:
> Hi.
>
> 2019-09-01 6:08 UTC+02:00, Matt Sicker <bo...@gmail.com>:
> > If you enable the project authorization setting on Jenkins, you can store
> > credentials in a specific user who the build runs as. It’s somewhat
> > primitive at the moment, but I’ve been working on related features lately
> > to improve the situation there for more complex CICD scenarios. Jenkins
> > pipelines aren’t going away anytime soon unlike SaaS fads sometimes do.
> ;)
>
> Sorry but I don't understand how to apply this so that I could
> see GitHub's "actions" pages.
>
> Regards,
> Gilles
>
> > On Sat, Aug 31, 2019 at 18:37, Gilles Sadowski <gi...@gmail.com>
> > wrote:
> >
> >> Le sam. 31 août 2019 à 19:22, Gary Gregory <ga...@gmail.com> a
> >> écrit :
> >> >
> >> > That is what I thinking, using GitHub actions we can keep builds and
> >> > sources in one place. Well two places: sources+builds in Apache and
> >> GitHub.
> >> > It feels like we can remove Travis.
> >>
> >> I can see this page
> >> https://travis-ci.org/apache/commons-bcel
> >> without being logged in.
> >> Concluding to the opposite.
> >>
> >> Moreover, not having any control over the evolution of one or the
> other's
> >> policy, why put all one's eggs in one basket?
> >>
> >> Gilles
> >>
> >> >
> >> > Gary
> >> >
> >> > On Sat, Aug 31, 2019, 12:53 Matt Sicker <bo...@gmail.com> wrote:
> >> >
> >> > > GitHub Actions are more of a replacement for Travis currently.
> >> > > Provided
> >> > > you’re not doing anything fancy in your pipelines, it might not
> >> > > require
> >> > > Jenkins, either.
> >> > >
> >> > > On Sat, Aug 31, 2019 at 11:17, Stefan Bodewig <bo...@apache.org>
> >> wrote:
> >> > >
> >> > > > On 2019-08-31, Gary Gregory wrote:
> >> > > >
> >> > > > > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski <
> >> gilleseran@gmail.com
> >> > > >
> >> > > > > wrote:
> >> > > >
> >> > > > >> Links returns "404".
> >> > > >
> >> > > > > Works for me, anyone else?
> >> > > >
> >> > > > Only works if you are logged in - an probably a member of the
> >> > > > apache
> >> > > > organization. github returns 404 for links you are not allowed to
> >> see.
> >> > > >
> >> > > > Stefan
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> > > > For additional commands, e-mail: dev-help@commons.apache.org
> >> > > >
> >> > > > --
> >> > > Matt Sicker <bo...@gmail.com>
> >> > >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> >> For additional commands, e-mail: dev-help@commons.apache.org
> >>
> >> --
> > Matt Sicker <bo...@gmail.com>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
> --
Matt Sicker <bo...@gmail.com>
Re: [bcel][all] GitHub Actions for Maven builds
Posted by Gilles Sadowski <gi...@gmail.com>.
Hi.
2019-09-01 6:08 UTC+02:00, Matt Sicker <bo...@gmail.com>:
> If you enable the project authorization setting on Jenkins, you can store
> credentials in a specific user who the build runs as. It’s somewhat
> primitive at the moment, but I’ve been working on related features lately
> to improve the situation there for more complex CICD scenarios. Jenkins
> pipelines aren’t going away anytime soon unlike SaaS fads sometimes do. ;)
Sorry but I don't understand how to apply this so that I could
see GitHub's "actions" pages.
Regards,
Gilles
> On Sat, Aug 31, 2019 at 18:37, Gilles Sadowski <gi...@gmail.com>
> wrote:
>
>> Le sam. 31 août 2019 à 19:22, Gary Gregory <ga...@gmail.com> a
>> écrit :
>> >
>> > That is what I thinking, using GitHub actions we can keep builds and
>> > sources in one place. Well two places: sources+builds in Apache and
>> GitHub.
>> > It feels like we can remove Travis.
>>
>> I can see this page
>> https://travis-ci.org/apache/commons-bcel
>> without being logged in.
>> Concluding to the opposite.
>>
>> Moreover, not having any control over the evolution of one or the other's
>> policy, why put all one's eggs in one basket?
>>
>> Gilles
>>
>> >
>> > Gary
>> >
>> > On Sat, Aug 31, 2019, 12:53 Matt Sicker <bo...@gmail.com> wrote:
>> >
>> > > GitHub Actions are more of a replacement for Travis currently.
>> > > Provided
>> > > you’re not doing anything fancy in your pipelines, it might not
>> > > require
>> > > Jenkins, either.
>> > >
>> > > On Sat, Aug 31, 2019 at 11:17, Stefan Bodewig <bo...@apache.org>
>> wrote:
>> > >
>> > > > On 2019-08-31, Gary Gregory wrote:
>> > > >
>> > > > > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski <
>> gilleseran@gmail.com
>> > > >
>> > > > > wrote:
>> > > >
>> > > > >> Links returns "404".
>> > > >
>> > > > > Works for me, anyone else?
>> > > >
>> > > > Only works if you are logged in - an probably a member of the
>> > > > apache
>> > > > organization. github returns 404 for links you are not allowed to
>> see.
>> > > >
>> > > > Stefan
>> > > >
>> > > > ---------------------------------------------------------------------
>> > > > To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> > > > For additional commands, e-mail: dev-help@commons.apache.org
>> > > >
>> > > > --
>> > > Matt Sicker <bo...@gmail.com>
>> > >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>>
>> --
> Matt Sicker <bo...@gmail.com>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org