R
Rob Fitzpatrick
Guest
As long as the windows system matches (gui vs. tty) you can take the 64-bit t-code from your build system and deploy it to your clients running 64-bit OE, regardless of distro. You didn't mention your OE version, but on 11.x, again as long as you stay within the same window system, you can deploy the same r-code to 32-bit and 64-bit clients. You could put up a build system in Arcade but I don't know if that would streamline the process. You would need to push source code to it (unless it was also a code repository) and then push PLs from it to your clients. Whereas if the server was local then you would build and push. If you are no longer compiling at the client site you will need to maintain schema-holder DBs on your build server; these would be your compile targets. You'll need a process to keep them current with the schema changes you deploy to client sites. There have been some recent conference talks on automated builds and continuous integration. You may want to look into that to further automate your code deployments. From Progress Exchange 2013: Beginner's Guide to Continuous Integration Gilles Querret, Riverside Software slides: http://www.progress.com/~/media/Progress/Documents/News%20and%20Events/Exchange2013/Track%203%20-%20Beginners%20guide%20to%20continuous%20integration.pdf video: http://www.youtube.com/watch?v=_ETXNLN7hGI&list=PLC679RvCan2As0qGgpU5aJg49slSfo-2Q&index=4 Also have a look at Progress Compilation Tools (PCT), also from Gilles Querret.
Continue reading...
Continue reading...