允许重新部署“最新"邮件Nexus OSS中的docker标签 [英] Allow redeploy for "latest" docker tag in Nexus OSS

查看:175
本文介绍了允许重新部署“最新"邮件Nexus OSS中的docker标签的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用nexus托管maven和docker工件.对于docker生产工件,我想启用禁用重新部署"功能,以确保一旦可能在生产环境中,映像就永远不会在nexus服务器上更改.

I'm using nexus to host both maven and docker artifacts. For the docker production artifacts I'd like to turn on "disable redeploy" to ensure the image can never change on the nexus server once it is potentially in production.

但是,启用禁用重新部署"似乎无法重新发布最新"标签以指向最新版本.

However, enabling "disable redeploy" appears to make it impossible to re-publish the "latest" tag to point to the latest version.

在尝试推送时,我在客户端上得到了模糊的错误,例如blob upload invalid: blob upload invalid.

When trying to push I get obscure errors on the client such as blob upload invalid: blob upload invalid.

是否可以禁用重新部署到具体版本的标签,同时允许使用最新"之类的标签

Is it possible to disable redeploy to concrete version tags, while allowing on tags like "latest"

推荐答案

在声纳类型3.21.1中已添加了此功能.选择禁用重新部署策略"后,我们得到一个新选项:允许重新部署最新"标签,但对所有其他标签都遵循部署策略.

In sonartype version 3.21.1 this feature has been added. When the Disable redeploy policy is selected , we get new option: Allow redeploying the 'latest' tag but defer to the Deployment Policy for all other tags.

链接: https://issues.sonatype.org/browse/NEXUS-18186

这篇关于允许重新部署“最新"邮件Nexus OSS中的docker标签的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