RE: Source control PLUS Deployment control...
AFAIK, Dreameaver ONLY supports SourceSafe. It definitely does NOT support Subversion (I think there is an extension, but when I looked at the CVS extension from the same company, I didn't much care for it.). I don't think the webdav support in DW is sufficient for interfacing with source control (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 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 for them on Dreamweaver, but my Mac friends tell me Subversion repositories can be mounted pretty easily on OS X since it's all Web_DAV under the hood -- that's probably even easier than dealing with Tortoise for simple tasks) ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209267 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Source control PLUS Deployment control...
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 deployment that is easy to get wrong by hand. 2. Downloaded Ant. Read the readme and looked at the examples. 3. Wrote Ant script, it runs perfectly. Thirty minutes of time just saved hours of hunting down problems. As an aside, I'll be talking about these tools at CF-United in the Open Source Java Tools session and they are certainly topics that can come up at the BOF. Looking forward to that!! -Joe -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209268 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
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 talking about these tools at CF-United in the Open Source Java Tools session and they are certainly topics that can come up at the BOF. Joe, Not going to get to your talks due to geography but was wondering if you could help with the question below I've been trying to work out. I've been looking at Ant a little bit but am quite confused at what it actually can do for me. Would I be right in saying it's an automated sort of regexp text changer (ie look at all files in a targetted filelist and swap $env_dsn_1 with value 'test_dsn'?) Can it also handle the automated insert of - CF DSN's - CF Mappings - Alter Unix Shell Scripts with environment variables - Alter environment variables in CF files - Run sql scripts against a database (using the op$user account) - Integrate with the SCC System to extract a specific Tag release (in this case VSS) All depending on the enviroment (ie dev, test, prod) It's all prolly a case of RTFM (and I'm still looking at it quizically now :) but so little time, so little knowledge in this field, quick pointers would be appreciated. If you're opinionin is just to get your feet wet that'll do me too! -- David ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209272 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
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. I can't find a similar function in Subversion...I can see the history of individual files but don't see a way to label, get or rollback a whole tree to a previous state. On 6/12/05, John Paul Ashenfelter [EMAIL PROTECTED] wrote: 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 for them on Dreamweaver, but my Mac friends tell me Subversion repositories can be mounted pretty easily on OS X since it's all Web_DAV under the hood -- that's probably even easier than dealing with Tortoise for simple tasks) And the latest Subversion (1.2) added reserved checkout functionality, which is the model Visual SourceSafe (among others) uses -- files are locked until the user checks them back in. This is in addition to the base functionality of Subversion, which follows the model used by CVS and other SCC that allows anyone to check out any files and focuses on merging to resolve changes. Scripting it all You could setup all of this to run as batch files in windows or linux. The staging process could be scheduled. You could trigger the running of the staging deployment by calling a CF page with a CFExecute that runs the batch file. If you are extra crafty you might use a nifty new CF Gateway to watch for some file system chage or listen for a ping from somewhere to tell it to run and get the latest release 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, especially if you need to do things like reset databases, run test or acceptance suites, or any other of the additional quality control steps as part of an automated deployment process. Plug in CruiseControl and you've got a pretty robust system for deploying for test, stage, and production/delivery. As an aside, I'll be talking about these tools at CF-United in the Open Source Java Tools session and they are certainly topics that can come up at the BOF. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209297 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
Since SubVersion applies version numbers to the whole repo, each commit has 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 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. ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209302 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Source control PLUS Deployment control...
in SVN.so if I commit a single file in a main trunk, the whole trunk gets a new version number? CVS has tags, tag module to get what Brian is talking of. DK On 6/13/05, James Holmes [EMAIL PROTECTED] wrote: Since SubVersion applies version numbers to the whole repo, each commit has 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 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. ~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209303 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Source control PLUS Deployment control...
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): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209304 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
Yep: http://svnbook.red-bean.com/en/1.1/ch02s03.html#svn-ch-2-sect-3.2 Unlike those of many other version control systems, Subversion's revision numbers apply to entire trees, not individual files. Each revision number selects an entire tree, a particular state of the repository after some 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 Deployment control... in SVN.so if I commit a single file in a main trunk, the whole trunk gets a new version number? CVS has tags, tag module to get what Brian is talking of. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209305 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Source control PLUS Deployment control...
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 structure. Perhaps that's what the 'checkout release' does? I haven't seen or played with that feature. -nathan strutz http://www.dopefly.com/ Chip temm wrote: 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 Homesite, all of the Tortoise right-click menus will be available in the directory browsing pane (but NOT in the file browser below it). When you change a file and want to update your server version, right click its parent directory and COMMIT. Simple. If you want to use Homesite's Project-thingy with its source control integration, you will have to install something like Jalinidi Igloo which emulates SourceSafe's API (called SCC). Hasn't been worth it for me. SO, that's the client side We have a development server, where all the changes are made and tested by editing the files directly through ftp and testing them through the web browser. When they're ready, we ftp them over to the production server and use Araxis Merge to compare the changes with the old files and merge them (just for safety, and also certain files only get parts of them deployed, such as the cfc files which contain all the DAO logic). How can we make this type of set up work with SVN? I mean if we retrieve a file from CVS through Homesite+ or CFEClipse, how do we save the file to the dev server so that we can test it, and then when we're done, how do we deploy the changes to production? Is this even possible? Russ The environment Here's the thing: you need to think about source control a bit differently than you thought about the FTP method you setup. Ideally, you would have a souce control server, a staging server (you call that dev server above), a production server and your local development machine. Developing You develop on a local standalone CF server- you should be able to test anything here (except load) that you can test on your staging server. When you are happy with a certain file (or directory), you commit it to your SVN repository. On the SVN machine there is no web server, cf server, whatever- it is just a place to keep track of your changes and make sure that if everything else blows up you keep your job. Deploying to staging When you want to deploy the code to staging (to demo for a client, beta test, whatever) you go to the staging box and use tortoise (or a shell script call to cvsnt) to UPDATE (or if this is the first deployment CHECKOUT) the code from the SVN box. If you are strict, you will include in your staging deployment process a step to encrypt your CF code. This keeps you honest and doesn't allow you to make code changes on staging (from where you would likely forget to commit them). In fact, you should really do a CHECKOUT RELEASE (this is TortoiseCVS terminology- may be different on SVN) which ensures that your fresh files are not COMMITable from their new home. Deploying to production Same as deploying to staging. You don't move a thing from staging. You don't have to. All of your changes are in SVN right? If your deployment to staging worked and all other environment variables are the same, your deployment to production will be as simple as pie. Using CF Enterprise to help You could alternately create a CAR on Staging when you are ready to deploy and push that to Production. This is an additional insurance that the deployment is a success as the CAR wraps up all the CF server settings nicely for you: when you restore the CAR on the target, CF is setup exactly as it was on the source server. Saving money If you don't have an extra server for the source control, no prob. Use your staging box- but do NOT put your SVN repository in the webroot. The key is to keep source control separate from the normal running location of your apps. Scripting it all You could setup all of this to run as batch files in windows or linux. The staging process could be scheduled. You could trigger the running of the staging deployment by calling a CF page with a CFExecute that runs the batch file. If you are extra crafty you might use a nifty new CF Gateway to watch for some file system chage or listen for a ping from somewhere to tell it to run and get the latest release You're on the right path- it is less complicated than it sounds! Cheers Chip Temm ~| Logware (www.logware.us): a new and convenient web-based time
RE: Source control PLUS Deployment control...
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 test system with all of the files I need to deploy to the production system. The archive name is the ticket number. I move the archive to production, deploy it, and I have a history of everything I have done to the system. We don't have any huge clusters, so I do this all machine by machine. My team doesn't like it because it takes longer than other deployment methods, but it creates a very good audit trail, which is important to me. I could, in theory, have a non-CF person (e.g. a system admin) do the deployment of the archives into production, which would provide another level of separation of duties (big for SOX), but we're not quite there yet. My company's flagship product is a Service Management solution, it does everything you could every dream of and more in that space. It's a really cool product, but it is probably overkill times 100 for what you need. If you are curious you can read all about it on our Web site: www.peregrine.com Rob 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 future) I have an added dilemma to this. I have two separate production environments that I have to keep synced with changes. This can become daunting sometimes figuring out what changes have deployed to what production environment. Technically they should be synced, but that isn't always the case. It would be nice to be able to see what's been deployed where at any given time. I have more twists in this pretzel but that's the largest... -I run sql server here and it would be nice to also be able to keep track of the changes and deployment status of SQL -A ticketing system that can handle requests from our users and a ticketing system that can handle internal tickets for our internal fixes and upgrades. -A web based interface for the ticketing systems that allows our users to see only their tickets and their statuses. Does something like this even exist??? I am sure I am not the only one in the universe that needs to keep track of deployment as well as version control of the actual programs... Anyone have any recommendations?? Jeff ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209317 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
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 Homesite, all of the Tortoise right-click menus will be available in the directory browsing pane (but NOT in the file browser below it). When you change a file and want to update your server version, right click its parent directory and COMMIT. Simple. If you want to use Homesite's Project-thingy with its source control integration, you will have to install something like Jalinidi Igloo which emulates SourceSafe's API (called SCC). Hasn't been worth it for me. SO, that's the client side We have a development server, where all the changes are made and tested by editing the files directly through ftp and testing them through the web browser. When they're ready, we ftp them over to the production server and use Araxis Merge to compare the changes with the old files and merge them (just for safety, and also certain files only get parts of them deployed, such as the cfc files which contain all the DAO logic). How can we make this type of set up work with SVN? I mean if we retrieve a file from CVS through Homesite+ or CFEClipse, how do we save the file to the dev server so that we can test it, and then when we're done, how do we deploy the changes to production? Is this even possible? Russ The environment Here's the thing: you need to think about source control a bit differently than you thought about the FTP method you setup. Ideally, you would have a souce control server, a staging server (you call that dev server above), a production server and your local development machine. Developing You develop on a local standalone CF server- you should be able to test anything here (except load) that you can test on your staging server. When you are happy with a certain file (or directory), you commit it to your SVN repository. On the SVN machine there is no web server, cf server, whatever- it is just a place to keep track of your changes and make sure that if everything else blows up you keep your job. Deploying to staging When you want to deploy the code to staging (to demo for a client, beta test, whatever) you go to the staging box and use tortoise (or a shell script call to cvsnt) to UPDATE (or if this is the first deployment CHECKOUT) the code from the SVN box. If you are strict, you will include in your staging deployment process a step to encrypt your CF code. This keeps you honest and doesn't allow you to make code changes on staging (from where you would likely forget to commit them). In fact, you should really do a CHECKOUT RELEASE (this is TortoiseCVS terminology- may be different on SVN) which ensures that your fresh files are not COMMITable from their new home. Deploying to production Same as deploying to staging. You don't move a thing from staging. You don't have to. All of your changes are in SVN right? If your deployment to staging worked and all other environment variables are the same, your deployment to production will be as simple as pie. Using CF Enterprise to help You could alternately create a CAR on Staging when you are ready to deploy and push that to Production. This is an additional insurance that the deployment is a success as the CAR wraps up all the CF server settings nicely for you: when you restore the CAR on the target, CF is setup exactly as it was on the source server. Saving money If you don't have an extra server for the source control, no prob. Use your staging box- but do NOT put your SVN repository in the webroot. The key is to keep source control separate from the normal running location of your apps. Scripting it all You could setup all of this to run as batch files in windows or linux. The staging process could be scheduled. You could trigger the running of the staging deployment by calling a CF page with a CFExecute that runs the batch file. If you are extra crafty you might use a nifty new CF Gateway to watch for some file system chage or listen for a ping from somewhere to tell it to run and get the latest release You're on the right path- it is less complicated than it sounds! Cheers Chip Temm ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209260 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe:
Re: Source control PLUS Deployment control...
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 for them on Dreamweaver, but my Mac friends tell me Subversion repositories can be mounted pretty easily on OS X since it's all Web_DAV under the hood -- that's probably even easier than dealing with Tortoise for simple tasks) And the latest Subversion (1.2) added reserved checkout functionality, which is the model Visual SourceSafe (among others) uses -- files are locked until the user checks them back in. This is in addition to the base functionality of Subversion, which follows the model used by CVS and other SCC that allows anyone to check out any files and focuses on merging to resolve changes. Scripting it all You could setup all of this to run as batch files in windows or linux. The staging process could be scheduled. You could trigger the running of the staging deployment by calling a CF page with a CFExecute that runs the batch file. If you are extra crafty you might use a nifty new CF Gateway to watch for some file system chage or listen for a ping from somewhere to tell it to run and get the latest release 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, especially if you need to do things like reset databases, run test or acceptance suites, or any other of the additional quality control steps as part of an automated deployment process. Plug in CruiseControl and you've got a pretty robust system for deploying for test, stage, and production/delivery. As an aside, I'll be talking about these tools at CF-United in the Open Source Java Tools session and they are certainly topics that can come up at the BOF. -- John Paul Ashenfelter CTO/Transitionpoint (blog) http://www.ashenfelter.com (email) [EMAIL PROTECTED] ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209263 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
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 future) I have an added dilemma to this. I have two separate production environments that I have to keep synced with changes. This can become daunting sometimes figuring out what changes have deployed to what production environment. Technically they should be synced, but that isn't always the case. It would be nice to be able to see what's been deployed where at any given time. I have more twists in this pretzel but that's the largest... -I run sql server here and it would be nice to also be able to keep track of the changes and deployment status of SQL -A ticketing system that can handle requests from our users and a ticketing system that can handle internal tickets for our internal fixes and upgrades. -A web based interface for the ticketing systems that allows our users to see only their tickets and their statuses. Does something like this even exist??? I am sure I am not the only one in the universe that needs to keep track of deployment as well as version control of the actual programs... Anyone have any recommendations?? Jeff ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209102 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
Re: Source control PLUS Deployment control...
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 this though, as I haven't had experience with any of them lately. - Calvin On 6/9/05 11:04 AM, Jeff Waris [EMAIL PROTECTED] wrote: 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 future) I have an added dilemma to this. I have two separate production environments that I have to keep synced with changes. This can become daunting sometimes figuring out what changes have deployed to what production environment. Technically they should be synced, but that isn't always the case. It would be nice to be able to see what's been deployed where at any given time. I have more twists in this pretzel but that's the largest... -I run sql server here and it would be nice to also be able to keep track of the changes and deployment status of SQL -A ticketing system that can handle requests from our users and a ticketing system that can handle internal tickets for our internal fixes and upgrades. -A web based interface for the ticketing systems that allows our users to see only their tickets and their statuses. Does something like this even exist??? I am sure I am not the only one in the universe that needs to keep track of deployment as well as version control of the actual programs... Anyone have any recommendations?? Jeff ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209129 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
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 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 our clusters). We have a single master server that we push all updates to. That server, as part of recieving updates, ensure that they are propogated to all other machines, both in the cluster it's a member of, and our backup cluster at a different datacenter. So when we add a new machine, we register it as a slave with the master server, and it immediately gets all updates that are passed to the master. It works really well, as long as having all your servers updated at the same time is a reasonable course of action (which is not the case a lot of times). cheers, barneyb On 6/9/05, Jeff Waris [EMAIL PROTECTED] wrote: 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 future) I have an added dilemma to this. I have two separate production environments that I have to keep synced with changes. This can become daunting sometimes figuring out what changes have deployed to what production environment. Technically they should be synced, but that isn't always the case. It would be nice to be able to see what's been deployed where at any given time. snip / -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209132 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
RE: Source control PLUS Deployment control...
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. We have a development server, where all the changes are made and tested by editing the files directly through ftp and testing them through the web browser. When they're ready, we ftp them over to the production server and use Araxis Merge to compare the changes with the old files and merge them (just for safety, and also certain files only get parts of them deployed, such as the cfc files which contain all the DAO logic). How can we make this type of set up work with SVN? I mean if we retrieve a file from CVS through Homesite+ or CFEClipse, how do we save the file to the dev server so that we can test it, and then when we're done, how do we deploy the changes to production? Is this even possible? 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 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 our clusters). We have a single master server that we push all updates to. That server, as part of recieving updates, ensure that they are propogated to all other machines, both in the cluster it's a member of, and our backup cluster at a different datacenter. So when we add a new machine, we register it as a slave with the master server, and it immediately gets all updates that are passed to the master. It works really well, as long as having all your servers updated at the same time is a reasonable course of action (which is not the case a lot of times). cheers, barneyb On 6/9/05, Jeff Waris [EMAIL PROTECTED] wrote: 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 future) I have an added dilemma to this. I have two separate production environments that I have to keep synced with changes. This can become daunting sometimes figuring out what changes have deployed to what production environment. Technically they should be synced, but that isn't always the case. It would be nice to be able to see what's been deployed where at any given time. snip / -- Barney Boisvert [EMAIL PROTECTED] 360.319.6145 http://www.barneyb.com/ Got Gmail? I have 50 invites. ~| Logware (www.logware.us): a new and convenient web-based time tracking application. Start tracking and documenting hours spent on a project or with a client with Logware today. Try it for free with a 15 day trial account. http://www.houseoffusion.com/banners/view.cfm?bannerid=67 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:209134 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations Support: http://www.houseoffusion.com/tiny.cfm/54
