CODEWITHSUNDEEP
jenkinsopenshiftconfigstartup
Peter Gordon
Peter Gordon

Reputation: 1077

Where is jenkins config.xml? And why is this error appearing?

These two parts are together because I think they're related to each other.

I'm running Jenkins' latest LTS war file (v1.596.2) directly from the command line. I'm using an Openshift DIY cartridge to do this.

I have set my "JENKINS_HOME" environment variable to "$OPENSHIFT_DATA_DIR/jenkins".

export JENKINS_HOME=$OPENSHIFT_DATA_DIR/jenkins

Part 1: where is my config.xml file?

This works fine and most files seem to have been stored there fine, but I can't find the config.xml file... I'm probably overlooking something but I can't find it anywhere!

Part 2: Boot up error

I also have this error when I boot up my server using:

java -jar jenkins.war --httpListenAddress=$OPENSHIFT_DIY_IP --ajp13Port=-1

It shows this error message in the console: http://pastebin.com/30eBBHN5

The server does boot, but it just shows this screen: https://i.sstatic.net/bpsZ9.png

I know Openshift only allows you to bind to port 8080, otherwise you have to bind to a private port in the range 15000 - 35530 (see this). However, I couldn't find any documentation on what ports Jenkins tries to bind or how to change the bindings, other than the main http (8080) and https (not used) ports.

(my jenkins cartridge URL - may not be running)

Any ideas as to what I should try?

Upvotes: 3

Views: 2931

Answers (1)

user2879327
user2879327

Reputation:

The config.xml (https://wiki.jenkins-ci.org/display/JENKINS/Administering+Jenkins) according to that page is stored in the JENKINS_HOME location, you need to create it there (along with any other configuration files that you need). You should be set with having set your JENKINS_HOME to a folder in your OPENSHIFT_DATA_DIR.

As for the port issue. You might check out the current Jenkins cartridge that OpenShift provides (https://github.com/openshift/origin-server/tree/master/cartridges/openshift-origin-cartridge-jenkins) and check out some of the configuration files they are using, or their startup commands and see if that information helps you get yours running.

Also, don't use export JENKINS_HOME=$OPENSHIFT_DATA_DIR/jenkins use this "rhc set-env " instead, it's much safer than exporting...

Upvotes: 3

Related Questions