You may encounter these problems when using 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 Orchestrate.
Adapters must therefore be configured with the queue server hostname, username, and password.
- When you create a new "Source" in TeamForge Orchestrate, a unique set of queue server credentials
is created for use with your adapters. To find the queue server hostname and credentials, log into
TeamForge as a privileged Orchestrate user and navigate to:
- Locate the section named "Adapter Configuration Information".
- Copy the queue server's hostname, username, and password and use them to configure
your adapter.
- 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 Orchestrate 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 and populate and save the required configuration.
- Automated test results for my Jenkins builds are not showing in TeamForge Orchestrate
- TeamForge Orchestrate 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 Orchestrate, 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.