You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by Mario Kevo <ma...@est.tech> on 2022/09/23 10:26:02 UTC

Release manager permissions

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: mkevo@apache.org

Can someone give me these permissions, so I can start building a new patch release?

Thanks and BR,
Mario

Re: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
I updated your JIRA permission, please check. What is your DockerHub username?

Anthony


> On Sep 23, 2022, at 3:26 AM, Mario Kevo <ma...@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: mkevo@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.


Re: Release manager permissions

Posted by Owen Nichols <on...@vmware.com.INVALID>.
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 <ma...@est.tech>
Date: Sunday, September 25, 2022 at 11:42 PM
To: dev@geode.apache.org <de...@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 <ba...@vmware.com.INVALID>
Poslano: 23. rujna 2022. 20:15
Prima: dev@geode.apache.org <de...@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 <ma...@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: mkevo@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.

Re: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
BTW, you should now have access to DockerHub and bulk change in JIRA. Anything else you need to create the 1.15.1 release candidate?

Anthony


> On Sep 26, 2022, at 8:55 AM, Anthony Baker <ba...@vmware.com.INVALID> wrote:
> 
> ⚠ External Email
> 
> Looks like Docker is limiting access. I’ll need to rotate some people from the Docker org.
> 
> Anthony
> 
> 
>> On Sep 25, 2022, at 11:42 PM, Mario Kevo <ma...@est.tech> wrote:
>> 
>> ⚠ 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 <ba...@vmware.com.INVALID>
>> Poslano: 23. rujna 2022. 20:15
>> Prima: dev@geode.apache.org <de...@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 <ma...@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: mkevo@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.
>> 
> 


Re: Odg: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
Looks like Docker is limiting access. I’ll need to rotate some people from the Docker org.

Anthony


> On Sep 25, 2022, at 11:42 PM, Mario Kevo <ma...@est.tech> wrote:
> 
> ⚠ 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 <ba...@vmware.com.INVALID>
> Poslano: 23. rujna 2022. 20:15
> Prima: dev@geode.apache.org <de...@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 <ma...@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: mkevo@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.
> 


Odg: Release manager permissions

Posted by Mario Kevo <ma...@est.tech>.
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 <ba...@vmware.com.INVALID>
Poslano: 23. rujna 2022. 20:15
Prima: dev@geode.apache.org <de...@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 <ma...@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: mkevo@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.


Re: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
Hi Alberto,

All the existing concourse CI scripts are in GitHub [1] so it’s definitely possible for someone to stand up a Concourse deployment and use the current pipelines. I assume there are some domain names and certificates that may need to be transferred as well. This has worked well but could be a lot of work and learning to get started. Of course there are other tools as well. To date, I’m not aware of any interest from potential CI sponsors.

My experience with ASF resources is fairly out of date. When we used this back in the day, the testing took quite some time. I believe we had a daily job and release jobs. Perhaps the Jenkins tooling has been updated to allow more “pipeline-like” test jobs.

Anthony



[1] https://github.com/apache/geode/tree/develop/ci


On Sep 27, 2022, at 4:12 AM, Alberto Gomez <al...@est.tech>> wrote:

⚠ External Email

Hi,

Do you know if any company has offered to sponsor the CI pipelines? What would it take for such a company besides paying the bills? Would a migration be needed?

Regarding the old ASF Jenkins jobs, my understanding is that they would offer the same CI functionality as we have today, but they would be run on ASF provided resources which would most likely make the time to get results longer and less predictable. Is that correct?


Thanks,

Alberto
________________________________
From: Anthony Baker <ba...@vmware.com.INVALID>>
Sent: Friday, September 23, 2022 8:15 PM
To: dev@geode.apache.org<ma...@geode.apache.org> <de...@geode.apache.org>>
Subject: 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 <ma...@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: mkevo@apache.org<ma...@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.



Re: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
A few ASF links worth looking into:

https://infra.apache.org/services.html#build
https://builds.apache.org/
https://infra.apache.org/hosting-external-agent.html


On Sep 27, 2022, at 1:45 PM, Owen Nichols <on...@vmware.com.INVALID>> wrote:

⚠ External Email

