Hi Mario, you won’t need any Concourse permissions for Geode 1.15.x patch release(s) in the next two months, as the relevant “main”[1] and “rc”[2] pipelines already exist (just skip the deploy_rc_pipeline step).
[1] https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-15-main [2] https://concourse.apachegeode-ci.info/teams/main/pipelines/apache-support-1-15-rc From: Mario Kevo <mario.k...@est.tech> Date: Sunday, September 25, 2022 at 11:42 PM To: dev@geode.apache.org <dev@geode.apache.org> Subject: Odg: Release manager permissions ⚠ External Email Hi Anthony, I still don't have permission for Concourse. I logged in with a GitHub account and saw that I'm not authorized to run jobs. Username: mkevo The username for Docker Hub is the same: mkevo. Thanks, Mario ________________________________ Šalje: Anthony Baker <bak...@vmware.com.INVALID> Poslano: 23. rujna 2022. 20:15 Prima: dev@geode.apache.org <dev@geode.apache.org> Predmet: Re: Release manager permissions Just a reminder to all: we need to find an alternative to the VMware-sponsored CI pipelines currently in use. Any ideas? Should we try to resurrect the old ASF Jenkins jobs? Anthony > On Sep 23, 2022, at 3:26 AM, Mario Kevo <mario.k...@est.tech> wrote: > > ⚠ External Email > > Hi devs, > > I need the following permissions for the release manager: > > * bulk modification permission on Apache Geode JIRA > * permission to deploy pipelines to Geode CI > * Docker Hub credentials with permission to upload Apache Geode to Docker > Hub > > username: mkevo > mail: mk...@apache.org > > Can someone give me these permissions, so I can start building a new patch > release? > > Thanks and BR, > Mario > > ________________________________ > > ⚠ External Email: This email originated from outside of the organization. Do > not click links or open attachments unless you recognize the sender.
