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: https://github.com/popatop15/TimeMine/blob/master/script.sh And my .travis.yml: https://github.com/popatop15/TimeMine/blob/master/.travis.yml I am 100% new to TravisCI, so forgive me if something seems odd or out of best practice. I’m just trying to set up a system which works :slight_smile:

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.

Oh ok, I understand the problem you described, but where would I put that source option? Can’t seem to find it in the docs.

source (aka .) is a Bash builtin command (https://linux.die.net/man/1/bash).

Thank you, wasn’t familiar with that command. Tested and this was my solution. Thanks!

A quick note: source executes the contents of the file automatically so ./ or setting +x was not necessary.

Tagging in after_success script doesn't trigger deployment

Deployment

Topic		Replies	Views
Another build is triggered if I generate TRAVIS_TAG dynamically Deployment github-releases	1	1024	December 18, 2019
Job triggered by tag but TRAVIS_BRANCH is different to TRAVIS_TAG Deployment bug	1	1474	November 7, 2023
Tags not always built Travis CI Discussions & Feedback trigger-custom-build	7	1757	September 23, 2022
Travis CI build does not execute tags: true v2 bug	2	865	November 25, 2021
Pushing tag does not trigger deployment to github releases Deployment	3	4311	April 22, 2019

Tagging in after_success script doesn't trigger deployment

Related topics