pony-build Updates

Khushboo:

Khushboo has been wrestling with git and getting her branch(s) to push properly.  Some very informative posts can be found on her blog. She also continues creating build scripts for other python packages.

Fatima:

Fatima has been working on getting branch support in for Mecurial checkouts in pony-build, to go along with the new changes, she has also been working on tests. You can read up on all her research into the subject as well as her progress over at her blog.

Jack:

Jack has been continuing his work on his pony-client changes. During his work on this he stumbled onto another bug with forcing builds that he is looking in to also.

Max:

Max has implemented a fix for defaulting to an in-memory db for the server. He has also been working on some failure conditions within build steps under a certain context. He,however, has taken a break from the perils of subprocess timeouts until he can secure a windows machine for proper testing. You can mozy on over to his blog for more info.

Edit: When is pony-build going to get some love and have our own Category?

Max’s Midway Update

Here is where you can find my thoughts on all this UCOSP and pony-build stuff so far.

Indentation….Serious Business

The pony-build team just had our weekly meeting the other night and the following is what people have been working on:

1) Jack has been working on some command line stuff. You can follow his thread here, for descriptions of his changes as well as what he is planning to tackle next.

2) Fatima has been working on getting her coverage build script finished up and working, as well as refining the HgClone implementation in the pony-build client. You can follow along on her progress here, which is a great post on never giving up. The following thread all so pertains to her work on HgClone. Following.

3) Khushboo has been working on refining and finishing up her nose pony-build build script. See the following two posts on her blog for more info here and here.

4) I have finished up some automatic folder creation stuff for GitClone and started to work on some things with virtualenv support. You can follow the cach_dir stuff here. The following thread covers some discussion on the virtualenv stuff–thread. Also see the following blog posts for more info on these items. Post 1 and Post 2.

Getting up to speed with Pony-Build

Since we couldn’t all meet for the Sprint code in Toronto, the first steps into pony-build were to get to speed with the software layout and with working with Git. We were constantly communicating via Skype and our group lead Pr. Titus was very patient and helpful throughout the process.

We first got the software running on Linux via Lyorn then on our own computer (on Windows and Mac). Then our next task was to write one of the client scripts for existing packages, commit it, and push it to Github.  We had the option to adapt existing scripts to build our own package.

The build commands are usually individual to each package, so our next task is to make sure the build scripts actually build and report to the central server as expected.

Being in the pony-build team is a continuous learning experience that I’m enjoying everyday more and more.

The pony-build Express

As the dust settles from this years Spring Code Sprint, I am left with some interesting reflections. One, coding for 9 hours straight sure gets hard without proper caffeine intake, maybe an IV drip will be a good investment for the next one. Two, ordering lots of food when someone else is paying is lots of fun, even if you end up walking (waddling?) out with some of it in a bag. Three, you can never have a shortage of computer related jokes or quips with rooms full of CSC majors.

The only sad part of my Sprint experience was that my group was unable to make it up to Toronto. Luckily for us Al Gore was able to invent the internet, so no matter how far apart people are we can get stuff going. With Titus, our fearless leader, at the helm we quickly got the ball rolling.

• We where able to get the remote group members setup and running pony-build.
• We cleaned up and implemented the virtualenv support for build recipes.
• We began work on some other improvements and bug fixes.

My work at the Code sprint was on getting virtualenv support working properly and working on this issue. All and all it was a fairly successful two days. Since pony-build is in such an early alpha state, our team will pretty much be able to mold it however we want. I am looking forward to working on this project throughout the semester and seeing where we can take it.