I don't think that you're missing something. This is probably just an communication issue - IMHO Kamil thought that you have some "automated deployment" tool in your hands, which will always checkout and update staging to the latest 'pre-release' tag.
j.
----- Original Message -----
From: "Tim Flink" tflink@redhat.com To: "AutoQA development" autoqa-devel@lists.fedorahosted.org Sent: Wednesday, November 23, 2011 3:44:46 PM Subject: Re: Deploying to staging
On Wed, 23 Nov 2011 04:11:28 -0500 (EST) Kamil Paral kparal@redhat.com wrote:
Once other have had the chance to look at the code, we can push to master and do another build (either another pre-release or go for 0.7.0).
Tim,
are we able to deploy arbitrary git commit to staging, or do we have to tag it as "pre-release" every time we want to update staging?
I've not been tagging anything in git, just updating the spec and pushing to master.
Am I missing part of the process somewhere?
Tim
autoqa-devel mailing list autoqa-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/autoqa-devel