jmac13
Member
Hi All, (I'm using open edge 10.2b)
I've been looking at procedure libraries as a possible method for us to deploy code (or a release) to site. Currently we will make changes to our code then zip up the source code and unzip it on site and compile it in a deployment folder. Then copy across the .r's to the live folder, to me this isn’t really the best solution. So I was looking at creating a procedure library that we updated and then we would copy that across instead.
I’ve got a few concerns about using procedure libraries (see below) and wondered if anyone has used them to deploy code and if so what are their experiences etc? I’ve seen in an older thread that Cringer said he used them so if you see this post let me know your thoughts.
On the plus side I can see that because programs are loaded into memory with .pl that you can deploy code without effecting users currently connected to the system. but also at the same time I could see an issue if say Program X was changed and user A loaded up a new session but user B hadn’t that they would be using 2 different versions of program X.
Also if we wanted to release a hot fix everyone would have to log out to get this.. is there anyway round this?
Thanks
I've been looking at procedure libraries as a possible method for us to deploy code (or a release) to site. Currently we will make changes to our code then zip up the source code and unzip it on site and compile it in a deployment folder. Then copy across the .r's to the live folder, to me this isn’t really the best solution. So I was looking at creating a procedure library that we updated and then we would copy that across instead.
I’ve got a few concerns about using procedure libraries (see below) and wondered if anyone has used them to deploy code and if so what are their experiences etc? I’ve seen in an older thread that Cringer said he used them so if you see this post let me know your thoughts.
A procedure library is a bit like a .dll file in that it is a single file containing a library of .r files. It saves you having to deploy hundreds of small files all the time. We tend to work on the basis of a library.pl that contains the last major release, and a patch.pl that contains anything that has changed since the release. If handled well this should make maintenance a lot easier in the long run.
On the plus side I can see that because programs are loaded into memory with .pl that you can deploy code without effecting users currently connected to the system. but also at the same time I could see an issue if say Program X was changed and user A loaded up a new session but user B hadn’t that they would be using 2 different versions of program X.
Also if we wanted to release a hot fix everyone would have to log out to get this.. is there anyway round this?
Thanks