← Back to team overview

openstack team mailing list archive

Re: Coalescing and Coordinating Continuous Integration, Developer Tools, Function and Smoke Testings Efforts

 

Just for verification, this testing meeting is scheduled for 12pm Pacfiic on
Tuesdays? I just added http://tinyurl.com/openstack-meetings to my calendar
and it appears to be scheduled for 2pm Pacific on Tuesdays. The PPB meeting
appears to have last been on a Thursday and has no other scheduled
instances...

--andy

On Tue, Jun 7, 2011 at 1:09 PM, Monty Taylor <mordred@xxxxxxxxxxxx> wrote:

> On 06/07/2011 02:52 PM, Andy Smith wrote:
> >
> >
> > On Tue, Jun 7, 2011 at 8:44 AM, Monty Taylor <mordred@xxxxxxxxxxxx
> > <mailto:mordred@xxxxxxxxxxxx>> 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 <http://launchpad.net/openstack-ci>
> >     project for that.
> >
> >
> > Would you like to check in the various configs I sent you from the anso
> > setups, should I propose that merge, or do you think that this is not
> > the proper place for jenkins configs + testing scripts?
>
> I can stick them in or you can. I'm not particularly thrilled with the
> jenkins config.xml + version control story at the moment. (although I
> did add the config history plugin so that we're not just constantly
> overwriting that stuff through the web) (if you stick them in, shove
> them in a subfolder or something- I've currently checking the
> openstack-ci branch out straight in to the jenkins root.
>
> >
> >     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.
> >
> >
> > Yay for no longer having manual config there :)
>
> zomg. you're not kidding.
>
> >     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.
> >
> >
> > I suppose I should be on that list.
>
> Done. Thanks!
>
> >     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@xxxxxxxxxxxxxxxxxxx
> >     <mailto:openstack@xxxxxxxxxxxxxxxxxxx>
> >     Unsubscribe : https://launchpad.net/~openstack
> >     More help   : https://help.launchpad.net/ListHelp
> >
> >
>

Follow ups

References