Versions Compared

Old Version 3

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

Saved on

compared with

New Version 4

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

Saved on

Key

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

...


Autobuild has been configured for these repositories with following setup:to follow the same principles as already used with publishing to JFrog Artifactory - this means that one can trigger a build by pushing to branch "develop"

...

and by creating a release (tag) in Github. The only exception is that pushing to other branches besides "develop" doesn't trigger creating image in Docker Hub.

Dockerhub autobuild configuration:

Docker Tag

SourceComment
latestdevelop
build everything pushed
Every push to "develop" branch is built and
publish it
published under tag "latest
tag
".

release-{sourceref}

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

configured for other rules to
Without this configuration Docker Hub doesn't work.
no
No build should actually trigger this.

{\1}-{\2}

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

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

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

Releases like "1.3.5-M.1", "1.5.7-RC.1", "1.5.7.1-RC.1" and "2.0.0-RELEASE"

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

.{\4}

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

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

$/

Releases like "2.0.0"


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

  • build stage - builds the jar. Only the jar is passed to the run stage.
  • run stage - runs the jar built