Great question/comment! I always look forward to this part with new podlings.
On Sat, Mar 28, 2015 at 5:32 PM Peter Ansell <[email protected]> wrote: > That is fine with me. > > I am not overly fascinated by internal Apache infrastructure though so > I would like to keep the .travis.yml file and the references to > coveralls if possible as there is nothing broken with that system > right now for CI and code coverage. > It's weird that you feel this way (from my point of view). Part of why projects seek out the ASF is to leverage the infrastructure in place that's provided. It's generally expected that the in house services will be leveraged. http://www.apache.org/dev/services.html I would expect that projects that come in through the incubator will leverage the ASF Jenkins instances over external builders. It's fine to have external builders, but the official CI for the project would be ASF Jenkins. For example, Travis can't deploy to the nexus instances for snapshots. > > Thanks, > > Peter > > John > > On 28 March 2015 at 23:12, John D. Ament <[email protected]> wrote: > > Unless anyone sees any issues with it, I'd like to enable Jenkins builds > > for CommonsRDF. > > > > Let me know. > > > > John >
