Revise publish sub-command to eliminate pipeline conditionals
Feature: internalise release id conditional logic for publish sub-command As a user I want a single sub-command to handle the various scenarios of when to publish or not to publish build artifacts.
In general the workflow of build harness tries to eliminate complexity in the pipeline implementation so that the pipeline becomes a sequence of calling the various build_harness sub-commands without any additional support in the pipeline except perhaps for any required secrets. Presently the publish
sub-command requires conditional logic in the pipeline for when to publish and when not to and in the example .gitlab-ci.yml
implementation of the project itself three publish jobs with conditional logic are required to cover off the necessary scenarios.
Like the package
sub-command, the publish
sub-command can be driven by the release id, with an optional flag to determine if pre-release packages are published, or not.