zalando-stups/skrop

SHOULD semantically version project artifacts . You MUST tag all versions in GitHub with the exact version name. E.g.: 0.1.0.

rgritti opened this issue · 3 comments

rgritti commented

Actual Status

There is no publishing concept in this project yet. We need to onboard one, applying that rule of using semantic versioning, GitHub versions and GIT tags.

Tasks

  • Document how to manually publish this project to Zalando Open-Source Docker Registry (including the manual GIT-Tag and GH-Version)
  • Configure Travis CI to perform that release task (check with Arpad how they do it)
    • Should it try to continuous-deliver at each merge to master?
    • If so, how to automatically "decide" which digit of the semantic version to increment?
  • Document how to manage versions (the ideal version of it, on top of the manual version already documented).
Adeynack commented

Travis and versions

Get inspiration from Skipper, task ci-trigger in their Makefile.

Adeynack commented

Last try here
Failed to GIT TAG the version. Check Travis log for error detail (near the end).

Adeynack commented

@danpersa @rgritti and other maintainers: I will leave it to you to re-scope this issue and close it if you will.

The current status is a milestone in itself. Now, Travis CI is bumping up automatically the patch version. See the README under section Versioning for details. It was unfortunately not possible in the time I had to work on this to find a more interesting solution. However, this actual solution, even if a bit manual, is an upgrade to not having automatic versioning at all.

No publishing of the artifact is done at all at this state. Only the version automatically being incremented.

Have a great continuation on this project!