Best Coldfusion Deployment Practices

I am new to Coldfusion and have inherited an already deployed project. Due to various technical limitations, it is impossible to work locally on our workstations (for example, you would do for .net). As a result, files are edited directly from test servers (and then sent to SVN).

Once again, since test db tends to lag behind prod db, we often have to edit the code directly from the prod server (please don’t blame it here, I know this is bad).

I would like to take this opportunity to return the process to something controlled:

  • Editing Local Code
  • Unit Testing Using MXUnit
  • Compliance with SVN
  • Take the hook on the SVN to be deployed to the test server
  • Testing on a test server
  • Somehow launch a deployment trigger on prod servers.

In terms of technology, I thought of a combination: CFEclipse, MXUnit, SVN, and ANT

Apart from SVN, everything will be new and subject to change if you have the best advice.

Has anyone implemented such processes and could I consult how to start?

+5
source share
2 answers

In our office, we first tried ANT + MXUnit + Selenium + TeamCity, but after a while we decided to switch to the Jenkins / Hudson continuous integration server.

There are many instructions and guides for continuous integration, so I think you do not need to explain this in detail here.

, ANT svncheckin/checkout, MXUnit, / Selenium Jenkins .

: ANT , ( :)). MXUnit , , . / Selenium , Java - . TeamCity Jenkins , , .

:

http://www.jetbrains.com/teamcity/

http://jenkins-ci.org/

http://seleniumhq.org/

BDD (Behavior driven development) JBehave http://jbehave.org/ , , "" .

!

+5

git svn. . Mylyn/Tasktop, .

0

All Articles