Skip to content

Tool spreadsheet for releases

jbradbury edited this page Jul 30, 2018 · 4 revisions

The spreadsheet for container releases contains all relevant data for tracking the container release process in a single place. It draws information directly from Jenkins (builds data) and GitHub (revisions and changes on the different branches), as well as the intended state.

For a new Release

We suggest that the release manager duplicates the columns created for Cerebellin (highlighted in purple) for each new release. Columns are:

  • Status of container (<release-name>): manually filled per container by the developer of that container or release managers. Shows whether the container will make it to the release or not. Not making it to the release means that it shouldn't make it to the table of containers for the release notes AND that is either commented on the set of tools in Galaxy, or that in Galaxy is simple left at the state it was in the previous release.

  • Current tag on <release-name> release branch: This column is automatically filled, and inspects the content of the tool to containers mapping file in Galaxy in the release branch for the release in question, to obtain the current tag for that container being used. Before the Galaxy release actually happens, ALL tags here should be release tags.

  • <release-name> tag properly set: compares the latest release tag available through Jenkins with the current tag set on the previous column, giving a "yes" if they match. If they don't match it means that the either the tool needs a new release (and that the release branch for Galaxy is pointing to a dev tag) or that the tool has been released, but Galaxy setup is not yet pointing to the release tag.

  • Needs new release for <release-name>: A manually set column by the developer of the container or the release managers that defines whether a new release needs to be done for the tool container, to be later fixed on Galaxy. This is used for some status counts.

The summary tab aims to be a place where you can capture time snapshots of the state of the release (see examples there for Cerebellin). This could be replicated for each new release.

Clone this wiki locally