Re: [bcel][all] GitHub Actions for Maven builds

2019-09-01 Thread Matt Sicker
I think I replied to the wrong email. On Sun, Sep 1, 2019 at 04:53, Gilles Sadowski wrote: > Hi. > > 2019-09-01 6:08 UTC+02:00, Matt Sicker : > > 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 > >

Re: [bcel][all] GitHub Actions for Maven builds

2019-09-01 Thread Gilles Sadowski
Hi. 2019-09-01 6:08 UTC+02:00, Matt Sicker : > 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

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Matt Sicker
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

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gilles Sadowski
Le sam. 31 août 2019 à 19:22, Gary Gregory 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

RE: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Mark Roberts
][all] GitHub Actions for Maven builds 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. Gary On Sat, Aug 31, 2019, 12:53 Matt Sicker wrote: > GitHub Acti

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gary Gregory
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. Gary On Sat, Aug 31, 2019, 12:53 Matt Sicker wrote: > GitHub Actions are more of a replacement for Travis

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Matt Sicker
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 wrote: > On 2019-08-31, Gary Gregory wrote: > > > On Sat, Aug 31, 2019 at 10:58 AM

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Stefan Bodewig
On 2019-08-31, Gary Gregory wrote: > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski > 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.

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Romain Manni-Bucau
Le sam. 31 août 2019 à 17:42, Gilles Sadowski a écrit : > Le sam. 31 août 2019 à 17:30, Romain Manni-Bucau > a écrit : > > > > s/irrelevant/being transformed/ ;), tasks change, human stays > > No, it won't just be a transformation: Fulfilling a mission (at the > service of humans) requires some

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gilles Sadowski
Le sam. 31 août 2019 à 17:30, Romain Manni-Bucau a écrit : > > s/irrelevant/being transformed/ ;), tasks change, human stays No, it won't just be a transformation: Fulfilling a mission (at the service of humans) requires some measure of independence. Reliance on an external entity (for services

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Romain Manni-Bucau
s/irrelevant/being transformed/ ;), tasks change, human stays Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gilles Sadowski
Le sam. 31 août 2019 à 17:19, Romain Manni-Bucau a écrit : > > Works for me too Maybe another service that requires being logged in (?). > Looks cool, just needs synchro with infra If the above is true, then just another step towards making "infra" (and Apache) irrelevant in the not so far

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Romain Manni-Bucau
Works for me too Looks cool, just needs synchro with infra probably if we need secrets to deploy on nexus or so Le sam. 31 août 2019 à 17:08, Gary Gregory a écrit : > On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski > wrote: > > > Hello. > > > > Le sam. 31 août 2019 à 14:28, Gary Gregory a >

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gary Gregory
On Sat, Aug 31, 2019 at 10:58 AM Gilles Sadowski wrote: > Hello. > > Le sam. 31 août 2019 à 14:28, Gary Gregory a > écrit : > > > > Hi All: > > > > FYI: I've played a bit with GitHub Actions to run builds. You can see an > > example here for Commons BCEL: > > > >

Re: [bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gilles Sadowski
Hello. Le sam. 31 août 2019 à 14:28, Gary Gregory a écrit : > > Hi All: > > FYI: I've played a bit with GitHub Actions to run builds. You can see an > example here for Commons BCEL: > > https://github.com/apache/commons-bcel/actions Links returns "404". Gilles > > Gary

[bcel][all] GitHub Actions for Maven builds

2019-08-31 Thread Gary Gregory
Hi All: FYI: I've played a bit with GitHub Actions to run builds. You can see an example here for Commons BCEL: https://github.com/apache/commons-bcel/actions Gary