besu icon indicating copy to clipboard operation
besu copied to clipboard

Published 20 hours ago ā€¢ verified publisher icon hyperledger

Hotfix CI/CD

Open jflo opened this issue 11 months ago ā€¢ 1 comments

As Besu becomes more modular, and refactoring becomes more aggressive, we may need finer grained resolution to our releases.

While still abiding by all normal release/review policies, we should also add the capability to create a release from an ephemeral hotfix branch, and create all essential artifacts from it. This must include artifact jars and docker images, but does not require documentation or homebrew.

jflo avatar Dec 10 '24 18:12 jflo

This issue is stale because it has been open for 6 months with no activity.

github-actions[bot] avatar Jun 09 '25 02:06 github-actions[bot]

Hi @jflo šŸ‘‹,

I'm Adharsh, a DevOps and Cloud Engineer exploring open source. I'd like to contribute to this issue by improving the GitHub Actions pipeline to support hotfix releases from ephemeral branches.

Could you clarify:

  • Naming convention you prefer for hotfix branches (e.g., hotfix/*)?
  • Whether artifact versioning should auto-increment or be manually set?

Looking forward to collaborating!

Thanks,

adharsh277 avatar Aug 02 '25 12:08 adharsh277

hi @adharsh277 I closed your PR - didn't realised you'd also commented here https://github.com/hyperledger/besu/pull/9029

I think we need to discuss within the team exactly what are our acceptance criteria, before jumping into solutions.

@jflo happy to discuss

macfarla avatar Aug 04 '25 01:08 macfarla

A hotfix/* converntion would be fine. Artifact versioning should be manually set.

Will solicit more opinions from other maintainers, thank you for your interest!

jflo avatar Aug 04 '25 12:08 jflo

Hi @jflo, @macfarla and team,

Thank you for clarifying the direction on hotfix branches and artifact versioning. I completely understand the importance of aligning with internal expectations before moving forward. Once the team has finalized the acceptance criteria, I would be happy to contribute again based on the updated guidelines. Iā€™m here to learn, iterate, and support the CI/CD pipeline improvements in any way that adds value to the project. Please feel free to tag me when the discussion progresses ā€” looking forward to collaborating further.

adharsh277 avatar Aug 07 '25 05:08 adharsh277

The release process depends on the branch starting with release- but can be release-XYZ-hotfix - I don't think we need another workflow added.

macfarla avatar Aug 07 '25 22:08 macfarla