Hi folks:
Thilina sez:
I tried to do a small commit and the built took forever to run. Atlast
Deepal came to my help and commited it for me.. But now I'll get
second thoughts whenever i need to commit something to Axis2 :(.
IMO These long and hard build times will cause a negative effect on
the contributions.. Specially from somebody like me, who don't have a
super druper machine..
+1
As we've discussed before, we should think about having various levels
of testing included in our available targets. This makes it feasible to
have interoperability testing included in our codebase, but not executed
when a user is offline, or making only small changes.
IMHO, we should have at least these levels:
Dev - just run unit tests, no serious integration tests. This should
essentially be a "sanity check" for quick development builds. Should
not include deep integration tests with complex extensions or big WSDLs.
This build should be kept, I'd like to hope, under 5 minutes on a
reasonable machine.
Normal - run most tests, including integration tests, but still no tests
which require a network connection for interop testing. This should be
the default, I think.
Interop - run everything including remote interop suite with public
endpoints from other vendors.
So while you're working you'd do "maven dev" to build jars and unit
test, then before checkin you'd make sure "maven jar" passed (the normal
tests), and every once in a while run "maven interop" (certainly before
dists, and hopefully on gump once a day).
Thoughts?
--Glen
