Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Reduce fragility of standard workflow of fluid-publish

Description

The "standard" workflow of fluid-publish is a bit fragile -

i) it depends on the existence of a git remote named "upstream" - at the very least we should document this clearly, and, if possible, add a CLI task that can take this as a copy from an existing remote in order to assist the user

ii) if part of the workflow is already complete, the plugin will bomb out -

$ node publish.js --standard
fatal: tag 'v1.1.0' already exists
child_process.js:484
throw err;
^

Error: Command failed: git tag -a v1.1.0 -m 'Tagging the 1.1.0 release'
fatal: tag 'v1.1.0' already exists

In cases like this there should be some assistance to the user in how they could get the task to run - perhaps a command hint that they could run to get the repo into a suitable condition

iii) It would be nice if the default behaviour of the plugin in all cases was to echo commands that it was executing to the terminal as an indicator of progress

Environment

None

Activity

Show:

Justin Obara March 15, 2018 at 6:59 PM

PR ( https://github.com/fluid-project/fluid-publish/pull/5  ) merged into the project repo.

Justin Obara August 4, 2016 at 7:17 PM

Talked more about this in the IRC channel today ( https://botbot.me/freenode/fluid-work/2016-08-04/?msg=70783796&page=1 ). Will add templates for the hints as well and output those when an error occurs.

Justin Obara November 27, 2015 at 3:33 PM

Have started working on this in my https://github.com/jobara/fluid-publish/tree/FLUID-5799 branch.

i) added an option to specify the remote name, it will default to "upstream" but can be changed via the --options command line argument.

Fixed

Details

Assignee

Reporter

Components

Priority

Created October 27, 2015 at 3:59 PM
Updated March 15, 2018 at 6:59 PM
Resolved March 15, 2018 at 6:59 PM