Hi, On 17 October 2017 at 12:12, Robert Munteanu <[email protected]> wrote:
> On Tue, 2017-10-17 at 12:08 +0100, Ian Boston wrote: > > Hi, > > Could travis be used ? > > > > https://github.com/apache/sling/blob/trunk/.travis.yml > > > > I dont think that need personal access tokens or a special technical > > uses > > as it uses OAuth. > > > > From memory the main problem with Travis + Sling is a) the size of > > the log > > file (fixed for Sling see yml file) and b) the time taken to build. > > Other > > than that it works well for small repos that build fast. > > Travis requires administrative access to Github, which we don't have. > https://travis-ci.org/apache/sling/builds/288988140?utm_source=github_status&utm_medium=notification It seems to be active and working on apache/sling trunk I don't remember having administrative access to GitHub when making that work, but I guess perhaps, Infra had already enabled it. Enabling once per repo might be more attractive to Infra than having to manage 380+ special users, or perhaps thats the same thing. > We would need to ask infra to do this, and since they do it manually I > don't think it will be too high on their priority list. > > Are we missing features from Travis or is it just the ease of > configuration? > Ease of configuration (once you get past its output limits) Good integration with GitHub, especially pull requests. Doesn't consume Apache resources. (I assume) I've used both on other projects and generally found Travis less hassle than Jenkins, but thats only my experience. This has been especially true where I wanted to do a little more PR validation than a simple build. Best Regards Ian > > Thanks, > > Robert >
