Forum Post: RE: Mixed projects in OpenEdge Studio and svn

[andrew.may]

We have a general guideline that a dev must be able to just pull a project from source control, run a build script to do any required initialisation & then be able to run / develop it straight away. We also want a project to be able to be built straight after being pulled from source control We tend to have: · Source + ant build script + distributable resources + Ivy dependencies file - all in the main project’s source control repository · Build script can be run on a Dev PC (for testing purposes) without any extra setup. · Release + QA builds are done on a Hudson instance. · Hudson Jobs configured to pull the required version of the SCM repository & then run the ant build script that is in the pulled repo · Hudson Job config is not in SCM (I’m uneasy about this, but haven’t had the chance to change it yet) · Build script uses Ivy to pull in dependencies (e.g. our framework & utility libraries) from an Artifactory instance · Build script then compiles source, packages it up in a .pl file & produces a zip containing the .pl file, any .pl files brought in as dependencies & any distributable resources (e.g. icons / default config files) · If project is a library or framework project then Hudson will also publish the .pl and/or .zip files to Artifactory so that downstream jobs can fetch them later. · Hudson then triggers any downstream jobs From: Peter van Dam [mailto:bounce-pdam@community.progress.com] Sent: 30 September 2014 10:27 To: TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] Mixed projects in OpenEdge Studio and svn Mixed projects in OpenEdge Studio and svn Thread created by Peter van Dam Hi there, I am wondering how others are handling the situation where you have a project that mixes stuff like the following: - ABL code - all kinds of scripts, including linux, jenkins, ant, etc. - documentation - test data - ABL test code We would ideally want all this stuff in a single project, since it is a single project, but we only want the ABL subdirectory contents (objects and static files) distributed to the build location. So basically we would only want the compiled objects and static objects from, say, the src directory distributed to the build location (without the src directory prefix). How do you configure this? Thanks, -peter Stop receiving emails on this subject. Flag this post as spam/abuse.

Continue reading...