Page MenuHomePhabricator

Document how to execute releasing the specified version of Wikibase software suite using the release pipeline
Closed, ResolvedPublic5 Estimated Story Points

Description

As a Wikibase Release Manager I want to build the specific version of Wikibase software suite, so that it can be released (duh).

Input to the pipeline when triggered is going to be the version of "main" components (e.g. Mediawiki) that should be used in the release packages built.
Output will be the set of release artifacts compatible with the version provided.

Technical issue to solve/agree on:

  • Different versions of software elements should be possible to be built using the pipeline. Possible solution: provide versions to env files separate for different runs, have separate env files, and pass the version to use to Makefile.

Developers will provide instructions on how to verify the right version in included in the release artifacts.

Acceptance criteria:

  • Release pipeline generates the release artifacts based on the version of the "main" components provided
  • Use of release pipeline is documented in the README

Event Timeline

WMDE-leszek set the point value for this task to 5.

Say we have a list of .env files which specify the versions of the individual components.

These could be read by the workflow. We could then either have the workflow "dispatched" see: https://github.blog/changelog/2020-07-06-github-actions-manual-triggers-with-workflow_dispatch/ or specific ones could be triggered by Cron

Maybe there should always be a .env in the root of the folder and this is "run" on every push to master.

Added another PR restructuring all of the documentation to use an index with links -> https://github.com/wmde/wikibase-release-prototype/pull/21