Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Automatically use most recent tag as default version

See original GitHub issue

Is your feature request related to a problem? Please describe. Automation is nice. Setting the default version can be a bit of a hassle when you have many workflows. Would be nice if we could set automatically.

Describe the solution you’d like This could be either set on Dockstore or in a .dockstore.yml.

If in .dockstore.yml could go in a general config section. ex.

workflows:
   - subclass: ...
     primaryDescriptorPath: ...
     config:
        defaultVersion: tag/branch/manual

If on Dockstore, have a place where a user can set the default version to be automatic. There could be a checkbox that when clicked, will automatically update the default version. I think it is fine if we default this to true for new workflows and default to most recent tag.

They could have a few options - most recent tag, most recent branch, most recent tag/branch

I am leaning towards the second option as it works for all workflows.

┆Issue is synchronized with this Jira Story ┆Fix Versions: Dockstore 1.11 ┆Issue Number: DOCK-1508 ┆Sprint: Sprint 62- Mako shark ┆Issue Type: Story

Issue Analytics

State:
Created 3 years ago
Comments:17 (9 by maintainers)

Top GitHub Comments

1reaction

agduncan94commented, Aug 6, 2020

After more thought, I think that the dockstore.yml should not have workflow specific information. It should only ever have version specific information. I think the default branch should be set on Dockstore.

0reactions

unito-botcommented, Jun 10, 2021

➤ Denis Yuen commented:

Was able to add a new version and switch to it from the .dockstore.yml

Nice!

Webservice ( https://github.com/dockstore/dockstore/releases/tag/1.11.0-rc.0 ) - 1.11.0-rc.0

UI ( https://github.com/dockstore/dockstore-ui2/releases/tag/2.8.0-rc.1 ) - 2.8.0-rc.1

Compose Setup ( https://github.com/dockstore/compose_setup/releases/tag/1.11.0-rc.1 ) - 1.11.0-rc.1

Deploy ( https://github.com/dockstore/dockstore-deploy/releases/tag/1.11.0-rc.0 ) - 1.11.0-rc.0

Top Results From Across the Web

Automatic tagging of releases - git - Stack Overflow

I wrote this to help with updating tags incrementally e.g. 1.0.1 to 1.0.2 etc. 2020 update: I have posted an improved version beneath/here....

Getting latest tag on git repository - gists · GitHub

The command finds the most recent tag that is reachable from a commit. # If the tag points to the commit, then only...

Artifact default version is not applied on automatic release

All artifacts are configured with "Latest from the build pipeline default branch with tags" as "Default version" (Tag fields is blank).

git-tag Documentation - Git

Make a GPG-signed tag, using the default e-mail address's key. ... You really want to call the new version "X" too, even though...

add_git_tag - fastlane docs

add_git_tag. This will add an annotated git tag to the current branch. This will automatically tag your build with the following format: <grouping> ......