summaryrefslogtreecommitdiffstats
path: root/doc/developer
diff options
context:
space:
mode:
authorDonatas Abraitis <donatas@opensourcerouting.org>2023-09-05 07:54:27 +0200
committerDonatas Abraitis <donatas@opensourcerouting.org>2023-09-05 07:54:27 +0200
commitb32fd280feb56a133c2a5a83f6e98b1d1c6f7bbc (patch)
treecb3c0888c7898a03337e4763c1d5790bc5fc042b /doc/developer
parentMerge pull request #14346 from opensourcerouting/frr-format-gcc-13 (diff)
downloadfrr-b32fd280feb56a133c2a5a83f6e98b1d1c6f7bbc.tar.xz
frr-b32fd280feb56a133c2a5a83f6e98b1d1c6f7bbc.zip
doc: Reuse $TAG for git checkout when building Docker images
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
Diffstat (limited to 'doc/developer')
-rw-r--r--doc/developer/frr-release-procedure.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/developer/frr-release-procedure.rst b/doc/developer/frr-release-procedure.rst
index 6088b52da..9378637de 100644
--- a/doc/developer/frr-release-procedure.rst
+++ b/doc/developer/frr-release-procedure.rst
@@ -152,11 +152,11 @@ Stage 2 - Staging
3. Suppose we are releasing 8.5.0, then ``X.Y.Z`` is ``8.5.0``. Run this:
.. code-block:: console
-
+
cd /home/builduser/frr
TAG=X.Y.Z
git fetch --all
- git checkout frr-<version>
+ git checkout frr-$TAG
docker buildx build --platform linux/amd64,linux/arm64,linux/ppc64le,linux/s390x,linux/arm/v7,linux/arm/v6 -f docker/alpine/Dockerfile -t quay.io/frrouting/frr:$TAG --push .
git tag docker/$TAG
git push origin docker/$TAG
@@ -165,7 +165,7 @@ Stage 2 - Staging
create a git tag corresponding to the commit that the image was built
from and upload that to Github. It's important that the git tag point to
the exact codebase that was used to build the docker image, so if any
- changes need to be made on top of the ``frr-<version>`` release tag, make
+ changes need to be made on top of the ``frr-$TAG`` release tag, make
sure these changes are committed and pointed at by the ``docker/X.Y.Z``
tag.