git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Strange annotated tag issue

From
Jeff King <peff@peff.net>
Date
Mar 25, 2019, 23:36 UTC
Message-ID
<20190325233644.GC23728@sigill.intra.peff.net>
In-Reply-To
<CAGyf7-EOrCgPY19jgwRd5H-0ADMX9WtLUuACmTAANnNVW-K-_Q@mail.gmail.com>
On Mon, Mar 25, 2019 at 11:43:52AM -0700, Bryan Turner wrote:
Show 21 quoted lines
> > I don't think I've ever seen a tag-to-a-tag in the wild, but I wouldn't
> > be surprised if somebody has found a use for it. For example, because
> > tags can be signed, I can make a signature of your signature, showing a
> > cryptographic chain of custody.
> 
> For a while the Atlassian Bamboo team followed a workflow where they
> would do a build in CI, tag that build and then deploy it to a sandbox
> environment for smoke testing. If it passed the smoke tests, it would
> get "promoted" from the sandbox environment to internal instances used
> by the various teams to do their builds. When a sandbox build was
> "promoted", they'd create a tag of the sandbox build's tag to have
> traceability between the two environments.
> 
> I'm not advocating for or judging that workflow one way or another,
> and the Bamboo team has since moved on to a different workflow. I just
> thought I'd share it as a tag-of-tag workflow that I've seen a real
> team using. (There was one place in Bitbucket Server's code where we
> didn't handle recursive tags correctly, so their workflow caused some
> errors that I needed to make some adjustments for. As a result,
> Bitbucket Server's test suite now includes tests that cover tag-of-tag
> behaviors.)

Thanks, I always like hearing these kinds of data points. If nothing else, it's a good reminder that if Git has behaved some way for many years, then _somebody_ is likely to have taken advantage of it, whether we considered it a possibility or not. :)

-Peff
Previous: Bryan TurnerNext: Ævar Arnfjörð Bjarmason
Message 9 of 48 in “Strange annotated tag issue”
  1. Robert DaileyMar 21, 2019
  2. Bryan TurnerMar 21, 2019
  3. Jeff KingMar 21, 2019
  4. Jeff KingMar 21, 2019
  5. Robert DaileyMar 25, 2019
  6. Jeff KingMar 25, 2019
  7. Robert DaileyMar 25, 2019
  8. Bryan TurnerMar 25, 2019
  9. Jeff KingMar 25, 2019
  10. Ævar Arnfjörð BjarmasonMar 25, 2019
  11. Jeff KingMar 25, 2019
  12. 0/3 tag: prevent recursive tagsDenton Liu, Mar 26, 2019
  13. 1/3 tag: prevent recursive tagsDenton Liu, Mar 26, 2019
  14. Denton LiuMar 26, 2019
  15. Ævar Arnfjörð BjarmasonMar 26, 2019
  16. Elijah NewrenMar 27, 2019
  17. Ævar Arnfjörð BjarmasonMar 27, 2019
  18. Robert DaileyMar 28, 2019
  19. 2/3 t7004: ensure recursive tag behavior is workingDenton Liu, Mar 26, 2019
  20. Ævar Arnfjörð BjarmasonMar 26, 2019
  21. 3/3 git-tag.txt: document --allow-recursive-tag optionDenton Liu, Mar 26, 2019
  22. Ævar Arnfjörð BjarmasonMar 26, 2019
  23. Jeff KingMar 26, 2019
  24. 0/2 tag: prevent nested tagsDenton Liu, Apr 2, 2019
  25. 1/2 tag: fix formattingDenton Liu, Apr 2, 2019
  26. 2/2 tag: prevent nested tagsDenton Liu, Apr 2, 2019
  27. 2/2 tag: prevent nested tagsDenton Liu, Apr 2, 2019
  28. Junio C HamanoApr 3, 2019
  29. Junio C HamanoApr 3, 2019
  30. Robert DaileyApr 3, 2019
  31. Junio C HamanoApr 4, 2019
  32. Robert DaileyApr 4, 2019
  33. Junio C HamanoApr 4, 2019
  34. Robert DaileyApr 5, 2019
  35. Johannes SixtApr 3, 2019
  36. Denton LiuApr 3, 2019
  37. Jeff KingApr 4, 2019
  38. Junio C HamanoApr 4, 2019
  39. Jeff KingApr 4, 2019
  40. Junio C HamanoApr 4, 2019
  41. Jeff KingApr 4, 2019
  42. Eckhard MaaßApr 11, 2019
  43. Junio C HamanoApr 12, 2019
  44. Elijah NewrenApr 5, 2019
  45. Junio C HamanoApr 5, 2019
  46. 0/2 tag: advise on recursive taggingDenton Liu, Apr 4, 2019
  47. 1/2 tag: fix formattingDenton Liu, Apr 4, 2019
  48. 2/2 tag: advise on nested tagsDenton Liu, Apr 4, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.