Tarantool development patches archive
 help / color / mirror / Atom feed
From: Alexander Turenko <alexander.turenko@tarantool.org>
To: Kirill Yukhin <kyukhin@tarantool.org>
Cc: Alexander Turenko <alexander.turenko@tarantool.org>,
	tarantool-patches@freelists.org,
	"Alexander V . Tikhonov" <avtikhon@tarantool.org>
Subject: [tarantool-patches] [PATCH] travis-ci: deploy packages from tagged revisions
Date: Fri, 14 Jun 2019 19:44:30 +0300	[thread overview]
Message-ID: <af29af799078bfae09980454397da1c6c06d3d9f.1560528583.git.alexander.turenko@tarantool.org> (raw)

The problem was that a tagged revision is not deployed, so after a
release we did an empty commit to trigger deployment. Now it is worked
around by adding extra deployment rules that deploys tagged revisions.
The workaround was suggested by Hiro Asari in [1].

[1]: https://github.com/travis-ci/travis-ci/issues/7780#issuecomment-302389370

Fixes #3745.
---

https://github.com/tarantool/tarantool/issues/3745
https://github.com/tarantool/tarantool/tree/Totktonada/gh-3745-deploy-tagged-revisions

 .travis.yml | 26 ++++++++++++++++++++++++--
 1 file changed, 24 insertions(+), 2 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index e94d02ef5..061da9af4 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -104,7 +104,7 @@ before_deploy:
   - ls -l build/
 
 deploy:
-  # Deploy packages to PackageCloud
+  # Deploy packages to PackageCloud from master branch (w/o tagged revisions)
   - provider: packagecloud
     username: "tarantool"
     repository: "2_2"
@@ -116,7 +116,7 @@ deploy:
       repo: tarantool/tarantool
       branch: "master"
       condition: -n "${OS}" && -n "${DIST}" && -n "${PACKAGECLOUD_TOKEN}"
-  # Deploy source tarballs to S3
+  # Deploy source tarballs to S3 from master branch (w/o tagged revisions)
   - provider: script
     script: make -f .travis.mk source_deploy
     skip_cleanup: true
@@ -124,6 +124,28 @@ deploy:
       repo: tarantool/tarantool
       branch: "master"
       condition: "x${TARGET} = xsource"
+  # Deploy packages to PackageCloud from tagged revisions
+  # https://github.com/travis-ci/travis-ci/issues/7780#issuecomment-302389370
+  - provider: packagecloud
+    username: "tarantool"
+    repository: "2_2"
+    token: "${PACKAGECLOUD_TOKEN}"
+    dist: "${OS}/${DIST}"
+    package_glob: build/*.{rpm,deb,dsc}
+    skip_cleanup: true
+    on:
+      repo: tarantool/tarantool
+      tags: true
+      condition: -n "${OS}" && -n "${DIST}" && -n "${PACKAGECLOUD_TOKEN}"
+  # Deploy source tarballs to S3 from tagged revisions
+  # https://github.com/travis-ci/travis-ci/issues/7780#issuecomment-302389370
+  - provider: script
+    script: make -f .travis.mk source_deploy
+    skip_cleanup: true
+    on:
+      repo: tarantool/tarantool
+      tags: true
+      condition: "x${TARGET} = xsource"
 
 notifications:
   email:
-- 
2.21.0

             reply	other threads:[~2019-06-14 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14 16:44 Alexander Turenko [this message]
2019-07-26 17:23 ` [tarantool-patches] " Kirill Yukhin
2019-07-26 17:47   ` Alexander Turenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=af29af799078bfae09980454397da1c6c06d3d9f.1560528583.git.alexander.turenko@tarantool.org \
    --to=alexander.turenko@tarantool.org \
    --cc=avtikhon@tarantool.org \
    --cc=kyukhin@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='Re: [tarantool-patches] [PATCH] travis-ci: deploy packages from tagged revisions' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox