(but I could be wrong here).
- Calvin
-Original Message-
From: John Paul Ashenfelter [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 12, 2005 11:12 PM
To: CF-Talk
Subject: Re: Source control PLUS Deployment control...
I'm jumping into this SCC/deployment discussion pretty late, but wanted
I'm pretty suprised no one's mentioned Ant and the many, many tools
around it for the deployment side of things. Regardless of the SCC
system, Ant is a nobrainer for automating deployment,
I was about to :)...here's my experience with ant:
1. Needed to set up a system to automate a complex
I'm pretty suprised no one's mentioned Ant and the many, many tools
around it for the deployment side of things. Regardless of the SCC
system, Ant is a nobrainer for automating deployment,
.
Thirty minutes of time just saved hours of hunting down problems.
As an aside, I'll be
John, are you aware of a way to label a tree in Subversion? In VSS you can
apply a label to a whole project, and then if you need to you can deploy a
specific label, or roll back to a specific label. I can't find a similar
function in Subversion...I can see the history of individual files but
-Talk
Subject: Re: Source control PLUS Deployment control...
John, are you aware of a way to label a tree in Subversion? In VSS you
can apply a label to a whole project, and then if you need to you can
deploy a specific label, or roll back to a specific label
its own label (the version number). Just take note of which version
you want and checkout that version.
-Original Message-
From: Brian Kotek [mailto:[EMAIL PROTECTED]
Sent: Monday, 13 June 2005 11:48
To: CF-Talk
Subject: Re: Source control PLUS Deployment control...
John, are you
http://svnbook.red-bean.com/en/1.1/ch04.html
Massimo Foti
Tools for ColdFusion and Dreamweaver developers:
http://www.massimocorner.com
~|
Logware (www.logware.us):
committed change. Another way to think about it is
that revision N represents the state of the repository filesystem after
the Nth commit.
-Original Message-
From: Douglas Knudsen [mailto:[EMAIL PROTECTED]
Sent: Monday, 13 June 2005 11:58
To: CF-Talk
Subject: Re: Source control PLUS
Chip,
Insightful post, thanks. One thing that caught my eye is exporting to a
staging server calling 'svn checkout', shouldn't you 'svn export' that
instead? Checking out files also exports a flurry of .svn folders for
local version tracking, but exporting gives you a clean directory
If you are running CF Enterprise, you can use the Archive and Deploy system
built into the CF Admin. I started using it when we went through Sarbanes-Oxley
remediation. I get a ticket for a change, I make the changes, they go through
production control processing, then I create an archive on my
Hi Russ,
Does Homesite+/CFStudio have any CVS support (especially for subversion?).
We're planning to move to SVN from developing from ftp, but wondering how to
set the whole thing up.
Bunch of ways to do this with Homesite. The easiest I know of is to use
TortoiseSVN. From
I'm jumping into this SCC/deployment discussion pretty late, but
wanted to echo the votes for Subversion for source control. On the
client side, TortoiseSVN on the Windows client side is excellent and
Subclipse is there for Eclipse users.
(I haven't seen any Mac users chime in about how it works
I've been following this thread a bit and was wondering if anyone was in the
same boat as I am.
Right now we run VSS as version control of various CFM's in our test
environment. (VSS isn't necessarily our future as it was here before I was
and it really isn't suited for what we need for the
I wrote some of what you've described for an internal application (a
prototype) for a company that I used to work for, my current company also
has a custom built tool for migration management.
I don't think it is unheard of at all.
I couldn't really recommend a commercial/open source solution
For the first point, you can use your version control system to keep
both deployments in sync. Just have your production boxes check out a
working copy of your production branch, and then when you make
changes, run an 'update' on both of them.
Or you could take a different tack (what we do for
?
Russ
-Original Message-
From: Barney Boisvert [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 09, 2005 1:17 PM
To: CF-Talk
Subject: Re: Source control PLUS Deployment control...
For the first point, you can use your version control system to keep
both deployments in sync. Just have your
16 matches
Mail list logo
