New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[1pt] Tagged releases are not uploaded (extra commit is needed) #3745
Comments
We have the same problems with modules (say, avro-schema). |
Totktonada
added a commit
that referenced
this issue
Jun 14, 2019
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]: travis-ci/travis-ci#7780 (comment) Fixes #3745.
Totktonada
added a commit
to tarantool/memcached
that referenced
this issue
Jul 24, 2019
Totktonada
added a commit
to tarantool/small
that referenced
this issue
Jul 25, 2019
Totktonada
added a commit
to tarantool/small
that referenced
this issue
Jul 25, 2019
Totktonada
added a commit
that referenced
this issue
Jul 26, 2019
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]: travis-ci/travis-ci#7780 (comment) Fixes #3745. (cherry picked from commit 2fe7036)
Totktonada
added a commit
that referenced
this issue
Jul 26, 2019
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]: travis-ci/travis-ci#7780 (comment) Fixes #3745. (cherry picked from commit 2fe7036)
Totktonada
added a commit
to tarantool/memcached
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
to tarantool/memcached
that referenced
this issue
Jul 29, 2019
Totktonada
added a commit
to tarantool/pg
that referenced
this issue
Jul 30, 2019
Totktonada
added a commit
to tarantool/pg
that referenced
this issue
Jul 30, 2019
Totktonada
added a commit
to stefansaraev/mqtt
that referenced
this issue
Jul 31, 2019
Totktonada
added a commit
to tarantool/mqtt
that referenced
this issue
Jul 31, 2019
Totktonada
added a commit
to stefansaraev/expirationd
that referenced
this issue
Jul 31, 2019
Totktonada
added a commit
to tarantool/expirationd
that referenced
this issue
Jul 31, 2019
avtikhon
added a commit
to tarantool/queue
that referenced
this issue
Aug 2, 2019
Removed release repos: 1_7/1_9. Added the build distros: Fedora 30, Ubuntu 19.04, Debian 10. Removed the build distros: Fedora 26,27. Deploy packages from tagged revisions, see: tarantool/tarantool#3745 Closes #94
Totktonada
added a commit
to tarantool/queue
that referenced
this issue
Aug 6, 2019
Totktonada
added a commit
to tarantool/queue
that referenced
this issue
Aug 6, 2019
avtikhon
added a commit
to tarantool/mysql
that referenced
this issue
Aug 20, 2019
Removed release repos: 1_6, 1_7. Added release repos: 1_10, 2x, 2_2, 2_3. Added the build distros: Fedora 30, Ubuntu 19.04, Debian 10. Deploy packages from tagged revisions, see: tarantool/tarantool#3745 Closes #26
Totktonada
pushed a commit
to tarantool/mysql
that referenced
this issue
Aug 20, 2019
Removed release repos: 1_6, 1_7. Added release repos: 1_10, 2x, 2_2, 2_3. Added the build distros: Fedora 30, Ubuntu 19.04, Debian 10. Deploy packages from tagged revisions, see: tarantool/tarantool#3745 Closes #26
We should also enable tarball and package jobs on tagged revisions, because, say, |
Totktonada
added a commit
to tarantool/avro-schema
that referenced
this issue
Oct 23, 2019
Totktonada
added a commit
to tarantool/avro-schema
that referenced
this issue
Oct 23, 2019
avtikhon
added a commit
that referenced
this issue
Oct 8, 2020
If the commit tagged, then push packages to 'live' repository with force push '-f -s' flags to be sure that if occasionaly the commit before current commit pushed packages with the current branch naming then the current push won't fail on it and will push the packages to the release repository after. Closes #3745
avtikhon
changed the title
Tagged releases are not uploaded (extra commit is needed)
[1pt] Tagged releases are not uploaded (extra commit is needed)
Oct 9, 2020
avtikhon
added a commit
that referenced
this issue
Oct 14, 2020
If the commit tagged, then push packages to 'live' repository with force push '-f -s' flags to be sure that if occasionaly the commit before current commit pushed packages with the current branch naming then the current push won't fail on it and will push the packages to the release repository after. Part of #3745
avtikhon
added a commit
that referenced
this issue
Oct 14, 2020
Drop a tag that points to a current commit (if any) on a job triggered by pushing to a branch (as against of pushing a tag). Otherwise we may get two jobs for the same x.y.z-0-gxxxxxxxxx build: one is run by pushing a branch and another by pushing a tag. The idea is to hide the new tag from the branch job as if a tag would be pushed strictly after all branch jobs for the same commit. Closes #3745 Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org>
More detailed description is in the mailing list. |
Totktonada
pushed a commit
that referenced
this issue
Oct 14, 2020
Drop a tag that points to a current commit (if any) on a job triggered by pushing to a branch (as against of pushing a tag). Otherwise we may get two jobs for the same x.y.z-0-gxxxxxxxxx build: one is run by pushing a branch and another by pushing a tag. The idea is to hide the new tag from the branch job as if a tag would be pushed strictly after all branch jobs for the same commit. Closes #3745 Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org> (cherry picked from commit 0f564f3)
Totktonada
pushed a commit
that referenced
this issue
Oct 14, 2020
Drop a tag that points to a current commit (if any) on a job triggered by pushing to a branch (as against of pushing a tag). Otherwise we may get two jobs for the same x.y.z-0-gxxxxxxxxx build: one is run by pushing a branch and another by pushing a tag. The idea is to hide the new tag from the branch job as if a tag would be pushed strictly after all branch jobs for the same commit. Closes #3745 Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org> (cherry picked from commit 0f564f3)
Totktonada
pushed a commit
that referenced
this issue
Oct 14, 2020
Drop a tag that points to a current commit (if any) on a job triggered by pushing to a branch (as against of pushing a tag). Otherwise we may get two jobs for the same x.y.z-0-gxxxxxxxxx build: one is run by pushing a branch and another by pushing a tag. The idea is to hide the new tag from the branch job as if a tag would be pushed strictly after all branch jobs for the same commit. Closes #3745 Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org> (cherry picked from commit 0f564f3)
For the record: it is not resolved, but is not important.
It should be fixed. |
avtikhon
added a commit
that referenced
this issue
Oct 15, 2020
Drop a tag that points to a current commit (if any) on a job triggered by pushing to a branch (as against of pushing a tag). Otherwise we may get two jobs for the same x.y.z-0-gxxxxxxxxx build: one is run by pushing a branch and another by pushing a tag. The idea is to hide the new tag from the branch job as if a tag would be pushed strictly after all branch jobs for the same commit. Closes #3745 Co-authored-by: Alexander Turenko <alexander.turenko@tarantool.org>
Totktonada
added a commit
to tarantool/gentoo-overlay
that referenced
this issue
Oct 29, 2020
* 1.10.8 -- LTS. * 2.4.3 -- old stable, last release of 2.4 series. * 2.5.2 -- stable. * 2.6.1 -- beta. Release notes: * https://github.com/tarantool/tarantool/releases/tag/1.10.8 * https://github.com/tarantool/tarantool/releases/tag/2.4.3 * https://github.com/tarantool/tarantool/releases/tag/2.5.2 * https://github.com/tarantool/tarantool/releases/tag/2.6.1 We fixed the problem with deployment of tagged revisions ([1]), so x.y.z.0 versions are here (not x.y.z.1 as it was for past releases). [1]: tarantool/tarantool#3745
5 tasks
ligurio
pushed a commit
to tarantool/expirationd
that referenced
this issue
Sep 22, 2021
ligurio
pushed a commit
to tarantool/pg
that referenced
this issue
Mar 25, 2022
ligurio
pushed a commit
to tarantool/pg
that referenced
this issue
Mar 25, 2022
ligurio
pushed a commit
to tarantool/pg
that referenced
this issue
Mar 25, 2022
ligurio
pushed a commit
to tarantool/pg
that referenced
this issue
Mar 25, 2022
ligurio
pushed a commit
to tarantool/pg
that referenced
this issue
Mar 25, 2022
ArtDu
pushed a commit
to ArtDu/expirationd
that referenced
this issue
May 10, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
travis-ci/travis-ci#7780 (comment)
The text was updated successfully, but these errors were encountered: