This is great! Looking forward to it.

Would any metrics need to be migrated over to the new Jenkins?
http://metrics.beam.apache.org/



On Fri, Jun 12, 2020 at 9:57 AM Tyson Hamilton <tyso...@google.com> wrote:

> Very exciting! Thanks for the advanced notice Damian.
>
> On Fri, Jun 12, 2020 at 7:58 AM Damian Gadomski <
> damian.gadom...@polidea.com> wrote:
>
>> Hello,
>>
>> During the last few days, I was preparing for the Beam Jenkins migration
>> from builds.apache.org to ci-beam.apache.org. The new Jenkins Master
>> will be dedicated only for Beam related jobs, all Beam Committers will have
>> build configure access, and Beam PMC will have Admin (GUI) Access.
>>
>> We (in cooperation with Infra) are almost ready for the migration itself
>> and I want to share with you the details of our plan. We are planning to
>> start the migration next week, most likely on Tuesday. I'll keep you
>> updated on the progress. We do not expect any issues nor the outage of the
>> CI services, everything should be more or less unnoticeable. Just don't be
>> surprised that the Jenkins URL will change to https://ci-beam.apache.org
>>
>> If you are curious, here are the steps that we are going to take:
>>
>> 1. Create 16 new CI nodes that will be connected to the new CI. We will
>> then have simultaneously running two CI servers.
>> 2. Verify that new builds work as expected on the new instance (compare
>> results of cron builds). (a day or two would be sufficient)
>> 3. Move the responsibility of Phrase/PR/Commit builds to the new CI,
>> disable on the old one.
>> 4. Modify the .test-infra/jenkins/README.md to point to the new instance
>> and replace Post-commit tests status in README.md and
>> .github/PULL_REQUEST_TEMPLATE.md
>> 5. Disable the jobs on the old Jenkins and add a description to each job
>> with the URL to the corresponding one on the new CI.
>> 6. Turn off VM instances of the old nodes.
>> 7. Remove VM instances of the old nodes.
>>
>> In case of any questions or doubts feel free to ask :)
>>
>> Regards,
>> Damian
>>
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to