Hi Mario, a basic concourse installation[1] needs a database (e.g. Postgres), the concourse web service, and 1 or more concourse workers.  A secrets store like Vault is also recommended.  These don’t have to be especially beefy (if hosting in GCP, something like gcp n2-standard-4 is fine).  Baseline operating costs for a concourse deployment could range from $100-1000 per month depending on what hardware or cloud provider is used and how many workers are used.

Geode pipeline jobs spawn additional instances in GCP to actually execute the tests.  The CPU, RAM, and disk specs for these machines are defined in geode/ci [2] and some jobs use as many as 96 CPUs for parallel execution.  In total, these spot instances cost on the order of $25 per PR commit + $75 per PR merged.

[1] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconcourse-ci.org%2Finstall.html&amp;data=05%7C01%7Cbakera%40vmware.com%7Ca9d8531cb8cd48365a8408daa0c93d0a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637999083443746661%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=3yeEMQS6gzEq%2Fu08d3L3AyJ2nrT0PhUxGQ9mk9svxN4%3D&amp;reserved=0
[2] https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2Fdevelop%2Fci%2Fpipelines%2Fshared%2Fjinja.variables.yml&amp;data=05%7C01%7Cbakera%40vmware.com%7Ca9d8531cb8cd48365a8408daa0c93d0a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637999083443746661%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=jualU0witOHsiGeaC3MTTGYj5aN9im8cLSfwJjps2wc%3D&amp;reserved=0

From: Mario Kevo <ma...@est.tech>>
Date: Tuesday, September 27, 2022 at 6:41 AM
To: dev@geode.apache.org<ma...@geode.apache.org> <de...@geode.apache.org>>
Subject: Odg: Release manager permissions
⚠ External Email

Hi Anthony,

I have a question regarding CI.
I saw the file in the geode repo with some values for machines on which tests are executed. https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2Fe2ac1113f8f6819095785be556bef8e080ab6988%2Fci%2Fpipelines%2Fshared%2Fjinja.variables.yml%23L92&amp;data=05%7C01%7Cbakera%40vmware.com%7Ca9d8531cb8cd48365a8408daa0c93d0a%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637999083443746661%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=B89hP4xyW3ncAGoM%2Fm%2FTPXrevROM%2FyNjJOSA8ZglVUU%3D&amp;reserved=0

So I have a question, what is the setup now that it is used on Concourse CI?
Do you have one or more machines(and how many) so tests can be executed in parallel? How many CPUs, RAM and disk sizes are used for them?

Thanks and BR,
Mario
________________________________
Šalje: Alberto Gomez <al...@est.tech>>
Poslano: 27. rujna 2022. 13:12
Prima: dev@geode.apache.org<ma...@geode.apache.org> <de...@geode.apache.org>>
Predmet: Re: Release manager permissions

Hi,

Do you know if any company has offered to sponsor the CI pipelines? What would it take for such a company besides paying the bills? Would a migration be needed?

Regarding the old ASF Jenkins jobs, my understanding is that they would offer the same CI functionality as we have today, but they would be run on ASF provided resources which would most likely make the time to get results longer and less predictable. Is that correct?


Thanks,

Alberto
________________________________
From: Anthony Baker <ba...@vmware.com.INVALID>>
Sent: Friday, September 23, 2022 8:15 PM
To: dev@geode.apache.org<ma...@geode.apache.org> <de...@geode.apache.org>>
Subject: 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 <ma...@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: mkevo@apache.org<ma...@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.


Re: Release manager permissions

Posted by Owen Nichols <on...@vmware.com.INVALID>.
Hi Mario, a basic concourse installation[1] needs a database (e.g. Postgres), the concourse web service, and 1 or more concourse workers.  A secrets store like Vault is also recommended.  These don’t have to be especially beefy (if hosting in GCP, something like gcp n2-standard-4 is fine).  Baseline operating costs for a concourse deployment could range from $100-1000 per month depending on what hardware or cloud provider is used and how many workers are used.

Geode pipeline jobs spawn additional instances in GCP to actually execute the tests.  The CPU, RAM, and disk specs for these machines are defined in geode/ci [2] and some jobs use as many as 96 CPUs for parallel execution.  In total, these spot instances cost on the order of $25 per PR commit + $75 per PR merged.

