Started by user Sven Gothel
Building remotely on win64-nvgtx460-win7-jogamp-x64-sgothel-011 (win7-x86_64-nvida) in workspace c:\JogAmpSlavex64\workspace\jogl_onmaster
 > git rev-parse --is-inside-work-tree
Fetching changes from the remote Git repository
 > git config remote.origin.url git://jogamp.org/srv/scm/jogl.git
Fetching upstream changes from git://jogamp.org/srv/scm/jogl.git
 > git --version
 > git fetch --tags --progress git://jogamp.org/srv/scm/jogl.git +refs/heads/*:refs/remotes/origin/*
 > git rev-parse "origin/master^{commit}"
Checking out Revision 043a9f751ab24e1c50a333d97a7f8f78e5e2a7a1 (origin/master)
 > git config core.sparsecheckout
 > git checkout -f 043a9f751ab24e1c50a333d97a7f8f78e5e2a7a1
 > git rev-list bcda2dad1a6569ffd4eba07b231d50fdafc60b7f
 > git remote
 > git submodule init
 > git submodule sync
 > git config --get remote.origin.url
 > git submodule update --init --recursive
No emails were triggered.
Triggering linux64-null-centos55-jogamp-x64-chuck-001
Configuration linux64-null-centos55-jogamp-x64-chuck-001 is still in the queue: linux64-null-centos55-jogamp-x64-chuck-001 is offline
linux64-null-centos55-jogamp-x64-chuck-001 completed with result SUCCESS
No emails were triggered.
Warning: you have no plugins providing access control for builds, so falling back to legacy behavior of permitting any downstream builds to be triggered
Triggering a new build of jogl-demos_onmaster #43
Notifying upstream projects of job completion
Finished: SUCCESS