[petsc-dev] does next model mess up our histories

[Jed Brown]

Satish Balay <balay at mcs.anl.gov> writes:
> I guess another alternative for these veryfew feature branches
> that need to iterate over nightlytest suites is:
>
> - never merge feature branch to next untile its complete
> - switch master or next nightlytest to feature branch [for a few days]
> - fix rebase feature branch as needed.

If we had a continuous integration system, the mere act of creating a
pull request could spawn the builds on many architectures and give us
the results.  MOOSE does this with moosebuild and a zillion project do
it with Travis-CI, Jenkins, etc.

It would be useful, but requires test system improvements.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20141002/6e1a663e/attachment.sig>