Howdy,
Let's say Alice has a parrot branch called "foozbar" that is ready for smoking.
Assuming Alice is already on her "foozbar" branch:
git checkout -b smoke-me/foozbar
git push origin smoke-me/foozbar
If all the commits in "foozbar" were already on the server, pushing a new
branch will not trigger the smoking mechanism. A new commit must be added.
A simple way to trigger this is to update NEWS/api.yaml or some other file that
surely needs some love. The next *new* commit that is pushed to
smoke-me/foozbar will trigger a build and test run by Jitterbug, which is
viewable currently at http://new.leto.net:3000 .
My next goal is to have nqp-rx built + tested as each new parrot commit
happens, then other HLLs when that works. This will require adding some
features to Jitterbug.
PS: Currently, "smoking" in Jitterbug means running the tests and emailing on
failures. Smolder reports are not being generated, but I think that could be
added if that is a feature people want.
Duke
--
Jonathan "Duke" Leto
[email protected]
http://leto.net
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
