Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A archlinux-docker
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
    • Locked files
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Arch LinuxArch Linux
  • archlinux-docker
  • Merge requests
  • !39

Add base-devel tag

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Sven-Hendrik Haase requested to merge add-base-devel-tags into master Aug 29, 2020
  • Overview 48
  • Commits 93
  • Pipelines 153
  • Changes 13

This does a few things (and sorry, I know this is quite a lot and I usually try to keep it small but the refactoring kinda needs everything to go in at once):

  • Change from image format from archlinux/base to archlinux/archlinux:base
  • Add base-devel tag
  • Try to supersede !36 (closed)
  • Try to address concerns in #35 (closed)
  • Set up some automatic publishing preparation
  • Add container security scanning because why not

Fixes #35 (closed).

Once this is merged, it needs some manual outside actions:

  • Create new repository for the Docker Hub organisation: archlinux/archlinux
  • Create a Docker Hub technical account and add it to the organisation
  • Delete the old archlinux/base on Dockerhub (as we use archlinux/archlinux with tags now)
  • Clean up references to add-base-devel-tags
  • Delete old testing garbage (tags, files, releases)

Also for this change:

  • Make sure that the security concept is properly observed: Do not let an image or artifact built on non-secure runners pass over to secure runners! Use the non-secure runners for testing only and use the secure runners for final artifact creation and such.
Edited Oct 25, 2020 by Sven-Hendrik Haase
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: add-base-devel-tags