And, we also moved to using ASP.NET, which added the complication of having a build step in the process. The number of people using the site increased massively, making it less and less practical to just put code changes multiple times during the day. The code base got bigger, making it more difficult to keep in sync. The teams responsible for testing and for maintaining the database and servers got increasingly nervous about developers having the ability to push code at any time. For a start there were more people involved. This was much better, but still relied on the developer doing the push to have the correct files on their local machine.Īs the site got bigger there were some new complications. Later, as we moved to having multiple web servers which each required a copy of the code, we created a simple Windows application which copied the files from our local directory onto each of the web servers and would also execute selected SQL scripts against the production database. We only got away with this because there were not many people writing code and there were not many people using the site. In the very early days we just copied ASP scripts directly onto the production server. What we called “the deployment process” changed a lot during my time at Trade Me. when there is a bug on the site that you quickly need to fix) you’re sure to forget some critical step and make an even bigger hole for yourself. Ideally it should be a one click process. How many steps does it take to get a change live on your website?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |