[...truncated 31205 lines...] |
deleting and forgetting pool/main/n/nova/nova-xvpvncproxy_2013.1+git201211121633~precise-0ubuntu1_all.deb |
deleting and forgetting pool/main/n/nova/python-nova_2013.1+git201211121633~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: 6615b32983ad6c708b795c5ded4cd974a814d327 |
INFO:root:Complete command log: |
INFO:root:Destroying schroot. |
bzr branch lp:~openstack-ubuntu-testing/nova/precise-grizzly-proposed /tmp/tmpCzbGYz/nova |
mk-build-deps -i -r -t apt-get -y /tmp/tmpCzbGYz/nova/debian/control |
python setup.py sdist |
git log -n1 --no-merges --pretty=format:%H |
git log 9471282626e004296351a4a97fb51209a53e7f42..HEAD --no-merges --pretty=format:[%h] %s |
bzr merge lp:~openstack-ubuntu-testing/nova/precise-grizzly --force |
dch -b -D precise --newversion 2013.1+git201211121702~precise-0ubuntu1 Automated Ubuntu testing build: |
dch -a [6615b32] Fix a bug in XenAPISession's use of virtapi |
dch -a [d6d0a67] Add missing webob to exc |
dch -a [9ff6819] Fix getattr usage |
debcommit |
bzr builddeb -S -- -sa -us -uc |
bzr builddeb -S -- -sa -us -uc |
debsign -k9935ACDC nova_2013.1+git201211121702~precise-0ubuntu1_source.changes |
sbuild -d precise-grizzly -n -A nova_2013.1+git201211121702~precise-0ubuntu1.dsc |
dput ppa:openstack-ubuntu-testing/grizzly-trunk-testing nova_2013.1+git201211121702~precise-0ubuntu1_source.changes |
reprepro --waitforlock 10 -Vb /var/lib/jenkins/www/apt include precise-grizzly nova_2013.1+git201211121702~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 'raring_grizzly_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 |