Build types: release -vs- dev #5

New Issue

djmil · 2024-08-22T22:54:02+02:00

djmil commented

2024-08-22 22:54:02 +02:00

Hustle free project development hinges on an ability of performing quick and efficient tests and delivering useful artifacts. Thus each iteration cycle of active search / development is facilitated by publishing a release which in it essence marks milestone achievement.

By default the build stage should build current (locally cloned) version of a project delivered in a form of a locally stored docker image. Which is used solely for the purpose of development iteration and testing.

$ ./build.sh
> ... sucessful

$ docker image ls
> djmil/gitea-pages:dev

While publish stage has to fetch latest tag and use it as a target version of a source code to run the build process against. Obviously, the tag should exist prior to the release preparation procedure. Than it should publish the resulting build to the docker hub.

$ ./build.sh -tag 0.1.0 -publish
> 1 checkout tag 0.1.0
> 2 build
> 3 publish to docker hub

Hustle free project development hinges on an ability of performing quick and efficient tests and delivering useful artifacts. Thus each iteration cycle of active search / development is facilitated by publishing a release which in it essence marks milestone achievement. By default the `build` stage should build current (locally cloned) version of a project delivered in a form of a **locally** stored docker image. Which is used solely for the purpose of development iteration and testing. ```bash $ ./build.sh > ... sucessful $ docker image ls > djmil/gitea-pages:dev ``` While `publish` stage has to fetch latest tag and use it as a target version of a source code to run the build process against. Obviously, the tag should exist prior to the release preparation procedure. Than it should publish the resulting build to the docker hub. ```bash $ ./build.sh -tag 0.1.0 -publish > 1 checkout tag 0.1.0 > 2 build > 3 publish to docker hub ```

djmil added this to the 0.1.0 milestone 2024-08-22 22:54:02 +02:00

djmil added the

feature

label 2024-08-22 22:54:02 +02:00

djmil added a new dependency 2024-08-22 22:58:03 +02:00

#2 Update readme

djmil removed a dependency 2024-08-22 22:58:27 +02:00

#2 Update readme

djmil commented

2024-08-22 23:31:13 +02:00

Dockerfile COPY vs ADD:

ADD is similar to COPY except for one distinct difference. ADD can fetch content from a URL (c)

ADD https://example.com/archive.zip /usr/src/things/
ADD git@github.com:user/repo.git /usr/src/things/

Dockerfile `COPY` vs `ADD`: > ADD is similar to COPY except for one distinct difference. ADD can fetch content from a URL [(c)](https://docs.docker.com/reference/dockerfile/#source) ```Dockerfile ADD https://example.com/archive.zip /usr/src/things/ ADD git@github.com:user/repo.git /usr/src/things/ ```

djmil added the

design

label 2024-08-22 23:45:33 +02:00

djmil referenced this issue from a commit

2024-08-25 17:47:37 +02:00

Build release -vs- local sources

djmil closed this issue

2024-08-25 17:47:37 +02:00

djmil referenced this issue from a commit

2024-08-25 18:08:36 +02:00

Build release -vs- local sources

Sign in to join this conversation.