jenkins-job-builder/tests/hipchat/fixtures/hipchat004.xml
Darragh Bailey dc464d943f Ensure tests run with ConfigParser object
Should always use a ConfigParser object when testing to allow unit tests
to check that calls behave as expected.

Read in the default configuration to align with expected usage, and fix
some issues caused by usage of dicts resulting in the option name
requested being taken as the default value.

Since '.get()' is a valid method for a dictionary object, take care to
ensure that we do not use a dummy dict object as this will not throw the
expected errors if a config file is not provided and will also treat the
option name as a default value resulting in the wrong data appearing in
the outputted XML.

Change-Id: I6abb85f0363a48f220914c52b74e5a5fb65b0faa
2015-08-11 16:36:08 +01:00

24 lines
826 B
XML

<?xml version="1.0" encoding="utf-8"?>
<project>
<properties>
<jenkins.plugins.hipchat.HipChatNotifier_-HipChatJobProperty>
<room/>
<startNotification>true</startNotification>
<notifySuccess>false</notifySuccess>
<notifyAborted>false</notifyAborted>
<notifyNotBuilt>false</notifyNotBuilt>
<notifyUnstable>false</notifyUnstable>
<notifyFailure>false</notifyFailure>
<notifyBackToNormal>false</notifyBackToNormal>
</jenkins.plugins.hipchat.HipChatNotifier_-HipChatJobProperty>
</properties>
<publishers>
<jenkins.plugins.hipchat.HipChatNotifier>
<buildServerUrl>http://localhost:8080/</buildServerUrl>
<sendAs>Jenkins</sendAs>
<authToken>dummy</authToken>
<room/>
</jenkins.plugins.hipchat.HipChatNotifier>
</publishers>
</project>