Running Omnis Studio from command line using Jenkins

[Doug Easterbrook]

hi Henk:

we use the newtech dongle that alex mentioned on all of our mac mini servers..   makes a huge difference.



Doug Easterbrook
Arts Management Systems Ltd.
mailto:doug at artsman.com
http://www.artsman.com
Phone (403) 650-1978




National User Conference, May 8-11, 2017
https://tickets.proctors.org/TheatreManager/95/online&perf=27956

> On Mar 28, 2017, at 7:58 AM, H.P. Noppe <henk at omnihis.nl> wrote:
> 
> Thank you Alex and Derek,
> 
> I will have look into this. I had to laugh how ridiculous simple the dongle can be made. :D
> 
> Grtz Henk
> 
>> 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/ <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 <https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html>
>> 
>> Derek
> 
>> On 28 Mar 2017, at 15:40, Alex Clay <aclay at mac.com <mailto:aclay at mac.com>> wrote:
>> 
>> Hi Henk,
>> 
>> On the Mac, Omnis uses graphic acceleration. When running purely headless, this acceleration is disabled and Omnis runs slooooow. You have a few options to handle this:
>> 
>> 1) Keep a screen-sharing session up to the machine, which is your current solution
>> 2) Connect a display or KVM switch. This is what we do
>> 3) Add a dongle that tricks the Mac into thinking a display is connected. We've using this in the past successfully
>> 
>> For the dongle, you can roll your own with a VGA adaptor and a resistor:
>> 
>> https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html <https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html> <https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html <https://macminicolo.net/blog/files/build-a-dummy-dongle-for-a-headless-mac-mini.html>>
>> 
>> You can also purchase a dongle that's specifically designed for this.
>> 
>> MiniDisplay: http://www.newertech.com/products/cblmdpheadb.php <http://www.newertech.com/products/cblmdpheadb.php> <http://www.newertech.com/products/cblmdpheadb.php <http://www.newertech.com/products/cblmdpheadb.php>>
>> 
>> HDMI: http://www.newertech.com/products/hdmi_headless_video_adapter.php <http://www.newertech.com/products/hdmi_headless_video_adapter.php> <http://www.newertech.com/products/hdmi_headless_video_adapter.php <http://www.newertech.com/products/hdmi_headless_video_adapter.php>>
>> 
>> One of our colocation providers, MacStadium. put up this video showing some performance differences using these devices:
>> 
>> https://www.youtube.com/watch?v=BV_PJVhxj54 <https://www.youtube.com/watch?v=BV_PJVhxj54> <https://www.youtube.com/watch?v=BV_PJVhxj54 <https://www.youtube.com/watch?v=BV_PJVhxj54>>
>> 
>> I hope this helps!
>> 
>> Alex
>> 
>> 
>>> On Mar 28, 2017, at 05:31, H.P. Noppe <henk at omnihis.nl <mailto: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 <http://lists.omnis-dev.com/>
>> 
>> _____________________________________________________________
>> Manage your list subscriptions at http://lists.omnis-dev.com <http://lists.omnis-dev.com/>
> 
> _____________________________________________________________
> Manage your list subscriptions at http://lists.omnis-dev.com