You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/07/26 14:05:20 UTC
[jira] [Commented] (FLINK-4261) Setup atomic deployment of
snapshots
[ https://issues.apache.org/jira/browse/FLINK-4261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15393836#comment-15393836 ]
ASF GitHub Bot commented on FLINK-4261:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2296
[FLINK-4261][tools] retry in case of failed snapshot deployment
Unfortunately, we can't deploy snapshots atomically using the Nexus
repository. The staged process which leads to an atomic deployment is
only designed to work for releases. Best we can do is to retry
deploying artifacts in case of failures.
- introduce retry in case of failure of snapshot deployment
- simplify deployment script
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-4261
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2296.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2296
----
commit ee91c12fc0d1d0ba9c7ad29c205dc41ec9f94264
Author: Maximilian Michels <mx...@apache.org>
Date: 2016-07-21T15:06:06Z
[FLINK-4261][tools] retry in case of failed snapshot deployment
Unfortunately, we can't deploy snapshots atomically using the Nexus
repository. The staged process which leads to an atomic deployment is
only designed to work for releases. Best we can do is to retry
deploying artifacts in case of failures.
- introduce retry in case of failure of snapshot deployment
- simplify deployment script
----
> 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
(v6.3.4#6332)