[Openstack] Coalescing and Coordinating Continuous Integration, Developer Tools, Function and Smoke Testings Efforts

Joseph Heck joseph.heck at gmail.com
Tue Jun 7 18:45:41 UTC 2011


love it! Im good with the updated proposed meeting time - will miss it this week, but am looking forward to jumping in. 

- joe

On Jun 7, 2011, at 9:33 AM, Monty Taylor <mordred at inaugust.com> wrote:

> It has been pointed out that the hour before the openstack meeting
> belongs to PPB - so let's make that a proposal for 2 hours before
> #openstack-meeting.
> 
> On 06/07/2011 10:44 AM, Monty Taylor wrote:
>> Hey all!
>> 
>> It's time to both expand and contract some things around automation and
>> testing. Thusfar all of the work on Jenkins and Tarmac and other
>> 'official' build and testing automation has been done exclusively by
>> Soren and me, In the mean team, several people have been hacking on
>> projects that range from helpful to spectacular, and because of lack of
>> communication, only some of them are directly useful to the project's
>> infrastructure. I'd like to change this. Specificaly, I'd like to make
>> sure we can expand how we're working so that there is greater visibility
>> in to what/how we doing things in Jenkins land, and that the barrier to
>> entry to helping out isn't terrible. And I'd like to contract the number
>> of unrelated efforts in to something resembling a plan.
>> 
>> a) I'm working on geting relevant bits from our jenkins into to VC
>> somewhere so that it's easier for us all to collaborate. I'm using the
>> launchpad.net/openstack-ci project for that.
>> 
>> b) I configured the OpenStack Jenkins to use Launchpad's OpenID provider
>> as a SSO source - so now I can use Launchpad teams to manage who can do
>> what on Jenkins - which means better federation of that management.
>> 
>> c) I want to set up a regular (say weekly) IRC meeting for everyone
>> interested in CI, dev tools and functional/smoke testing. (although for
>> sake of sanity, lets keep "interested" to be "interested in working on"
>> I was thinking perhaps the hour right before the normal openstack one...
>> anybody have strong thoughts? Of the topics/actions to be discussed are
>> managing/moving forward with the current work on the testing
>> infrastructure, and having discussions about how/if various work by
>> folks can be leveraged by the Jenkins that is the gatekeeper over
>> openstack branches.
>> 
>> d) Make sure people know what we're doing over here in OpenStack
>> CI/Tools land, so that they are aware of the tools already present so
>> that they don't duplicate effort, and also of the current todo list in
>> case anyone wants to help. Our Jenkins already does several things that
>> it turns out nobody knows about. That's gotta get fixed. (Speaking of-
>> if there's any Java folks laying around out there sick of all the
>> python, there are a couple of tasks that can use love - more to come on
>> that)
>> 
>> The meeting should be simple this time around - I propose meeting the
>> hour before the openstack meeting, starting next week. I don't think we
>> really need a separate mailing list, but I'm open to opinions... Also,
>> in the mean time, ping me back and let me know if you're wanting to be
>> part of this.
>> 
>> Thanks!
>> Monty
>> 
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp




More information about the Openstack mailing list