Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 411EB200B52 for ; Mon, 25 Jul 2016 16:11:27 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 3F8B9160A7D; Mon, 25 Jul 2016 14:11:27 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AE136160A67 for ; Mon, 25 Jul 2016 16:11:26 +0200 (CEST) Received: (qmail 43468 invoked by uid 500); 25 Jul 2016 14:11:20 -0000 Mailing-List: contact dev-help@flink.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flink.apache.org Delivered-To: mailing list dev@flink.apache.org Received: (qmail 43435 invoked by uid 99); 25 Jul 2016 14:11:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 25 Jul 2016 14:11:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A35172C0D5E for ; Mon, 25 Jul 2016 14:11:20 +0000 (UTC) Date: Mon, 25 Jul 2016 14:11:20 +0000 (UTC) From: "Maximilian Michels (JIRA)" To: dev@flink.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (FLINK-4261) Setup atomic deployment of snapshots MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 25 Jul 2016 14:11:27 -0000 Maximilian Michels created FLINK-4261: ----------------------------------------- Summary: 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)