valkey icon indicating copy to clipboard operation
valkey copied to clipboard

Valkey Release Workflow

Open roshkhatri opened this issue 1 year ago • 5 comments

Valkey Releases

The release process at a high level will look like as follows:

  1. Version Tags (7.2.4) would have be created.
  2. Once the Tag is pushed to a release branch and the release should be published.
  3. When a release is pushed, the workflow to build binaries for arm and x86 will execute to create the tarball and checksums.
  4. These files will then be pushed to the S3 bucket in the directories such as /major_version/minor_version/patch_version/
  5. These files can be linked from the download page of the the website.
  6. For download latest/stable version from source, it can be linked to the valakey-io/valkey/archive/refs/tags/*.*.*.tar.gz

Please add any suggestions or questions if you may have.

roshkhatri avatar Apr 05 '24 17:04 roshkhatri

When a release is pushed, the workflow to build binaries for arm and x86 will execute to create the tarball and checksums.

Is this workflow automated, or will we manually initiate it?

These files can be linked from the download page of the the website.

Are we vending these from S3 or from the website, I presume we want to vend them through the website so we can better gate access to them.

madolson avatar Apr 05 '24 20:04 madolson

Is this workflow automated, or will we manually initiate it?

The release workflow we can keep manual for now and automate in the next iterations, initiating the workflow to build the binaries will be Automated.

Are we vending these from S3 or from the website, I presume we want to vend them through the website so we can better gate access to them.

Yes, we want to vend them through the website. I though the website is also hosted on S3. But yes, correct, from the website.

roshkhatri avatar Apr 05 '24 20:04 roshkhatri

Also, have you seen the tools that exist here: https://github.com/valkey-io/valkey/tree/unstable/utils/releasetools ?

madolson avatar Apr 06 '24 04:04 madolson

Yeah, I did not realize they were there, but these are only valid for releasing the whole source-code tarbal files and not the actual builds.

The workflows I am currently working would look like these: This was triggered when I have pushed a tag to the my repo simulating the release tag publish. Screenshot 2024-04-06 at 1 09 57 AM

roshkhatri avatar Apr 06 '24 08:04 roshkhatri

Will be there Docker Images for every release?

Thanks in advance

K2ouMais avatar Apr 12 '24 05:04 K2ouMais

Will be there Docker Images for every release?

That is the plan.

@roshkhatri Can we close this?

madolson avatar Sep 04 '24 15:09 madolson

Yes we will have a docker image for every release here: https://hub.docker.com/r/valkey/valkey/tags

roshkhatri avatar Sep 04 '24 17:09 roshkhatri