From: roylee17 <roylee17@gmail.com>
To: git@vger.kernel.org
Subject: How to add daily tags for a central repo?
Date: Mon, 31 May 2010 22:21:51 -0700 (PDT) [thread overview]
Message-ID: <1275369711233-5124575.post@n2.nabble.com> (raw)
Hi,
We currently host our projects on a central server.
For the daily build purpose, I currently using a script to do the following
steps:
1. clone the project from the central server
2. find the target commit for a specified date
commit=`git log origin/master -n1 --format=%H --until="${timespec}
00:00:00"`
3. tag the commit
git tag -f daily/${timespec} ${commit}
4. push the tag up to the central server
This usually works fine and allows us to tag earlier commit with past dates
However, it depends on the "COMMIT DATE", which is a local time to the
developer who
committed the changes.
And if some developer didn't have the time or date configured correctly on
his machine,
the changes committed by him may not be included in a tag, even it is pushed
to the
on a date earlier than the target date to tag.
Alternatively, we can queue the job to do the following steps "on a target
date":
1. clone the project from the central server
2. tag the "latest commit"
3. push the tag to the server
But I'd like to know better ways to do the daily tag things?
Roy
--
View this message in context: http://git.661346.n2.nabble.com/How-to-add-daily-tags-for-a-central-repo-tp5124575p5124575.html
Sent from the git mailing list archive at Nabble.com.
next reply other threads:[~2010-06-01 5:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-01 5:21 roylee17 [this message]
2010-06-01 6:43 ` How to add daily tags for a central repo? Michael J Gruber
2010-06-01 7:55 ` Roy Lee
2010-06-01 8:05 ` Michael J Gruber
2010-06-01 8:25 ` Roy Lee
2010-06-01 8:52 ` Michael J Gruber
2010-06-01 9:45 ` Roy Lee
2010-06-01 22:20 ` Ilari Liusvaara
2010-06-02 4:40 ` Junio C Hamano
2010-06-02 7:55 ` Roy Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1275369711233-5124575.post@n2.nabble.com \
--to=roylee17@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).