tarantool / tarantool / 24364

83%

master: 88%

push

travis-ci

<a href="https://github.com/tarantool/tarantool/commit/<a class=hub.com/tarantool/tarantool/commit/782d2a9fa1f675cbcbf2fe60ebcf0a79182dbbcf">782d2a9fa<a href="https://github.com/tarantool/tarantool/commit/782d2a9fa1f675cbcbf2fe60ebcf0a79182dbbcf">&quot;&gt;gitlab-ci: fix deployment of tagged commits

Found that tagged commits were not run the deployment gitlab-ci jobs.
To fix it added &amp;#39;tags&amp;#39; label for deployment and perfomance jobs. Also
found that after the commit tagged it has tag label in format &amp;#39;x^0&amp;#39;
and all previous commits till the previous tag became to have tags in
format &amp;#39;x~&amp;lt;commits before&amp;gt;&amp;#39; like &amp;#39;x~1&amp;#39; or &amp;#39;x~2&amp;#39; and etc. So the check

  if git name-rev --name-only --tags --no-undefined HEAD ; then

became always pass and previous commits on rerun could began to deploy.
To fix it was used gitlab-ci environment variable &amp;#39;CI_COMMIT_TAG&amp;#39;, it
shows in real if the current commit has tag and has to be deployed.

Part of #3745

(cherry picked from commit </a><a class="double-link" href="https://github.com/tarantool/tarantool/commit/<a class="double-link" href="https://github.com/tarantool/tarantool/commit/5aa1a1dfe58f39d9024b6e66000a71458a26f3ff">5aa1a1dfe</a>">5aa1a1dfe</a><a href="https://github.com/tarantool/tarantool/commit/782d2a9fa1f675cbcbf2fe60ebcf0a79182dbbcf">)

Conflicts:
	.gitlab-ci.yml

42488 of 51320 relevant lines covered (82.79%)

969723.89 hits per line