[GH-ISSUE #346] Incremental release CD pipeline #122

New issue

Closed

opened 2026-02-26 04:34:06 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 04:34:06 +03:00

Owner

Originally created by @mageddo on GitHub (Mar 8, 2023).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/346

What is expected

Actual pipeline do some steps

Build
Test
Generate Jar
Generate Native Image Jar source
Generate Linux AMD64 Binary
Generate Linux ARM64 Binary (Which takes around 50 minutes to complete)
Compress the artifacts in tar.gz format
Create a Github release with a GIT tag
Upload the artifacts
Upload docker images

All the process takes around 50 min, most time is spent on generating arm image as it needs qemu emulator.

I'm proposing to work on a more incremental behavior so we can partially release and benefit soonly of the results, the drawback it's it will be possible to have a release with Linux binaries and not with arm ones cause this specific step failed, but I think that's something which is rare to happen

=> Step 1 - Basic release

Build
Test
Generate Jar
Generate Native Image Jar source
Generate Linux AMD64 Binary
Compress the artifacts in tar.gz format
Create a Github release with a GIT tag
Upload Linux amd64 and jar artifacts
Docker image push

=> Step 2 - Linux arm release

Generate Linux ARM64 Binary (Which takes around 50 minutes to complete)
Compress the artifacts in tar.gz format
Upload the artifacts to latest generated release
Docker image push

=> Step 3 - A future Windows release and so on....

https://github.com/mageddo/dns-proxy-server/issues/306

Originally created by @mageddo on GitHub (Mar 8, 2023). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/346 ### What is expected Actual pipeline do some steps * Build * Test * Generate Jar * Generate Native Image Jar source * Generate Linux AMD64 Binary * Generate Linux ARM64 Binary (Which takes around 50 minutes to complete) * Compress the artifacts in tar.gz format * Create a Github release with a GIT tag * Upload the artifacts * Upload docker images All the process takes around 50 min, most time is spent on generating arm image as it needs qemu emulator. I'm proposing to work on a more incremental behavior so we can partially release and benefit soonly of the results, the drawback it's it will be possible to have a release with Linux binaries and not with arm ones cause this specific step failed, but I think that's something which is rare to happen => Step 1 - Basic release * Build * Test * Generate Jar * Generate Native Image Jar source * Generate Linux AMD64 Binary * Compress the artifacts in tar.gz format * Create a Github release with a GIT tag * Upload Linux amd64 and jar artifacts * Docker image push => Step 2 - Linux arm release * Generate Linux ARM64 Binary (Which takes around 50 minutes to complete) * Compress the artifacts in tar.gz format * Upload the artifacts to latest generated release * Docker image push => Step 3 - A future Windows release and so on.... * https://github.com/mageddo/dns-proxy-server/issues/306