Re: [jboss-dev] Reminder Commit & Testing Policy
I've been experimenting with Git for a while and have tried to setup a
QA based commit policy like this
* Hudson QA runs of a public git-svn repo (1)
* I pull and push to a my public git repo (2)
* I work on multiple local git repos one for office one for home (3,4)
* (1) pulls from (2) and runs the QA
* If QA passes (1) commits to svn
* If QA doesn't pass, the pull is reverted
The idea is that I don't commit to SVN directly. Instead Hudson does
when the changes that it pulled in (from various repos) are ok.
I'll blog about when it proves useful and I get more experience with it.
cheers
-thomas
On 04/09/2010 08:10 PM, Jason T. Greene wrote:
This is just a friendly reminder that all minor commits (changes
unlikely to affect others) need to be ran through smoke-tests before
committing.
Everything else needs to have a full testsuite run *before* committing.
This can be done by either running it locally on your box, or you can
commit to a private branch and create a temporary hudson job.
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
JBoss OSGi Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx