Ok lets start with jenkins, i like the idea On Tue, 9 Feb 2021 at 11:58 Christofer Dutz <[email protected]> wrote:
> Well Bertty, > > that sort of theoretical. Believe me. > As soon as you're part of such a huge organization as Apache, you tend to > have problems you don't as an individual. > > - Quotas on the CI server per account (All Apache projects run as one > account) > - We don't have Admin Rights for the Apache orgnaization (Only infra has > that) > - There are no Technical users to deploy stuff to Apache Infra (Nexus) and > using personal credentials will immediately disable them. > - ... > > Let's start with Jenkins and in paralell start moving to Github Actions, > if the project wants to. > > This way we have something working and don't have to rush the other option. > > Chris > > > > -----Ursprüngliche Nachricht----- > Von: bertty contreras <[email protected]> > Gesendet: Dienstag, 9. Februar 2021 15:32 > An: [email protected] > Cc: [email protected] > Betreff: Re: Finished adjusting the wayang build to Apache > > In the case of the github action are secrets that we can set like for > credential and all of it, also we can put conditions before to execute some > action. > > El mar, 9 feb 2021 a las 11:26, Christofer Dutz (< > [email protected]>) > escribió: > > > Well I just added the stuff and askted for Infra enabling it for us so > > we have something to discuss. > > > > I am on the builds@apache list and recently it seems to be full of > > people complaining about inaceptable build-times. I guess the main > > reason is that Jenkins is on Apache infrastructure. We have full > > control over it and it's easy for us to push to Apache infrastructure > (Maven repo). > > > > On Github Actions, the problem is that the build agent is not an ASF > > machine and not managed by Apache. So there have to be a number of > > hoops we need to jump through to allow these builds to push SNAPSHOTS > > and to allow committer commits to trigger a build, but not > > non-apache-comitters (like in the case of PRs). > > > > This isn't something we are stuck with ... I added the config in a way > > that we can simply delete it and use Github Actions. > > > > Chris > > > > > > > > -----Ursprüngliche Nachricht----- > > Von: bertty contreras <[email protected]> > > Gesendet: Dienstag, 9. Februar 2021 15:18 > > An: [email protected] > > Cc: [email protected] > > Betreff: Re: Finished adjusting the wayang build to Apache > > > > Hi, > > > > I figure out that many projects are setting up the github actions, and > > personally I used and is not that complicated and even sometimes is > easier. > > > > Also @Rodrigo were posted one issue to change to Github actions. > > > > > > https://issues.apache.org/jira/projects/WAYANG/issues/WAYANG-10?filter > > =allopenissues > > > > Personally, I preferred Github Actions, however, if you pick Jenkins I > > don't see any problem. > > > > Best regards, > > Bertty > > > > > > On Tue, 9 Feb 2021 at 10:21 Christofer Dutz > > <[email protected]> > > wrote: > > > > > Hi all, > > > > > > so I just pushed some initial changes for Wayang to put stuff in > > > place Apache requires. > > > > > > I would now like to add a Jenkinsfile to simplify the setup on > > > Apache's Jenkins. We need this in order to start distributing > SNAPSHOTs. > > > Alernately I think we could use Github Actions, but I'm hearing > > > quite a bit of complaints fort hat. > > > > > > Is this ok? > > > > > > Chris > > > > > >