[1] https://concourse-ci.org/install.html
[2] https://github.com/apache/geode/blob/develop/ci/pipelines/shared/jinja.variables.yml

From: Mario Kevo <ma...@est.tech>
Date: Tuesday, September 27, 2022 at 6:41 AM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: Odg: Release manager permissions
⚠ External Email

Hi Anthony,

I have a question regarding CI.
I saw the file in the geode repo with some values for machines on which tests are executed. https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fgeode%2Fblob%2Fe2ac1113f8f6819095785be556bef8e080ab6988%2Fci%2Fpipelines%2Fshared%2Fjinja.variables.yml%23L92&amp;data=05%7C01%7Conichols%40vmware.com%7C31a853c3aad94f48e55508daa08e079f%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637998829122537833%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=rXjrDcVdEuU62xVMR%2FHZr8%2FAZVZVGUYTY61R4x2Qw%2BY%3D&amp;reserved=0

So I have a question, what is the setup now that it is used on Concourse CI?
Do you have one or more machines(and how many) so tests can be executed in parallel? How many CPUs, RAM and disk sizes are used for them?

Thanks and BR,
Mario
________________________________
Šalje: Alberto Gomez <al...@est.tech>
Poslano: 27. rujna 2022. 13:12
Prima: dev@geode.apache.org <de...@geode.apache.org>
Predmet: Re: Release manager permissions

Hi,

Do you know if any company has offered to sponsor the CI pipelines? What would it take for such a company besides paying the bills? Would a migration be needed?

Regarding the old ASF Jenkins jobs, my understanding is that they would offer the same CI functionality as we have today, but they would be run on ASF provided resources which would most likely make the time to get results longer and less predictable. Is that correct?


Thanks,

Alberto
________________________________
From: Anthony Baker <ba...@vmware.com.INVALID>
Sent: Friday, September 23, 2022 8:15 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: 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 <ma...@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: mkevo@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.

Odg: Release manager permissions

Posted by Mario Kevo <ma...@est.tech>.
Hi Anthony,

I have a question regarding CI.
I saw the file in the geode repo with some values for machines on which tests are executed. https://github.com/apache/geode/blob/e2ac1113f8f6819095785be556bef8e080ab6988/ci/pipelines/shared/jinja.variables.yml#L92

So I have a question, what is the setup now that it is used on Concourse CI?
Do you have one or more machines(and how many) so tests can be executed in parallel? How many CPUs, RAM and disk sizes are used for them?

Thanks and BR,
Mario
________________________________
Šalje: Alberto Gomez <al...@est.tech>
Poslano: 27. rujna 2022. 13:12
Prima: dev@geode.apache.org <de...@geode.apache.org>
Predmet: Re: Release manager permissions

Hi,

Do you know if any company has offered to sponsor the CI pipelines? What would it take for such a company besides paying the bills? Would a migration be needed?

Regarding the old ASF Jenkins jobs, my understanding is that they would offer the same CI functionality as we have today, but they would be run on ASF provided resources which would most likely make the time to get results longer and less predictable. Is that correct?


Thanks,

Alberto
________________________________
From: Anthony Baker <ba...@vmware.com.INVALID>
Sent: Friday, September 23, 2022 8:15 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: 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 <ma...@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: mkevo@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.


Re: Release manager permissions

Posted by Alberto Gomez <al...@est.tech>.
Hi,

Do you know if any company has offered to sponsor the CI pipelines? What would it take for such a company besides paying the bills? Would a migration be needed?

Regarding the old ASF Jenkins jobs, my understanding is that they would offer the same CI functionality as we have today, but they would be run on ASF provided resources which would most likely make the time to get results longer and less predictable. Is that correct?


Thanks,

Alberto
________________________________
From: Anthony Baker <ba...@vmware.com.INVALID>
Sent: Friday, September 23, 2022 8:15 PM
To: dev@geode.apache.org <de...@geode.apache.org>
Subject: 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 <ma...@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: mkevo@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.


Re: Release manager permissions

Posted by Anthony Baker <ba...@vmware.com.INVALID>.
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 <ma...@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: mkevo@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.