FAQs on Jenkins Adapter

This section provides solutions to common issues with the Jenkins adapter.

How do I get the queue server hostname and credentials? I need it to set up my adapter.

Adapters use a message queue server to transmit data to TeamForge EventQ. Adapters must therefore be configured with the queue server hostname, username, and password.
When you create a new “Source” in TeamForge EventQ, a unique set of queue server credentials is created for use with your adapters. To create a Source and obtain queue server hostname and credentials, see the Manage Build Source documentation.
Note that the same queue server hostname, username and password may be shared by multiple sources; however, the source association must be unique for each source.

My build is marked “Unstable”

Builds are marked “Unstable” if the Jenkins system configuration has not been saved and the Jenkins adapter cannot successfully communicate with TeamForge EventQ or the message queue. The console output for the build will include a message like this:
Build information NOT sent: plug-in needs a Jenkins URL

Workaround: As a privileged Jenkins user, navigate to Manage Jenkins > Configure System and populate and save the required configuration.

Automated test results for my Jenkins builds are not showing in TeamForge EventQ

TeamForge EventQ relies on Jenkins to supply automated test results. Jenkins has a post-build action called “Publish JUnit test result report” which must be activated for test results to show up in TeamForge EventQ, regardless of whether JUnit is actually used.
Workaround: To enable this configuration, add the Publish JUnit test result report post-build action to the desired Jenkins job configuration.

If Jenkins runs along with any other applications such as TeamForge and JIRA on the same server, this error occurs. Hence, it is recommended to install Jenkins on a separate server. If you have installed Jenkins on the same server where other applications are installed as well, make sure that you host Jenkins on Tomcat to get rid of this issue. To know how to host Jenkins on Tomcat, check this wiki page: https://wiki.jenkins-ci.org/display/JENKINS/Tomcat.

Unable to embed Jenkins page into an iframe. How to fix it?

From the Jenkins version 1.532 and later, the Jenkins page is not displayed in an iframe.

Do you need a way to permit Jenkins to be visible in selected iframes? Here you go.

To configure X-Frame-Options:

If you try to load content into an iframe and the X-Frame-Options header is set to SAMEORIGIN, then the content loading is prevented. To override the default X-Frame-Options header settings, you have to perform the following:

You need to have the Jenkins plugin installed to configure the X-Frame-Options. You can download the plugin from https://wiki.jenkins-ci.org/display/JENKINS/XFrame+Filter+Plugin.

You must have Jenkins administrative privileges to do this. On the Jenkins Configuration page, in the XFrame Filter Configuration section, enter the value for X-Frame-Options Options as ALLOW-FROM <ctf domain name>.

For example, on the http://jenkins.maa.relenghub.collab.net/jenkins/configure page, enter ALLOW-FROM http://forge.collab.net for X-Frame-Options Options.

Now, the page can only be displayed in a frame on the specified origin.