Why jx install runs chrome to get the admin token?

Question

When I run jx install I get those error messages

Attempting to find the Jenkins API Token with the browser in headless mode...using url http://jenkins.jx.35.205.149.20.nip.io/me/configure
unable to automatically find API token with chromedp using URL http://jenkins.jx.35.205.149.20.nip.io/me/configure
retrying after error:Running in batch mode and no default api token found

Unfortunatly, I'm running those install script from an Ansible docker container. As a consequence, I have no chrome installed in container (neither do I have an X environment and window manager).

So why is this token retrieved ? And is there a way to set it "by hand" (through another jx command, as an example) ?

James Strachan · Accepted Answer · 2018-08-29T14:56:06.587

0

there’s currently no other way with Jenkins to get an API token until we move to ephemeral / one shot masters rather than static masters.

We could disable the use of Chrome though? If it cannot use Chrome to get the API token the code asks you to visit the URL and copy/paste the api token from the Jenkins console

edited Aug 29 '18 at 14:56

answered Aug 29 '18 at 12:58

James Strachan

9,168
34
31

OK, does it impact my install if this operation fails ? – Riduidel Aug 29 '18 at 13:00
1

Without an API token jx cannot create any jobs/projects in Jenkins – James Strachan Aug 29 '18 at 14:56
however if the Chrome part fails the installer should prompt you to click the URL yourself and generate a token and copy/paste it into the installer – James Strachan Jan 04 '19 at 08:05

Why jx install runs chrome to get the admin token?

1 Answers1