I think any CI system can do publish. the only thing is how to manage the secret we use in third party CI system.
Travis CI has a document related to this https://docs.travis-ci.com/user/best-practices-security/ On 2018/08/23 19:59:44, Mark Thomas <[email protected]> wrote: > On 23/08/18 11:26, Huxing Zhang wrote: > > Hi, > > > > On Thu, Aug 23, 2018 at 12:54 PM Ian Luo <[email protected]> wrote: > >> > >> I'm not quite sure if it's done, but what I suggest is, if it's not done > >> yet, we should consider to add instruction in .travis.yaml to publish all > >> artifacts to snapshot repository every time when CI passes, to make > >> everyone's life easier. > > > > I think we should publish the snapshot to Apache repository[1] for 2.7.x. > > I am afraid that it could not be done automatically if we are using > > third party CI system like travis. > > Maybe we can use any of the Apache CI system[3] in order to publish > > the snapshot. > > I'm sure you can. Tomcat does this from buildbot but I'd be surprised if > you couldn't do it from any of the CI systems. > > As an aside, Tomcat has seen the benefit of using multiple CI systems as > a failing test found by one CI system often passes on another. It might > be viewed as 'old school' by Apache Gump has been particularly good at > finding issues. > > Mark >
