[CI] Nightly Restart fails due to Non-Fast-Forward Error in Changelog Pipeline

[amrita-shrestha]

Currently, the nightly run cannot be restarted if it fails, particularly due to issues in the changelog pipeline. When attempting to restart, the process fails because the nightly branch is behind the latest branch, resulting in a non-fast-forward error.

Most of the time, before restarting the nightly run, a pull request (PR) gets merged, causing the local nightly branch to fall behind the remote branch.

Build:

• https://drone.owncloud.com/owncloud/ocis/42859/6/5

[phil-davis]

Maybe you can change .drone.star so that the changelog pipeline is not run in the nightly build. The nightly build is only for verification of test results, it should not "rebuild" the changelog anyway.

Or just adjust the "changelog" pipeline so that it does not do the "publish" step when running as "nightly".

The failing sequence is probably because changelog pipeline detects an extra change, which has arrived in master recently, and generates the changes for the changelog, then tries to push the changed changelog. But that fails because the latest master branch already has a new commit with the changed changelog.

[saw-jan]

Most of the time, before restarting the nightly run, a pull request (PR) gets merged, causing the local nightly branch to fall behind the remote branch.

The transifex commit (automatic - runs nightly) is one of the main reasons for the commit head change. PR merge is a rare case.

[saw-jan]

Maybe you can change .drone.star so that the changelog pipeline is not run in the nightly build. The nightly build is only for verification of test results, it should not "rebuild" the changelog anyway.

yeah, we do not run the changelog pipeline in the nightly build of desktop-client ci: https://drone.owncloud.com/owncloud/client/20262

[saw-jan]

@kobergj Is it okay to disable the changelog pipeline for nightly CI runs?

[kobergj]

Yes. We don't need the changelog pipline in nightly ci runs. 👍