The problem really is what we want to enter in the pom.xmls. That information is used for the regular maven release process and this is where the commits are pushed to during the release. Only one repository url is supported there. The information is not used for the actual CI builds, so for the Jenkins we can still decide which one to use independent of the scm information in the pom.xml.
But Robert's argument regarding what happens in case of parallel conflicting commits to both Github and gitbox is a very valid one. I think as long as the ASF is fine with this I would also rather promote the usage of Github instead of gitbox (because of its richer feature set) and therefore I am finally convinced that entering the Github SCM URL is fine there. Konrad > On 10. Oct 2017, at 11:38, Bertrand Delacretaz <[email protected]> wrote: > > On Mon, Oct 9, 2017 at 7:58 PM, Chetan Mehrotra > <[email protected]> wrote: >> ...I believe Github would provide more convenience and if dual system is >> approved then we should use Github as the preferred master... > > +1 but can we run tests and build releases from the ASF repositories? > The goal being to make sure those are the "golden" ones. > > -Bertrand
