Thursday, June 24, 2010

PYTI report #3

Hello All,

The other week i didn't have time to write in the blog it's my last year in my school and it's the period of last exams so i was very busy preparing, i still have to do some stuff for my school until this Saturday, but here what i was doing for PYTI when i did have time for it.


Now i'm working on changing the database layer because when i first ran the pony-build test i did have some problem with one of them and because i'm using postgresql to save packages i have to change the database layer of pony that support only sqlite and i think that it's the problem for not having test succed, so
i want to make sure that all tests passed before adding something to pony-buid.

So first thing when i will finish the database layer and if all test pass i will start with the ec2 interface, i will make first a prototype because in the first i wanted to change the pony-build structure to make it more modular so that the pony-build interface can be just a module that you can enable but now i think that i'm late from my initial schedule and i didn't start yet the virtual machine part and i already discuss with Titus about my ideas for the pony-build and like he said maybe it's better to make it work first with necessary and minimal change then trying to change or add other functionalities.


http://bitbucket.org/mouad/pypi-testing-infrastructure-pyti

Thursday, June 10, 2010

GSOC second meeting: PYPI Testing Infrastructure

After finishing the first steps of the web interface, now i have to integrate the web interface with the pony-build server.

For that matter pony-build have a wsgi interface that i'm trying to use but with some difficulties, hopefully i will overpass.

Also i'm thinking about a way to use the coordinator.py (API for pony-build) using an adapter pattern to interface the django application with the pony server , i'm thinking about changing the database layer because dealing with two databases will be useless (pony build work only with sqlite).

Finally i'm thinking also about making pony-build configurable by adding a configuration file where you can define the database, choose the web interface , choose the notification way ....

this week was my first real contact with pony-build and i think that it's a very good project, with a lot of documentation, and testing (so that i can play with it safely)


To close this post i will display the first screen shot of the web interface that i spend the last weeks doing, it's still need some work and every comment is welcome.

- login page support "openid" from different account like shown in the picture, i think the openid must be optional that user can disable (i'm talking about running the web interface locally)
- After the authentication the user are redirect to a page where he can see his package with some information like the last build date, the status of the package (the status of the last build) , and he can choose from the tool bar above the action that he want to do like configure the server, see package detail , build package




You can follow as on this link for more information :
http://bitbucket.org/mouad/pypi-testing-infrastructure-pyti






Thursday, June 3, 2010

GSOC first meeting : PyPI Testing Infrastructure (PYTI)

Hello all,

This my second post in this bloc and my first for the GSOC project : PYPI Testing Infrastructure (PYTI).

The project for the ones that don't know it is about creating a testing infrastructure to test packages that get upload it to PYPI check this link for more information .

For that matter we chose to work with pony-build as the continuous integrating system that will let us run the test in an EC2 machines that run on different platform (linux, windows, unix ...), and as an user interface, we chose to build a web interface with Django that will let the user :
  • build his own packages in the platform of his choice .
  • see build report with some other stuff related to the build like a time-line of build ...
  • every user must have an account in PYTI where he can enable some feature like a notification system for the build , schedule build to be run ...
In this first two weeks i was creating a prototype of the Web interface , now i'm adding some feature on it ,i hope that i will finish this week i will publish some screenshot as soon as i have something ready.

For the next days of this week i have to much task to do :
  • write a help of how using PYTI.
  • interface pony-build with the web interface that we created.
  • automatize the installation of the web interface .
  • add some feature to the Web interface
for the ones that are interested you can follow us on this link.