Skip to content

create another workflow to handle beta release - #337

Merged
xsalefter merged 5 commits into
java2xfrom
kb-beta-release
Aug 10, 2026
Merged

create another workflow to handle beta release#337
xsalefter merged 5 commits into
java2xfrom
kb-beta-release

Conversation

@xsalefter

Copy link
Copy Markdown
Contributor

Based on slack conversation that:

  1. It is OK to have public beta (0.25.x) release
  2. But do not touch the latest tag.

I decided that we need to have this PR. But note that, this PR depends on this PR by Vijay. Otherwise, docker build will fails.

  1. Changes in ansible/java.yml : Needed regardless, because killbill:0.25.x need JDK 21. I stated that.

  2. Changes in docker/templates/base/latest/Dockerfile : Actually optional. But because PR will targeted java2x branch and all of this work supposed to support killbill:0.25.x++ anyway, changes this actually preferred.

  3. Changes in .gitignore : The docker/templates/killbill/beta/Dockerfile actually generated for testing purpose only, just like these files are ignored as well:

    • docker/templates/killbill/latest/Dockerfile
    • docker/templates/killbill/tagged/Dockerfile
  4. New file docker/templates/killbill/beta/Dockerfile.template : This is the actual image file candidate. Implements docker buildx's multi-stage build: builder-base -> builder-tomcat -> base -> shell -> Dockerfile .

  5. New file .github/workflows/kb_beta_release.yml : This is the "frontend" that will take input from user and passed to the beta Dockerfile (see point 4) that already "concatenated".

@xsalefter
xsalefter merged commit 497e31b into java2x Aug 10, 2026
8 of 10 checks passed
@xsalefter
xsalefter deleted the kb-beta-release branch August 10, 2026 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants