| [...truncated 31139 lines...] |
| deleting and forgetting pool/main/n/nova/nova-volume_2013.1+git201211121232~precise-0ubuntu1_all.deb |
| deleting and forgetting pool/main/n/nova/nova-xcp-network_2013.1+git201211121232~precise-0ubuntu1_all.deb |
| deleting and forgetting pool/main/n/nova/nova-xcp-plugins_2013.1+git201211121232~precise-0ubuntu1_all.deb |
| deleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121232~precise-0ubuntu1_all.deb |
| deleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121232~precise-0ubuntu1_all.deb |
| INFO:root:Pushing changes back to bzr testing branch |
| DEBUG:root:['bzr', 'push', 'lp:~openstack-ubuntu-testing/nova/precise-grizzly'] |
| Pushed up to revision 402. |
| INFO:root:Storing current commit for next build: 9fbc478b5bb8d140d4154e472f81b3e76fe01040 |
| INFO:root:Complete command log: |
| INFO:root:Destroying schroot. |
| bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmp9qx0vi/nova |
| mk-build-deps -i -r -t apt-get -y /tmp/tmp9qx0vi/nova/debian/control |
| python setup.py sdist |
| git log -n1 --no-merges --pretty=format:%H |
| bzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --force |
| dch -b -D precise --newversion 2013.1+git201211121332~precise-0ubuntu1 Automated Ubuntu testing build: |
| dch -a No change rebuild. |
| debcommit |
| bzr builddeb -S -- -sa -us -uc |
| bzr builddeb -S -- -sa -us -uc |
| debsign -k9935ACDC nova_2013.1+git201211121332~precise-0ubuntu1_source.changes |
| sbuild -d precise-grizzly -n -A nova_2013.1+git201211121332~precise-0ubuntu1.dsc |
| dput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121332~precise-0ubuntu1_source.changes |
| reprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121332~precise-0ubuntu1_amd64.changes |
| bzr push lp:~openstack-ubuntu-testing/nova/precise-grizzly |
| + [ ! 0 ] |
| + jenkins-cli build precise_grizzly_deploy |
| No such job 'precise_grizzly_deploy' perhaps you meant 'precise_essex_deploy'? |
| java -jar jenkins-cli.jar build args... |
| Starts a build, and optionally waits for a completion. |
| Aside from general scripting use, this command can be |
| used to invoke another job from within a build of one job. |
| With the -s option, this command changes the exit code based on |
| the outcome of the build (exit code 0 indicates a success.) |
| With the -c option, a build will only run if there has been |
| an SCM change |
| JOB : Name of the job to build |
| -c : Check for SCM changes before starting the build, and if |
| there's no change, exit without doing a build |
| -p : Specify the build parameters in the key=value format. |
| -s : Wait until the completion/abortion of the command |
| --username VAL : User name to authenticate yourself to Jenkins |
| --password VAL : Password for authentication. Note that passing a |
| password in arguments is insecure. |
| --password-file VAL : File that contains the password |
| Build step 'Execute shell' marked build as failure |
| Email was triggered for: Failure |
| Sending email for trigger: Failure |
