Lets say our team wants to push a perl script to production asap. The developer has committed the code in subversion. Now how does this reach the build person? Do you use any modern tools for requesting/approval process for the release. Right now we are using our own system developed using perl/cgi which scans for the new commits and displays it so that dev can choose the file with the version and request a code release.
We want to improvise this as we are moving to svn. How does everyone achieve this? What tools, plugins do you use for requesting a particular file and its version? How about the approvals?
that does the notification (via email). In this case, I usually prefer to have the developers tag their release and the build engineer takes the tagged release and then independantly does the official build, package and deploy.
Why don't you tell us a little more about what you are trying to do!
Thanks for your reply. Yes, we will have the developers tag the release and build engineer take it from there. I am looking for the exact workflow followed after the tag is created. Do you communicate through emails? How about the approvals? I am looking to see if there is any tool out there to track the releases. Right now we use a cgi/perl form for this. We use makefile approach to checkout SVN tags. This makefile resides in CVS so that we can select this file on our form and request a release. We are out-dated, we use paper copies of the request and get approvals and peer reviews. I am looking to get rid of this. I also do not like using CVS to make an SVN release. I hope this makes sense. Please ask if you have any further questions.
Thanks
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.
