See <https://ci.centos.org/job/libvirt-go-build/systems=libvirt-debian-9/873/display/redirect?page=changes>

Changes:

[berrange] Add TLS destination parameter

[berrange] Add support for new job constants related to backups

[berrange] Add new domain backup APIs

------------------------------------------
Started by upstream project "libvirt-go-build" build number 873
originally caused by:
 Started by an SCM change
Running as SYSTEM
[EnvInject] - Loading node environment variables.
Building remotely on libvirt-debian-9 (libvirt) in workspace <https://ci.centos.org/job/libvirt-go-build/systems=libvirt-debian-9/ws/>
No credentials specified
 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url https://github.com/libvirt/libvirt-go.git # timeout=10
Fetching upstream changes from https://github.com/libvirt/libvirt-go.git
 > git --version # timeout=10
 > git fetch --tags --progress https://github.com/libvirt/libvirt-go.git +refs/heads/*:refs/remotes/origin/*
Checking out Revision ff5efd4cc9f5bf13563f49fd839aff4cfde3281f (refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f ff5efd4cc9f5bf13563f49fd839aff4cfde3281f
Commit message: "Add new domain backup APIs"
 > git rev-list --no-walk 5bc4a9e05e437e78affebd92d823a78fbc277f47 # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
[libvirt-go] $ /bin/sh -xe /tmp/jenkins3775764934420630539.sh
+ go build -v
_<https://ci.centos.org/job/libvirt-go-build/systems=libvirt-debian-9/ws/>
# _<https://ci.centos.org/job/libvirt-go-build/systems=libvirt-debian-9/ws/>
./domain_wrapper.go: In function ‘virDomainBackupGetXMLDescWrapper’:
./domain_wrapper.go:2466:16: error: ‘NULL’ undeclared (first use in this function)
     if (ret == NULL) {
                ^~~~
./domain_wrapper.go:2466:16: note: each undeclared identifier is reported only once for each function it appears in
Build step 'Execute shell' marked build as failure