Running Omnis Studio from command line using Jenkins

[Derek Delpero]

Hi Henk,

Maybe you need an hdmi adapter to run the mac mini headless?

http://www.fit-pc.com/web/products/fit-headless/fit-headless-for-mac-mini/

You can also make one pretty easily:
https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html

Derek


On Tue, Mar 28, 2017 at 4:31 AM, H.P. Noppe <henk at omnihis.nl> wrote:

> Dear Omnis people,
>
> Again something about Omnis Studio and running it from the command line.
> And also there is some unit testing and Jenkins involved. We too are using
> this to build a library overnight and running our unit tests on this build.
> The way we have setup is that for the nightly build we use a MacOS 10.12.3
> mcMini as slave. On this machine an Omnis Studio 5.0.1 is running in which
> the Omnis Studio VCS Build Scheduler is set to build the library. A Jenkins
> job picks it up and uses this to run the unit tests. For this we have two
> separate jobs.
> One to pick up the library and stores it on our FTP server and stores it
> as an artifact. A second one who picks up the artefact. This job is copying
> it back to the same slave and runs a shell script similar as below.
>
> open -a "/Applications/Omnis Studio 5.0.1 UnitTest.app”
> “pathToLibrary/TestLibaryName.lbs" --args --outputpath="$WORKSPACE/"
> --test-suite=“TestAll"
>
> This works like a charm as long there is a monitor attached to the
> computer or we have a VNC session open. The build Job is working just fine,
> but as soon you want to start Omnis from the command line you run into
> trouble. We use a different Omnis Studio.app for the build and running the
> unit tests. Does anyone have similar experiences with Omnis Studio and
> Jenkins. And is there a way to solve this?
>
> Grtz Henk
>
>
>
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com
>