Martijn Visser created FLINK-40654:
--------------------------------------

             Summary: cron_snapshot_deployment jobs fail because 
build-nightly-dist.yml still points at tools/azure-pipelines/free_disk_space.sh
                 Key: FLINK-40654
                 URL: https://issues.apache.org/jira/browse/FLINK-40654
             Project: Flink
          Issue Type: Bug
          Components: Build System
    Affects Versions: 2.4.0
            Reporter: Martijn Visser


FLINK-40224 moved {{free_disk_space.sh}} from {{tools/azure-pipelines}} to 
{{tools/ci}} and updated jobs-template.yml, e2e-template.yml and the GitHub 
action, but not build-nightly-dist.yml, which still has two references to the 
old path:

{code}
tools/azure-pipelines/build-nightly-dist.yml:29:      - script: 
./tools/azure-pipelines/free_disk_space.sh
tools/azure-pipelines/build-nightly-dist.yml:87:      - script: 
./tools/azure-pipelines/free_disk_space.sh
{code}

Both cron_snapshot_deployment jobs fail immediately:

{code}
./tools/azure-pipelines/free_disk_space.sh: No such file or directory
##[error]Bash exited with code '127'.
{code}

cron_snapshot_deployment_binary was green in build 77434 (2026-07-25) and has 
failed in every master nightly since 77447 (2026-07-26), which ran on the 
FLINK-40224 commit. No nightly binaries have been published since. It also 
means the disk space fix from FLINK-40058 has not run on master since then.

cron_snapshot_deployment_maven has been failing since build 76959 (2026-07-10) 
for a different reason, FLINK-40145, and will still fail once this path is 
corrected.

https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=79017



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to