Automated Build Process for a new module

I am looking to automate the build process for a module we developed from our source control. For this we have to compile all the .os files in the module and make it as an .oll file for every ospace. Can anyone give me some details on how to get started with this.

I tried to look into the details on how the eclipse is generating the oll files when we click on the build module option, but I couldn't any details from their.

Find more posts tagged with

Comments

appuGmail

I was fortunate (or is it un-? ) to be part of a early team who had lots of old 971/10 code builder days and were thrust upon CSIDE development earlier (in the 2014/15 era)

We were new to TFS we were not new to Oscript.We were also new to Eclipse. Here's how a bunch of Developers collaborated on developing stuff.Hopefully you can

wait for OT to give you better/current suggestions and take my advice with a pinch of salt(sea).

Example was a new module that we developed based on a logger/database subsystem,details not relevant only concentrate on the work involved

Developer A creates new module in his personal CSIDE environment.The strawman is made and checked into TFS
Developer A, B, C,D,E now works on individual task individually checking in things what is humanly possible so that not stepping on each person's toes.
If Developer A built a RH new and it checked out good using some kind of messaging(email,shout on top of the cube etc) Developer B,C,D,E would get the new RH if they pull in source.If it was weblingo then we had our own java utility that would sync weblingo.This process repeated until developers thought it can be functionally tested(Quasi Agile,hey new things learnt on the way )
We had a RDP VM box which we reserved as our "code maker",one would login to the "code maker" account and make a cut on that.Think of it as one of our developers putting that hat.I could assume any admin could be trained to do that step as well as it just involved very simple instruction but it could only be done on a machine that had LL server and CSIDE on it and the module in question was installed there to start with. The RDP VM box was selected as in this new environment it was very difficult to tell eclipse errors from Oscript errors so our way of a clean slate.
This .OLL would then make its way to our TEST environment that had load balanced and more resources and a clone of a database that had more stuff in it.
If Testing on TEST proved successful then it would go to Staging(pre production) and then business users would test it.
This cycle repeated until code was released to production.

A livelink server as it stands now can only see code in .OLL format .Some companies still use Builder to do work across many varieties of livelink.

Ours was a small team of home grown oscript developers who were hitherto not using any advanced techniques so we had a lot of teething pains

which we derived a workable process because at the end our goal was to produce new modules in the new OT paradigm.

I had asked OT to actually make it easier for Oscripters to get a set of .OS files and create an installable thing I bet a lot of old programmers like me

would have asked as well,but still even in 16.0 it does not seem like an option.The Company Oscripters are a dying breed as OT scares anyone from attempting Oscript,

a pity,as more people see the code they lead to better code, at least what I think. What is left out are Oscripters who work for product delivery companies working on the OT Eco System....

that OT cannot prevent because there are many gaps they fill that are needed very dearly by users

BTW the build code behind the scenes invoke the oscript compiler. For many of us builder based oscripters the module explorer mostly seems to look like builder.

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Mon, Oct 2, 2017 at 10:51 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

Automated Build Process for a new module Posted byPati, SathwikOn 10/02/2017 11:48 AM

I am looking to automate the build process for a module we developed from our source control. For this we have to compile all the .os files in the module and make it as an .oll file for every ospace. Can anyone give me some details on how to get started with this.I tried to look into the details on how the eclipse is generating the oll files when we click on the build module option, but I couldn't any details from their.
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center CS16

Sathwik_Pati

Hi Krishnankutty,

Can you elaborate Step 4 a little?
I assume that you have a seperate machine for generating build and all the code is pulled into that machine and a build is generated. Is that correct?

appuGmail

To be quite honest this is what we used we created snapshot VM's that had a working Livelink,its database,a CSIDE installed ,TFS connections set up and some very basic folder structures,categories etc I built first.Using cloning technology of VM's which I do not possess this so this was provisioned as Dev VM1,2,3,4 like that and all developers were given tasks .At some point before it can be put to a wider audience we needed a golden build of a module.This would check if any developer made incorrect assumptions or dependencies,so our golden code maker was just a snap shot where anyone can log in(theoretically) and we had a TFS expert with us who modelled how this would happen in a .NET shop.So we followed whatever he said and had naming schemes and what not.We noticed that if we re going to re-use a dev VM albeit using a different log on account then Eclipse would throw a fit on workspace being locked and what not.We were not a java shop to talk eclipse all the time so we resorted to a simpler approach that is all.

So long as developer machines are self sustaining I don't think you would have a problem doing collaborative programming.

So what you said is correct

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Tue, Oct 3, 2017 at 12:07 PM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

[EXTERNAL] - Re Automated Build Process for a new module Posted byPati, SathwikOn 10/03/2017 01:00 PM

Hi Krishnankutty,Can you elaborate Step 4 a little?
I assume that you have a seperate machine for generating build and all the code is pulled into that machine and a build is generated. Is that correct?
[To post a comment, use the normal reply function]
Topic: Automated Build Process for a new module
Forum: Content Server Development Forum
Content Server: Knowledge Center CS16