Build: https://travis-ci.com/popatop15/TimeMine/builds/141644846 I have tried tagging in before_deploy like stated in the docs here: https://docs.travis-ci.com/user/deployment/releases/#setting-the-tag-at-deployment-time However, that has the same results. Here’s the script that it executes: http…

TRAVIS_TAG envvar needs to be visible to the shell running the build logic – i.e. the main shell process. You are running ./script.sh as a child process so its environment changes don’t propagate to the main shell. source ./script.sh should fix the problem.

Tagging in after_success script doesn't trigger deployment

Deployment

native-api Split this topic December 18, 2019, 7:41pm 7

A post was split to a new topic: Another build is triggered if I create a tag dynamically

Topic		Replies	Views
Another build is triggered if I generate TRAVIS_TAG dynamically Deployment github-releases	1	971	December 18, 2019
Tag not triggering builds after years of working Travis CI Discussions & Feedback travis-build , bug	5	1559	November 16, 2023
Pushing tag does not trigger deployment to github releases Deployment	4	4181	April 22, 2019
Tags creates request but doesn't trigger a deploy job Travis CI Discussions & Feedback deployment	4	1649	May 22, 2019
Deployment best practices? Deployment github	2	1561	December 29, 2019

Tagging in after_success script doesn't trigger deployment

Related topics