Hi, On Fri, 15 Aug 2025, NoisyCoil wrote: > Since uploading is considered an optional task, shouldn't the workflow be > considered completed without it being executed? Or shouldn't this be > configurable at least?
When you start a workflow, you can pass parameters to the workflow. In the case of the `debian_pipeline` workflow [1], it supports an `enable_upload` parameter... and for the `upload-to-unstable` workflow template, we set it to True since the goal is to upload. [1] https://freexian-team.pages.debian.net/debusine/reference/workflows/specs/debian-pipeline.html [2] https://debusine.debian.net/debian/developers/workflow-template/upload-to-unstable/ However, currently, any parameter set at the workflow template level is a parameter that you can't override. So, no, it's currently not possible to disable that step. But we have plans to improve this and it's even scheduled for this quarter: https://salsa.debian.org/freexian-team/debusine/-/issues/869 So hopefully by the end of the quarter you will be able to do: $ dput -O debusine_workflow_data.enable_upload=false debusine.debian.net foo.changes > P.S.: I am not a DD yet (waiting for addition to the keyring) so I cannot > yet access Debusine to check if such configuration actually exists :-) But > based on what you're saying it sounds like it does not. The expectation is that you abort the workflow if you don't want to upload. (But you take that decision after having seen the result of the QA tasks and the upload task is created when the workflow is created, together with all the QA tasks too.) Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hert...@debian.org> ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS
