deployment-iso

Commit Graph

Author	SHA1	Message	Date
Sipwise Jenkins Builder	b685559634	MT#64349 Update bootstrap key with fixed SHA-1 situation Now it contains: pub rsa4096 2015-03-05 [SC] [expires: 2029-10-12] 68A702B1FD8E422AAAA1ADA3773236EFF411A836 uid [ unknown] Sipwise GmbH (Sipwise Repository Key) <support@sipwise.com> sub rsa4096 2015-03-05 [E] [expires: 2029-10-12] pub rsa4096 2011-06-06 [SC] F7B8A739CE638D719A078C9859104633EE5E097D uid [ unknown] Sipwise autobuilder (Used to sign packages for autobuild) <development@sipwise.com> sub rsa4096 2011-06-06 [E] pub rsa4096 2023-08-04 [SCEA] [expires: 2033-08-01] F0A595D85C375447BB09F25E34A72CE4979CA98A uid [ unknown] Sipwise autobuilder <development@sipwise.com> pub rsa4096 2024-08-14 [SCEA] [expires: 2034-08-12] A164D3A12AC0F6AB8F737EF66D1B7D01D2AD9C24 uid [ unknown] Sipwise autobuilder <development@sipwise.com> pub rsa4096 2025-06-09 [SCEA] [expires: 2035-06-07] 6ACB2E82869CD45C93DA14DF617ECBC182DAAB8B uid [ unknown] Sipwise autobuilder <development@sipwise.com> Change-Id: Icfe8b7b94126725026577b6379966b97d61f9a98	7 months ago
Michael Prokop	53cb7772da	MT#60283 Update grml-live to version 0.54.1 Lots of changes took place in between v0.53.2 and v0.54.1. To ensure to follow upstream changes, let's make sure our configuration avoids relying on features that are going to be dropped in upcoming versions. Relevant changes: * FAI_DEBOOTSTRAP=... became BOOTSTRAP_MIRROR=... (without the Debian release name, but just requiring the mirror URL) * the templates command line option `-t ...` is considered deprecated, now that boot templates are also class-based configuration files (via ${GRML_FAI_CONFIG}/config/media-files/$CLASS) Let's keep our templates as-is, but provide grml_build/config/media-files/SIPWISE as symlink to our templates directory * GRMLBASE and architecture-specific classes are now enabled by default and no longer should be included in the grml-live invocation, so drop GRMLBASE + AMD64 class names in wrapper.sh * The RELEASE class (which cleans up /root and /home/grml) is also automatically enabled, but since we e.g. ship files like /root/puppet.gpg we need to disable this new behavior by enabling the new "-R" option Change-Id: I66dc8c685decac25370234844e33d4be60dea08a	1 year ago
Michael Prokop	8647b3d7b5	MT#60283 Update to grml-live version v0.53.2 + Debian/trixie grml-live had >410 commits since v0.47.7 (which we used so far), including getting rid of FAI (through our own so called minifai implementation), supporting mmdebstrap for bootstrapping (and using it by default nowadays), and usage inside non-privileged containers. Misc changes: * No longer run any docker containers with --privileged, now that this is handled all internally from within grml-live's build driver * Upgrade everything to Debian/trixie (given that we also switched our trunk/master branch towards trixie also) * Provide wrapper.sh script to avoid maintaining it also inside jenkins-configs' jobs/internal/grml/build_grml_image.sh (which meant going through yet another layer and every single change to it required a full jenkins-config change). Update README.txt accordingly to provide usage examples. * Set up keyring for custom bootstrapping using our own mirror, using grml_build/config/bootstrap-keyring/SIPWISE and deploying /usr/share/keyrings/sipwise-archive-keyring.gpg via updatebase hook script * Ship .gitignore files to ignore directories that are relevant for the build process, though we also don't need to explicitly create them on every single build any longer. * Update configuration layout for grml-live change as of upstream version v0.51.0 (see grml-live.git commit f1dc42a), moving from /etc/grml/fai/config into /usr/share/grml-live/config. * Update configuration layout for grml-live change as of upstream version 0.53.0 (see grml-live.git commit 3a4bd41), changing schema files/<path>/<CLASS> into files/<CLASS>/<path>, class/<CLASS>.var into env/<CLASS> and hooks/<hookname>.<CLASS> into hooks/<CLASS>/<hookname>. * Add memtest86+ + ipxe to SIPWISE class, so they are available for boot menu integration (grml-live uses addons from grml_chroot and no longer from host system). grml_build/Dockerfile related changes: * Adjust ENV usage (fixes `LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 9)`) * Add snippet for usage with debian:trixie-slim as base docker image (useful for debugging e.g. without access to Sipwise systems) * Install ca-certificates (needed for access to https://github.com/ with debian:trixie-slim) * Switch from grml-live v0.47.7 to v0.53.2 * Drop deprecated dependencies that are no longer relevant with recent grml-live versions (fai-client + fai-server get replaced by our own minifai implementation, mksh is no longer relevant for grml-live, and isolinux, ipxe, memtest86+ + syslinux are used from the grml_chroot instead of from the host system, also see above) * Instead install mmdebstrap (which is much faster for bootstrapping than debootstrap), now being supported and the default, thanks to our minifai implementation * Drop /root/.bash_history, as we switched towards our custom wrapper.sh script t/Dockerfile related changes: * Mark /code as safe directory for git, to not fail with "fatal: detected dubious ownership in repository at '/code'" * Adjust ENV usage (fixes `LegacyKeyValueFormat: "ENV key=value" should be used instead of legacy "ENV key value" format (line 8)`) Addendum: it's yet unclear why we need the `ulimit -n 1048576` workaround to fix an apt/apt-mark performance issue. It feels similar to what has been observed for fakeroot at https://bugs.debian.org/920913. Credits to Chris Hofstaedtler for review and working on grml-live's minifai, to support all our needs. Change-Id: I85111806a550f1aeffcb5263af2455ec8b90cc32	1 year ago

Author

SHA1

Message

Date

Sipwise Jenkins Builder

b685559634

MT#64349 Update bootstrap key with fixed SHA-1 situation

Now it contains:

pub   rsa4096 2015-03-05 [SC] [expires: 2029-10-12]
      68A702B1FD8E422AAAA1ADA3773236EFF411A836
uid           [ unknown] Sipwise GmbH (Sipwise Repository Key) <support@sipwise.com>
sub   rsa4096 2015-03-05 [E] [expires: 2029-10-12]

pub   rsa4096 2011-06-06 [SC]
      F7B8A739CE638D719A078C9859104633EE5E097D
uid           [ unknown] Sipwise autobuilder (Used to sign packages for autobuild) <development@sipwise.com>
sub   rsa4096 2011-06-06 [E]

pub   rsa4096 2023-08-04 [SCEA] [expires: 2033-08-01]
      F0A595D85C375447BB09F25E34A72CE4979CA98A
uid           [ unknown] Sipwise autobuilder <development@sipwise.com>

pub   rsa4096 2024-08-14 [SCEA] [expires: 2034-08-12]
      A164D3A12AC0F6AB8F737EF66D1B7D01D2AD9C24
uid           [ unknown] Sipwise autobuilder <development@sipwise.com>

pub   rsa4096 2025-06-09 [SCEA] [expires: 2035-06-07]
      6ACB2E82869CD45C93DA14DF617ECBC182DAAB8B
uid           [ unknown] Sipwise autobuilder <development@sipwise.com>

Change-Id: Icfe8b7b94126725026577b6379966b97d61f9a98

Michael Prokop

53cb7772da

MT#60283 Update grml-live to version 0.54.1

Lots of changes took place in between v0.53.2 and v0.54.1. To ensure to
follow upstream changes, let's make sure our configuration avoids
relying on features that are going to be dropped in upcoming versions.

Relevant changes:

* FAI_DEBOOTSTRAP=... became BOOTSTRAP_MIRROR=... (without the Debian
  release name, but just requiring the mirror URL)

* the templates command line option `-t ...` is considered deprecated,
  now that boot templates are also class-based configuration files
  (via ${GRML_FAI_CONFIG}/config/media-files/$CLASS)

  Let's keep our templates as-is, but provide
  grml_build/config/media-files/SIPWISE as symlink to our templates
  directory

* GRMLBASE and architecture-specific classes are now enabled by
  default and no longer should be included in the grml-live invocation,
  so drop GRMLBASE + AMD64 class names in wrapper.sh

* The RELEASE class (which cleans up /root and /home/grml) is also
  automatically enabled, but since we e.g. ship files like /root/puppet.gpg
  we need to disable this new behavior by enabling the new "-R" option

Change-Id: I66dc8c685decac25370234844e33d4be60dea08a

Michael Prokop

8647b3d7b5

MT#60283 Update to grml-live version v0.53.2 + Debian/trixie

grml-live had >410 commits since v0.47.7 (which we used so far),
including getting rid of FAI (through our own so called minifai
implementation), supporting mmdebstrap for bootstrapping (and using it
by default nowadays), and usage inside non-privileged containers.

Misc changes:

* No longer run any docker containers with --privileged, now that this
  is handled all internally from within grml-live's build driver

* Upgrade everything to Debian/trixie (given that we also switched our
  trunk/master branch towards trixie also)

* Provide wrapper.sh script to avoid maintaining it also inside
  jenkins-configs' jobs/internal/grml/build_grml_image.sh (which meant
  going through yet another layer and every single change to it required
  a full jenkins-config change). Update README.txt accordingly to
  provide usage examples.

* Set up keyring for custom bootstrapping using our own mirror, using
  grml_build/config/bootstrap-keyring/SIPWISE and
  deploying /usr/share/keyrings/sipwise-archive-keyring.gpg via
  updatebase hook script

* Ship .gitignore files to ignore directories that are relevant for
  the build process, though we also don't need to explicitly create them
  on every single build any longer.

* Update configuration layout for grml-live change as of upstream
  version v0.51.0 (see grml-live.git commit f1dc42a), moving from
  /etc/grml/fai/config into /usr/share/grml-live/config.

* Update configuration layout for grml-live change as of upstream
  version 0.53.0 (see grml-live.git commit 3a4bd41), changing schema
  files/<path>/<CLASS> into files/<CLASS>/<path>,
  class/<CLASS>.var into env/<CLASS> and
  hooks/<hookname>.<CLASS> into hooks/<CLASS>/<hookname>.

* Add memtest86+ + ipxe to SIPWISE class, so they are available for boot
  menu integration (grml-live uses addons from grml_chroot and no longer
  from host system).

grml_build/Dockerfile related changes:

* Adjust ENV usage (fixes `LegacyKeyValueFormat: "ENV key=value" should
  be used instead of legacy "ENV key value" format (line 9)`)

* Add snippet for usage with debian:trixie-slim as base docker image
  (useful for debugging e.g. without access to Sipwise systems)

* Install ca-certificates (needed for access to https://github.com/ with
  debian:trixie-slim)

* Switch from grml-live v0.47.7 to v0.53.2

* Drop deprecated dependencies that are no longer relevant with recent
  grml-live versions (fai-client + fai-server get replaced by our own
  minifai implementation, mksh is no longer relevant for grml-live, and
  isolinux, ipxe, memtest86+ + syslinux are used from the grml_chroot
  instead of from the host system, also see above)

* Instead install mmdebstrap (which is much faster for bootstrapping
  than debootstrap), now being supported and the default, thanks to our
  minifai implementation

* Drop /root/.bash_history, as we switched towards our custom wrapper.sh
  script

t/Dockerfile related changes:

* Mark /code as safe directory for git, to not fail with
  "fatal: detected dubious ownership in repository at '/code'"

* Adjust ENV usage (fixes `LegacyKeyValueFormat: "ENV key=value" should
  be used instead of legacy "ENV key value" format (line 8)`)

Addendum: it's yet unclear why we need the `ulimit -n 1048576`
workaround to fix an apt/apt-mark performance issue. It feels similar to
what has been observed for fakeroot at https://bugs.debian.org/920913.

Credits to Chris Hofstaedtler for review and working on grml-live's
minifai, to support all our needs.

Change-Id: I85111806a550f1aeffcb5263af2455ec8b90cc32

3 Commits (master)