You should be able to adapt tools/azure-pipelines/build-apache-repo.yml [1] in your branch as a "debug" commit to add the steps/stages that you're planning to include in a test CI run of your PR (this debug commit should be removed before merging the PR). The ci stage will be executed as part of your PR. You can get inspired by the cron_build stage which is enabled in the nightly runs.
[1] https://github.com/apache/flink/blob/master/tools/azure-pipelines/build-apache-repo.yml On Thu, Sep 7, 2023 at 10:54 AM Gabor Somogyi <gabor.g.somo...@gmail.com> wrote: > Hi All, > > I've created a PR <https://github.com/apache/flink/pull/23359> which > changes "tools/releasing/create_binary_release.sh" which is called by > "Build snapshot binary release" nightly job. Is there a possibility to > double check that the PR is > not breaking it? > > The question can be generalized however. There are surrounding jobs (for > ex. python wheel build) > which are not executed in a PR (which is fine because that would be > overkill). But the question is > how to test them to minimize code breaks? > > Thanks in advance! > > BR, > G >
