[tarantool-patches] [PATCH] travis-ci: deploy packages from tagged revisions

[tarantool-patches] [PATCH] travis-ci: deploy packages from tagged revisions

[Alexander Turenko]

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

[tarantool-patches] Re: [PATCH] travis-ci: deploy packages from tagged revisions

[Kirill Yukhin]

Hello,

On 14 июн 19:44, Alexander Turenko wrote:
> 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.

I've checked the patch into master.

--
Regards, Kirill Yukhin

[tarantool-patches] Re: [PATCH] travis-ci: deploy packages from tagged revisions

[Alexander Turenko]

On Fri, Jul 26, 2019 at 08:23:52PM +0300, Kirill Yukhin wrote:
> Hello,
> 
> On 14 июн 19:44, Alexander Turenko wrote:
> > 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.
> 
> I've checked the patch into master.

It is needed in 2.1 and 1.10 too. As we agreed I cherry-picked the
commit to these branches, changed a packagecloud repository name
appropriately and pushed.