{"action":"opened","issue":{"url":"https://api.github.com/repos/spotify/helios/issues/909","repository_url":"https://api.github.com/repos/spotify/helios","labels_url":"https://api.github.com/repos/spotify/helios/issues/909/labels{/name}","comments_url":"https://api.github.com/repos/spotify/helios/issues/909/comments","events_url":"https://api.github.com/repos/spotify/helios/issues/909/events","html_url":"https://github.com/spotify/helios/issues/909","id":151878581,"number":909,"title":"Offline mode for helios solo and TemporaryJobs","user":{"login":"mattnworb","id":113840,"avatar_url":"https://avatars.githubusercontent.com/u/113840?v=3","gravatar_id":"","url":"https://api.github.com/users/mattnworb","html_url":"https://github.com/mattnworb","followers_url":"https://api.github.com/users/mattnworb/followers","following_url":"https://api.github.com/users/mattnworb/following{/other_user}","gists_url":"https://api.github.com/users/mattnworb/gists{/gist_id}","starred_url":"https://api.github.com/users/mattnworb/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mattnworb/subscriptions","organizations_url":"https://api.github.com/users/mattnworb/orgs","repos_url":"https://api.github.com/users/mattnworb/repos","events_url":"https://api.github.com/users/mattnworb/events{/privacy}","received_events_url":"https://api.github.com/users/mattnworb/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/spotify/helios/labels/enhancement","name":"enhancement","color":"84b6eb"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-29T14:20:34Z","updated_at":"2016-04-29T14:20:34Z","closed_at":null,"body":"A number of internal users have requested a way to be able to use TemporaryJobs and HeliosSoloDeployment in an offline mode, to be able to still run tests that use TemporaryJobs and docker images already cached on the local machine. \r\n\r\nFor instance, if the images referred to in a TemporaryJob would normally be pulled from a private registry behind a VPN and the test is run when not on the VPN.\r\n\r\nObviously this can't work for 100% of cases (if the local host doesn't have the image tag then nothing can proceed).\r\n\r\nOne possible way this could work is to support a system property that could be invoked like\r\n\r\n```\r\n$ mvn -DheliosSolo.offline verify\r\n```\r\n\r\nwhen this system property is set, then\r\n\r\n1. HeliosSoloDeployment shouldn't attempt to pull the helios-solo image before starting a container\r\n2. The helios agent spawned by helios-solo would have to be told to disable pulls before container starts (passed via an environment variable for example).\r\n3. ???\r\n\r\n"}}