Force Tag Push fails

694 views
Skip to first unread message

Sundar Shankar

unread,
Jul 12, 2013, 8:10:21 PM7/12/13
to repo-d...@googlegroups.com
I am trying to create floating tag for my project (LastGood) to keep track last successful builds. But, Gerrit is NOT allowing me to delete already existing tag on server.

git push origin :refs/tags/LastGood
remote: Branch refs/tags/LastGood:
remote: You need 'Push' rights with the 'Force Push'
remote: flag set to delete references.
remote: User: sundar
remote: Please read the documentation and contact an administrator
remote: if you feel the configuration is incorrect
remote: Processing changes: refs: 1, done   
To ssh://example.localhost.com:29418/test.git
 ! [remote rejected] LastGood (cannot delete references)

I have tried all these permissions for
Reference: refs/tags/*

Create Reference
Forge Committer Identity
Push
Push Merge Commit
Push Annotated Tag
Push Signed Tag

I have read somewhere that to delete tag needs 'Push Branch +3'. Not sure, how to set this credentials ? Any help will be appreciated.

-Sundar

Saša Živkov

unread,
Jul 13, 2013, 3:57:30 AM7/13/13
to Sundar Shankar, repo-d...@googlegroups.com
Have you tried Push+force on refs/tags/* ?




--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
 
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

sundar

unread,
Jul 13, 2013, 1:17:39 PM7/13/13
to Saša Živkov, repo-d...@googlegroups.com
Yes. It worked -:). Thanks Edwin and Sasa.

-Sundar

Magnus Bäck

unread,
Jul 15, 2013, 9:05:57 AM7/15/13
to repo-d...@googlegroups.com
On Friday, July 12, 2013 at 20:10 EDT,
Sundar Shankar <sundar...@gmail.com> wrote:

> I am trying to create floating tag for my project (LastGood) to keep
> track last successful builds.

I'm not sure you want to use tags for this. Git will not touch existing
tags when they're modified upstream (at least not annotated tags), so
only new clones will point to the current values of the tags. You should
probably use branches instead.

[...]

--
Magnus Bäck
ba...@google.com

Nicholas Mucci

unread,
Jul 16, 2013, 4:54:38 PM7/16/13
to repo-d...@googlegroups.com
I agree with Magnus here.  In the "git tag" man page, there's some very useful discussion about the risks and consequences of your proposal.

-Nick
Reply all
Reply to author
Forward
0 new messages