Changeset View
Changeset View
Standalone View
Standalone View
jobs/templates/debian/update-for-release.yaml
- job-template: | - job-template: | ||||
name: 'debian/packages/{name}/update-for-release' | name: 'debian/packages/{name}/update-for-release' | ||||
project-type: pipeline | project-type: pipeline | ||||
parameters: | parameters: | ||||
- git-parameter: | - git-parameter: | ||||
name: GIT_TAG | name: GIT_TAG | ||||
type: PT_TAG | type: PT_TAG | ||||
description: git tag to process | description: git tag to process | ||||
sortMode: DESCENDING_SMART | sortMode: DESCENDING_SMART | ||||
selectedValue: TOP | selectedValue: TOP | ||||
- bool: | - bool: | ||||
name: DRY_RUN | name: DRY_RUN | ||||
description: Don't push the resulting changes to a Debian branch | description: Don't push the resulting changes to a Debian branch | ||||
default: false | default: false | ||||
- bool: | |||||
name: DOWNLOAD_ARTIFACT_FROM_PYPI | |||||
description: download the module artifact source from pypi | |||||
default: true | |||||
ardumont: As the default suggests, it's supposed to be on, always.
Especially for the swh-* modules we… | |||||
ardumontAuthorUnsubmitted Done Inline ActionsI misunderstood the step. ardumont: I misunderstood the step.
And `download_artifact_from_pypi` is badly named here.
The 'gbp… | |||||
dsl: | dsl: | ||||
!include-raw: update-for-release.groovy | !include-raw: update-for-release.groovy | ||||
As the default suggests, it's supposed to be on, always.
Especially for the swh-* modules we control (and upload to pypi).
It's only expected to be used for external dependencies as a first draft.
A better solution is always welcome.
Might be just digging around the gbp import-origin step (from update-for-release job) to improve it and not depend on the pypi-upload job?