www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maximilian Michels (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-12320) Atomic deployment of snapshots
Date Mon, 25 Jul 2016 09:23:20 GMT

    [ https://issues.apache.org/jira/browse/INFRA-12320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15391590#comment-15391590
] 

Maximilian Michels commented on INFRA-12320:
--------------------------------------------

Thanks, that was my assumption (as written in the description). Just wanted to check if I
needed anything more.

Perhaps we could add some documentation?

> Atomic deployment of snapshots
> ------------------------------
>
>                 Key: INFRA-12320
>                 URL: https://issues.apache.org/jira/browse/INFRA-12320
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins, Nexus
>            Reporter: Maximilian Michels
>            Priority: Critical
>
> Flink's nightly snapshot builds tend to fail sometimes (unstable repository server) and
we want to be able to rollback the deployment then. We use Jenkins to deploy nightly snapshots:
https://builds.apache.org/job/flink-snapshot-deployment/
> Anyone familiar with how we would perform atomic Maven snapshot deployments via Nexus
staging repositories? It should work similarly to the staged process of deploying release
artifacts. However, we don't want to use the Web UI and rather automate it for nightly deployment
of snapshots.
> Does that work out of the box via the Nexus-staging-maven-plugin? Like explained here:
https://books.sonatype.com/nexus-book/reference/staging-deployment.html#fig-staging-example-pom
> I'm assuming we need some configuration for the Nexus repository from Infra.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message