The Jenkins Controller is preparing for shutdown. No new builds can be started.
Started by user Sven Gothel Building remotely on linux64-NVFX580-ubuntu10-jogamp-x32-c3d-003 (linux-x86_32-nvidia) in workspace /home/jogamp/JogAmpSlavex32/workspace/gluegen_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/gluegen.git Fetching upstream changes from git://jogamp.org/srv/scm/gluegen.git > git --version > git fetch --tags --progress git://jogamp.org/srv/scm/gluegen.git +refs/heads/*:refs/remotes/origin/* > git rev-parse origin/master^{commit} Checking out Revision 360c2d89e162616f5596dc83561601e0378bdb11 (origin/master) > git config core.sparsecheckout > git checkout -f 360c2d89e162616f5596dc83561601e0378bdb11 > git rev-list a4f7d51f5a643fcf528711ea0e1bbd19158f5f7c 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 joal_onmaster Notifying upstream projects of job completion Finished: SUCCESS