Team, As part of ongoing efforts to improve automated testing, the following NiFi issues introduced several updates to GitHub workflows:
- https://issues.apache.org/jira/browse/NIFI-9037 - https://issues.apache.org/jira/browse/NIFI-9040 - https://issues.apache.org/jira/browse/NIFI-9057 The primary ci-workflow continues to run for all pull requests and pushes to the main branch. In order to avoid unnecessary resource usage, the workflow now includes a concurrency setting that will cancel a running job on a push to the same branch. As a result, multiple updates in quick succession to a single pull request will result in only the last push continuing to build. This also impacts multiple updates to the main branch. When this occurs, GitHub cancels previous jobs for the specified branch with the following message: Canceling since a higher priority waiting request for 'branch' exists In addition to concurrency changes, there is a new system-tests workflow that runs every day at 00:00 UTC: https://github.com/apache/nifi/actions/workflows/system-tests.yml The project README includes an additional badge indicating the system-tests workflow status. The system-tests workflow runs integration tests in the nifi-system-test-suite and nifi-stateless-system-suite modules. These tests are not part of the standard continuous integration workflow, but they provide a very helpful indication of whether NiFi and NiFi stateless are functional at a system level. Reliable automated testing is vital to the continued health of the project, so thanks to everyone who contributes to the testing process! Regards, David Handermann
