Skip to content

Release Procedure

Jump to bottom Edit New page
Jeff Mesnil edited this page Jul 3, 2023 · 1 revision

Procedure to release new images

WildFly Docker images are available from https://quay.io/repository/wildfly/wildfly.

They are built using a GitHub action.

There are 2 steps to release images for new versions of WildFly:

  • Update the Dockerfile to pull the new versions of WildFly

  • Create a tag from this GitHub repository to trigger the GitHub action

Prepare the Dockerfile for new versions of WildFly.

  1. Open a PR against this repository with updated data in the Dockerfile for the two environment variables: 

    ENV WILDFLY_VERSION 28.0.1.Final
ENV WILDFLY_SHA1 8702fb7ba8d1249bf058e2223f662e5176b39d0d

    • The WILDFLY_VERSION corresponds to the WildFly version and will be used to download the wildfly-$WILDFLY_VERSION.tar.gz archive from the GitHub Releases.

      • This MUST be actual releases of WildFly (pre-releases do not provide stable URLS to download the archive)

    • The WILDFLY_SHA1 corresponds to the checksum of the tar.gz archive and can be read from the wildfly-$WILDFLY_VERSION.tar.gz.sha1 from the GitHub Releases.

    • Example of a PR to update the Dockerfile

  2. The PR can be open when WildFly is "pre-released" (as the checksum is known at that time) but do not merge it before WildFly is actually released.

Publish the container images for new versions of WildFly

Once the PR to update the WildFly version and checksum is merged, you can trigger the creation of new container images by creating a tag from GitHub UI

  • Draft a new Release from GitHub UI

    • The tag should be the updated version of WildFly

    • The target must point to the commit of the merged PR

    • Auto generate the release notes

This will trigger the GitHub action, build and push the container images to https://quay.io/repository/wildfly/wildfly

Add a custom footer
Add a custom sidebar
Clone this wiki locally