You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Wilfred Spiegelenburg (Jira)" <ji...@apache.org> on 2022/06/20 00:03:00 UTC
[jira] [Commented] (YUNIKORN-1240) Document changes required for RM multi-arch release builds
[ https://issues.apache.org/jira/browse/YUNIKORN-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556141#comment-17556141 ]
Wilfred Spiegelenburg commented on YUNIKORN-1240:
-------------------------------------------------
To clarify: we *must* not post any releases tagged {{{}latest{}}}. Two things:
* A release *must* be voted on and the content is set. That would not be the case for a release which is tagged with latest. It is even part of the official Apache release policy:
[https://www.apache.org/legal/release-policy.html#compiled-packages]
* The latest tag is ambiguous specially when we have multiple branches in development. Does it change when we release 1.0.1 after we release 1.1 or not? It was released latest but in semver it is not.
> Document changes required for RM multi-arch release builds
> ----------------------------------------------------------
>
> Key: YUNIKORN-1240
> URL: https://issues.apache.org/jira/browse/YUNIKORN-1240
> Project: Apache YuniKorn
> Issue Type: Task
> Components: release
> Reporter: Craig Condit
> Assignee: Wilfred Spiegelenburg
> Priority: Major
>
> Now that YUNIKORN-1215 is complete, we need to document the new process for producing Docker images.
> A couple things needed in addition to the documentation of the scripts themselves:
> 1. When building on linux, builds will fail if QEMU is not configured or installed properly. At least on Debian, this requires the `qemu-user-static` package.
> 2. After the release, we traditionally update the `\{image}-latest` tags to point to the new build. Now that these are multi-arch builds, this is a little tricky. We need to copy the manifest, which is not as simple as a re-tag and push.
> We could use this tool: [https://github.com/regclient/regclient].
> I verified that this works on a personal account (changing username of course):
> {code:java}
> regctl registry login
> regctl image copy apache/yunikorn:scheduler-1.1.0-test apache/yunikorn:scheduler-latest
> regctl image copy apache/yunikorn:scheduler-plugin-1.1.0-test apache/yunikorn:scheduler-plugin-latest
> regctl image copy apache/yunikorn:admission-1.1.0-test apache/yunikorn:admission-latest
> regctl image copy apache/yunikorn:web-1.1.0-test apache/yunikorn:web-latest{code}
> Doing something similar for all four images would allow us to maintain the "latest" images as before.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org