Skip to content

Inconsistencies in documentation

https://freexian-team.pages.debian.net/debusine/tutorials/getting-started-with-debusine.html talks about

Debusine can run many different workflows

and

You can find out what workflow templates are currently available by looking at the workspace in the web interface (e.g. http://debusine.internal/debusine/System/ or https://debusine.debian.net/debian/developers/).

but the linked pages show completely different workflow sets.

https://freexian-team.pages.debian.net/debusine/tutorials/getting-started-with-debusine.html says

debusine create-workflow debian-qa-unshare <<END
source_artifact: 536
codename: trixie
END

Or, if you’re using debusine.debian.net:

debusine create-workflow --workspace developers upload-to-unstable <<END
source_artifact: 536
END

Without digging in further: Are those workflows really equivalent? If yes: Why are they named so differently?

For me as a cautious newcomer it would be good to have a workflow described that doesn't target immediately an upload option to the archive. While this is probably one main feature of debusine I at least am reluctant to trigger actions that could result in a real upload. So please clarify that an upload job will stall until the signature is provided and be invalidated after a certain time without signature action.

Anyway I would appreciate an example to e.g. run just the autopkgtests of a package above the upload example to get familiar with debusine with an "non-dangerous" option first.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information