ExternalVendorCode/gns3-registry
1
0
Fork 0
mirror of https://github.com/GNS3/gns3-registry.git synced 2024-12-18 20:37:57 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Docker build tool renamed to docker_make

Browse Source 
The build tool behaves more like make, it builds only the changed images.
This commit is contained in:
Bernhard Ehlers 2023-12-15 19:51:41 +01:00
parent 4a875377a7
commit 67c7b12cb1
3 changed files with 10 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/bin/docker_build → .github/bin/docker_make vendored
View File

@ -16,10 +16,10 @@
# along with this program. If not, see <http://www.gnu.org/licenses/>.
"""
docker_build - (re)build outdated docker images
docker_make - (re)build outdated docker images
usage: docker_build [--help] [--all] [--dir DIR] [--dry-run] [--file FILE]
[image ...]
usage: docker_make [--help] [--all] [--dir DIR] [--dry-run] [--file FILE]
[image ...]
positional arguments:
image images to build additionally

12
.github/docker_build.md → .github/docker_make.md vendored
View File

@ -18,17 +18,17 @@ files, that got an update. Then a manual trigger is needed.
## Build Tool
The `docker_build` tool reads a configuration file and
The `docker_make` tool reads a configuration file and
then starts building images with `docker buildx build`.
If `docker_build` is launched without arguments, it checks
If `docker_make` is launched without arguments, it checks
all configured images for an update of the base image.
Additionally it checks, if `git` shows an update of
the directory containing the docker build context.
When at least one of these conditions is met, the tool
starts a rebuild of that image.
When `docker_build` is run with some image names as
When `docker_make` is run with some image names as
arguments, then these images are additionally built.
When using a base image name as an argument, then all
images with that base image are rebuilt.
@ -72,7 +72,7 @@ The target image may contain the full name, in which
case it will contain one or more '/' characters.
Another option is to specify only the last part of the
image name. Then `docker_build` uses the `DOCKER_REPOSITORY`
image name. Then `docker_make` uses the `DOCKER_REPOSITORY`
environment variable as its initial part. For example, an
DOCKER_REPOSITORY value of "ghcr.io/b-ehlers" plus the image
name of "alpine-1" results in "ghcr.io/b-ehlers/alpine-1".
@ -118,7 +118,7 @@ DOCKER_LOGIN_GH="ghcr.io github-user github-password"
uses YAML files in the .github/workflows directory
to define, which tasks should be run.
Before `docker_build` can be run the following steps
Before `docker_make` can be run the following steps
need to be done:
* Check out the repository code
@ -127,7 +127,7 @@ need to be done:
* Login to the Container Registries
* Install python requirements
Then `docker_build` can be executed,
Then `docker_make` can be executed,
normally without any arguments.
But what, when an image build needs to be forced?

2
.github/workflows/build-docker-images.yml vendored
View File

@ -110,4 +110,4 @@ jobs:
fi
# use option --dir to use a subdirectory as a docker base dir
python3 "$GITHUB_WORKSPACE/.github/bin/docker_build" --dir "docker" "$@"
python3 "$GITHUB_WORKSPACE/.github/bin/docker_make" --dir "docker" "$@"