Versions Compared

Old Version 2

changes.mady.by.user Unknown User (juhan)

Saved on

compared with

New Version 3

changes.mady.by.user Unknown User (juhan)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • pushing to branch "develop" - triggers a build and publishes to "latest"
  • tagging a version - triggers a build and publishes it as a version:
    • if the tag has a form "numbers.and.dots-RELEASE" (case insensitive) then the docker tag will be "release-numbers.and.dots"
      • example: 1.2.3-RELEASE becomes "release-1.2.3"
      • example: v-1.2.3 - nothing is triggered as only numbers and dots are allowed
    • if the tag has a form "numbers.and.dots" then docker tag will be: "numbers.and.dots"
      • example: 1.2.3 becomes "ver-1.2.3"
    pushing to any other branch besides "develop" - nothing is triggered and no images are builtonly if it matches:


Docker Tag

SourceComment
latestdevelopbuild everything pushed to "develop" branch and publish it under latest tag

release-{sourceref}

/^REL([0-9.]+)$/

configured for other rules to work. no build should actually trigger this

{\1}-{\2}

/^([0-9.]+)-([0-9A-Za-z.]+)$/


{\1}.{\2}.{\3}

/^([0-9]+)\.([0-9]+)\.([0-9]+)$/


{\1}.{\2}.{\3}.{\4}

/^([0-9]+)\.([0-9]+)\.([0-9]+)\.([0-9]+)$/



For autobuild to work the Dockerfile of each  has been split into two stages:

...