[bcel][all] GitHub Actions for Maven builds

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

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

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 ---

Re: [VOTE] Release Apache Commons Text 1.8 based on RC1

Waiting for nexus to come back online (otherwise successful validations). > On Aug 30, 2019, at 4:06 PM, Gary Gregory wrote: > > We have fixed quite a few bugs and added some enhancements since Apache > Commons Text 1.7 was released, so I would like to release Apache Commons > Text 1.8. > > Ap

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

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: > > > > https://github.com/apache/common

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

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

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 futu

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

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

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 c

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

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

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. Stefa

Re: [VOTE] Release Apache Commons Text 1.8 based on RC1

+1 validated with java 8 and 11, reports all good, signatures all look good, and the release notes look good. > On Aug 30, 2019, at 4:06 PM, Gary Gregory wrote: > > We have fixed quite a few bugs and added some enhancements since Apache > Commons Text 1.7 was released, so I would like to relea

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

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 Gilles

Re: [bcel][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 Actions are more of a replacement for Travis currentl

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

As another data point, we (Univ. of Wash. PLSE dept) moved off of Travis to a combination of CIrcleCI and Azure Pipleines. Mark -Original Message- From: Gary Gregory [mailto:garydgreg...@gmail.com] Sent: Saturday, August 31, 2019 10:22 AM To: Commons Developers List Subject: Re: [bcel]

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

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 https://travis-ci.org/apache/co

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 a