I discovered that last October I had apparently installed Ubuntu Xenial (16.04LTS) in a VirtualBox on my Fedora 22 host. This saved me from having to erect a new VM on which to run Jenkins. I whipped out my Jenkins notes from Jenkins VM for Continuous Deployment, and started in. I had to install:
At this point, I had to abandon my notes which are too old. I began using How to Install Jenkins Automation Service with Apache on Ubuntu 16.04. Continuing...
Next up, install and configure Apache httpd as a reverse proxy for Jenkins:
#netstat -plntu <Virtualhost *:80> ServerName xenial.jenkins.id ProxyRequests Off ProxyPreserveHost On AllowEncodedSlashes NoDecode <Proxy http://localhost:8080/*> Order deny,allow Allow from all </Proxy> ProxyPass / http://localhost:8080/ nocanon ProxyPassReverse / http://localhost:8080/ ProxyPassReverse / http://xenial.jenkins.id/ </Virtualhost>
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp6 0 0 :::8080 :::* LISTEN 23033/java tcp6 0 0 :::80 :::* LISTEN 22907/apache2
Configuring Jenkins, the domain name is xenial.jenkins.id. However, this is on a VM, so I tried to browse to http://10.0.2.15:8080. This didn't work either.
The only thing I got working was to go to localhost:8080 in a browser in the VM. It came up and I continue with the installation:
Now my problem is reaching this from elsewhere (that is, besides the VM itself). I solved this by dropping xenial, then changing the VirtualBox Network setting from NAT to Bridged.
(Incidentally, as soon as I rebooted in Bridged mode, then copy-and-paste became an option between my Fedora 22 host and xenial VM.)
Relaunching, I discovered that the IP address changed, but I was able to reach it from a browser on my Fedora 22 host using the URL below. I had already made an entry in /etc/hosts:
10.10.8.99 xenial xenial.jenkins.id http://xenial.jenkins.id:8080/
However, when I added an admin user, russ, to Jenkins, it did not take it and now I've lost the administrator password. I was able to get that back the same way I got it (from the Jenkins secrets). I got signed in again (on xenial), then changed the admin password to my own. Then I was able to log in from my Fedora 22 host.
From a browser on my Fedora 22 host, I clicked Manage Jenkins, then Configure Global Security. Then I continued the installation:
Just for fun, I continued the tutorial to test a simple automation job. To do that, I had to get out of the Manage Jenkins page and back to the simple dashboard. I clicked New Item, created a job and ran the build. It all worked. It was a great tutorial.