Continuous integration with pony-build

Registered by Stani on 2010-02-24

Integrate pony-build in Phatch (bzr support)

Blueprint information

Status:
Started
Approver:
Stani
Priority:
High
Drafter:
scherrey
Direction:
Approved
Assignee:
scherrey
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
None
Started by
Stani on 2010-02-24

Related branches

Sprints

Whiteboard

stani@scherrey (2010-03-07): Any updates?

scherry@stani - I'm back in BKK and getting caught up with work so no real progress unfortunately. I am extending my training course on TDD & Continuous Integration to incorporate pony-build so that is moving forward. Phatch has two other issues I need to resolve before we can get it going however. 1) bzr support for pony-build (shouldn't be too difficult), and 2) non-python dependencies which have fairly complex installer issues and this could be a tough nut to crack. Will likely have to pick one platform to start with (have a preference? i'm thinking linux/ubuntu) and then add more later. I do want to get this into Phatch because it will be an excellent proof of concept that pony-build is flexibly and mature enough to handle more complex requirements.

stani@scherry (2010-03-07): Great to hear from you! About ...
1) bzr support: I can't help you much with it. I guess people on #bzr or bzr mailing list might be interested.
2) "non-python dependencies which have fairly complex installer issues and this could be a tough nut to crack."
Which dependencies are these?
Phatch is very modular. So if you have Python and PIL installed (wxPython is not needed for the tests anyway as we don't do GUI testing), you can already do most tests. We can start with Python and PIL on Linux, and afterwards on Windows and Mac. Later I would start adding testing other dependencies (such as imagemagick, ...). On Ubuntu you would only need the phatch-cli package.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.