flink-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] (FLINK-4261) Setup atomic deployment of snapshots
Date Tue, 26 Jul 2016 14:51:20 GMT

    [ https://issues.apache.org/jira/browse/FLINK-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393894#comment-15393894

Maximilian Michels commented on FLINK-4261:

Retry via cd232e683f7aa6d7660ca2d545ba1534435e1ab1

> Setup atomic deployment of snapshots
> ------------------------------------
>                 Key: FLINK-4261
>                 URL: https://issues.apache.org/jira/browse/FLINK-4261
>             Project: Flink
>          Issue Type: Bug
>          Components: Build System, release
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>             Fix For: 1.1.0
> Users have reported that our nightly snapshots become inconsistent from time to time.
This happens when the upload to the snapshot repository fails during the deployment process.
Maven doesn't support atomic deployment but deploys artifacts one after another, directly
after installing them in the local repository. If the build fails at any time, no changes
are rolled back. 
> This problem has been solved for Nexus repositories. For releases, we already take advantage
of atomic deployments using staging repositories. Nexus repositories support this even without
using a special Maven plugin. 
> For releases, we have to use the Web UI to close and release staging repositories. For
snapshots this should be automated. Most importantly, the changes shouldn't alter anything
for our release process.
> I suggest to use the {{nexus-staging-maven-plugin}} which essentially replaces the standard
maven deploy plugin. It can be setup to auto-close and auto-release snapshots staging repositories.
For releases, it will be setup to never auto-close nor auto-release which keeps our existing
release process.

This message was sent by Atlassian JIRA

View raw message