Hi. 2019-09-01 6:08 UTC+02:00, Matt Sicker <boa...@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 <gillese...@gmail.com> > wrote: > >> Le sam. 31 août 2019 à 19:22, Gary Gregory <garydgreg...@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 <boa...@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 <bode...@apache.org> >> wrote: >> > > >> > > > On 2019-08-31, Gary Gregory wrote: >> > > > >> > > > > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski < >> gillese...@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-unsubscr...@commons.apache.org >> > > > For additional commands, e-mail: dev-h...@commons.apache.org >> > > > >> > > > -- >> > > Matt Sicker <boa...@gmail.com> >> > > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> -- > Matt Sicker <boa...@gmail.com> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
