openstack-ubuntu-testing team mailing list archive
Mailing list archive
Re: OpenStack Folsom packages
Thanks for the response. I'm investigating if it's feasible to converge the
Jenkins setup used by Ubuntu with the setup used internally by HP for
testing OpenStack. That way we could both leverage each other's work.
What do you think would be the best approach? Would it be straightforward
for me to replicate the same Jenkins setup you have? What are the
prerequisites to do that?
Once I have it working, I could modify the Jenkins scripts and parameterize
them, because we do certain things differently. Then, in theory, we would be
able to share the same scripts with different arguments.
I'm not sure if it's feasible to make that convergence, but I'd like to
investigate that option.
+44 117 31 29801 / Tel
aleksander.korzynski@xxxxxx / Email
Long Down Avenue
Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12
Registered No: 690597 England
The contents of this message and any attachments to it are confidential and
may be legally privileged. If you have received this message in error, you
should delete it from your system immediately and advise the sender.
To any recipient of this message within HP, unless otherwise stated you
should consider this message and attachments as "HP CONFIDENTIAL".
From: Adam Gandelman [mailto:adamg@xxxxxxxxxxxxx]
Sent: 15 August 2012 21:08
To: Korzynski, Aleksander
Subject: Re: [Openstack-ubuntu-testing] OpenStack Folsom packages
On 08/15/2012 06:17 AM, Korzynski, Aleksander wrote:
I'm setting an internal Nova Folsom build/release system for HP Cloud and
would like to ask if you can point to my some documentation as to how
Can you please explain what is the significance of the different archives
(Openstack Folsom Deps staging, Folsom Trunk Testing, Precise Trunk Testing)
and the branches on ubuntu-server-dev (nova/folsom, nova/quantal,
I've put together some basic docs that tries to cover our packaging
work-flow. Please see https://wiki.ubuntu.com/OpenStack/Packaging If you
still have questions, feel free to ask and I'll try to expand the wiki to
cover that as well.
Description: S/MIME cryptographic signature