Thank you for doing this. Is there a list of jobs that will be disabled? I am particularly curious about: website publishing job (which I need to use manually sometimes) and the job that publishes daily staging builds (which we share with users sometimes.)
Thank you. Ahmet On Tue, Sep 12, 2023 at 11:14 AM Danny McCormick via dev < dev@beam.apache.org> wrote: > Hey everyone, I wanted to let you know that as part of the migration from > Jenkins to GitHub Actions we are going to start disabling Jenkins jobs if > they have a corresponding GitHub Actions job that has been running > successfully for a while. We are starting with Yi's PR here - > https://github.com/apache/beam/pull/28316. This is the next step in the > process we kicked off last year [1] now that self-hosted runners have been > in place and working for a while [2]. > > We will not migrate jobs until we've confirmed we have parity with the > existing Jenkins implementations (for example, some jobs are still missing > test publishing and we won't remove the Jenkins version until they have > it). In the meantime, migrating some load off should help reduce the > overall load on Jenkins so that it experiences fewer issues. > > If you have any objections with this approach, please respond here. If you > run into any problems, please file an issue and tag me (@damccorm), Yi > (@abacn), Andrey (@andreydevyatkin), or Vlado (@volatilemolotov) - or just > tag all of us :). > > Thanks, > Danny > > [1] https://lists.apache.org/thread/0brbkmbd522d1ow43gx5b13dmywt2dgn > [2] - https://lists.apache.org/thread/3k1owt5k16byv39b9lszd3l7qv7od4r8 >
