On 06/04/2020 12:42, Cantor, Scott wrote:
On 4/6/20, 7:21 AM, "Roger Leigh" <rle...@codelibre.net> wrote:
You can simply push your feature branch and wait for the tests to pass before
merging to and pushing the integration
branch.
I'm not sure that there's been adequate discussion of any actual development
process for using git, or any policies put in place about how to deal with
feature branches.
But that aside are you saying every branch is automatically being built and
tested?
Hi Scott,
Yes, every GitHub branch update will trigger a CI run. This includes
all branch updates to GitBox since they are mirrored to GitHub. The
branch update can be by any possible means: direct push of a branch to
GitHub, indirectly via a push to GitBox, or opening/updating/merging a PR.
We had all this in place last year, but when we switched over to git,
the CI integrations (which belonged to the old mirror of the SVN
repository) were lost and needed re-enabling for the new repository.
It should be pretty simple for any Apache contributor to push any
potential update as a feature branch to GitBox and then check the CI run
passes, prior to merging to an integration branch. This will ensure
that no regressions should be present on an integration branch.
Regards,
Roger
---------------------------------------------------------------------
To unsubscribe, e-mail: c-dev-unsubscr...@xerces.apache.org
For additional commands, e-mail: c-dev-h...@xerces.apache.org
