{"action":"opened","issue":{"url":"https://api.github.com/repos/geerlingguy/ansible-role-jenkins/issues/47","repository_url":"https://api.github.com/repos/geerlingguy/ansible-role-jenkins","labels_url":"https://api.github.com/repos/geerlingguy/ansible-role-jenkins/issues/47/labels{/name}","comments_url":"https://api.github.com/repos/geerlingguy/ansible-role-jenkins/issues/47/comments","events_url":"https://api.github.com/repos/geerlingguy/ansible-role-jenkins/issues/47/events","html_url":"https://github.com/geerlingguy/ansible-role-jenkins/issues/47","id":150017615,"number":47,"title":"Release of jenkins 2.0 seems to break this role","user":{"login":"blaffoy","id":2404294,"avatar_url":"https://avatars.githubusercontent.com/u/2404294?v=3","gravatar_id":"","url":"https://api.github.com/users/blaffoy","html_url":"https://github.com/blaffoy","followers_url":"https://api.github.com/users/blaffoy/followers","following_url":"https://api.github.com/users/blaffoy/following{/other_user}","gists_url":"https://api.github.com/users/blaffoy/gists{/gist_id}","starred_url":"https://api.github.com/users/blaffoy/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/blaffoy/subscriptions","organizations_url":"https://api.github.com/users/blaffoy/orgs","repos_url":"https://api.github.com/users/blaffoy/repos","events_url":"https://api.github.com/users/blaffoy/events{/privacy}","received_events_url":"https://api.github.com/users/blaffoy/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-04-21T09:23:44Z","updated_at":"2016-04-21T09:23:44Z","closed_at":null,"body":"With the release of [Jenkins 2.0](http://mirrors.jenkins-ci.org/debian/jenkins_2.0_all.deb), the deployment procedure has changed somewhat. On first installing and starting, Jenkins 2.0 wants to lead you through a one time set up of an admin user. In order to do so, you must enter a one time password written to /\r\n\r\nThis password should be pasted into the web UI in order to allow configuration of an admin user.\r\n\r\nUntil such a user is set up, Jenkins will deny any attempts to use jenkins-cli.jar. This role relies on that CLI interface to install plugins (and I would guess for other features too).\r\n\r\nI think that being able to specify which version of Jenkins you wish to install would workaround this problem, as in this issue: https://github.com/geerlingguy/ansible-role-jenkins/issues/38\r\n"}}