At Aries we are also still investigating if it makes sense to actually use travis. I just wanted to announce that it is possible now if you also want to experiment.
What I like in travis and even more in circle ci is that you can define the whole build in your source repo. There is nothing to set up on the build server. Circle ci even allows to define a docker image where your code is built. So you can install whatever build tools you need. I noticed that the sling modules already use jenkins pipeline jobs. So I guess most these advantages (compare to old style jenkiona) are already present in the current builds. Christian Am Mi., 24. Apr. 2019 um 11:20 Uhr schrieb Radu Cotescu <[email protected]>: > Hi Christian, > > > On 24 Apr 2019, at 10:32, Christian Schneider <[email protected]> > wrote: > > > > I just found that apache infra can enable travis integration on request. > > > > I just enabled this for Aries: > > https://issues.apache.org/jira/browse/INFRA-18131 > > > > See here for an example: > > https://travis-ci.org/apache/aries-journaled-events > > > > Would this be interesting for sling? > > > > Cheers, > > Christian > > Sling’s modules are already built on ASF’s Jenkins server [0] and there’s > as well a SonarCloud integration [1][2]. I’m not sure what other features a > TravisCI integration would bring. > > Cheers, > Radu > > [0] - https://builds.apache.org/view/All/job/Sling/ < > https://builds.apache.org/view/All/job/Sling/> > [1] - https://sonarcloud.io/organizations/apache/projects < > https://sonarcloud.io/organizations/apache/projects> > [2] - > https://cwiki.apache.org/confluence/display/SLING/SonarCloud+analysis < > https://cwiki.apache.org/confluence/display/SLING/SonarCloud+analysis> > > -- -- Christian Schneider http://www.liquid-reality.de Computer Scientist http://www.adobe.com
