Extend `.gitlab-ci.yml` to support binary release assets

Release notes

Problem to solve

Extend the release: keyword to support file and tranform into release-cli commands.

Intended users

• Rachel (Release Manager)
• Sasha (Software Developer)

User experience goal

The user should be able to create releases and attach files to them in a single .gitlab-ci.yml release job.

Proposal

Extend the release: keyword to support file.

Example release yaml:

release:
  assets:
    links:
      - name: Mock binary
        url: <generic registry>/<namespace-project>/<tag>/bin/mock-bin.dmg
        file: bin/mock-bin.dmg
        filepath: pretty_link_name

Example release-cli commands:

release-cli create --tag-name v1.2.3 --assets-link='{"name": "Mock binary", "url":"<generic registry>/<namespace-project>/<tag>/bin/mock-bin.dmg", "file": "bin/mock-bin.dmg", "type": "other", "filepath": "/pretty_link_name" }'

Further details

• MVC using generic packages #38379 (closed)
• Improved approach removing the extra upload job and giving that responsibility to the release-cli as found in release-cli#54 (closed)

Permissions and Security

Documentation

• Add documentation about upload_dir and package_name to the release section
• Update complete examples of creating releases

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Tech evaluations

• #38379 (closed)
• release-cli#54 (closed)

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.