You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sling.apache.org by Christian Schneider <ch...@die-schneider.net> on 2019/04/24 08:32:36 UTC

Travis builds for sling?

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

-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: Travis builds for sling?

Posted by Konrad Windszus <ko...@gmx.de>.

If you consider doing this, please take the tiny URL of the Confluence page as this it the only stable one.
Konrad

> Am 02.07.2019 um 14:06 schrieb Robert Munteanu <ro...@apache.org>:
> 
>> On Thu, 2019-04-25 at 10:10 +0200, Christian Schneider wrote:
>> Many thanks. That helps a lot. Maybe that wiki should be linked from
>> the
>> JenkinsFiles so people have an easier time to understand that concept
>> and
>> how to tweak it.
>> 
> 
> Yes, we could. Note however that we have hundreds of Jenkinsfiles to
> patch like this :-)
> 
> If you feel lucky you can try and apply the changes yourself, something
> like:
> 
> - generate patch file
> - apply patch file to all repos
> - commit all repos
> - push all repos
> 
> should work. For running commands on top of all repositories you can
> use
> 
> $ repo forall -c "$COMMAND"
> 
> Robert
> 
>> Christian
>> 
>> Am Mi., 24. Apr. 2019 um 17:39 Uhr schrieb Konrad Windszus <
>> konrad_w@gmx.de
>>> :
>>> Hi Christian,
>>> this is explained in
>>> https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
>>> <
>>> https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup>;.
>>> Konrad
>>> 
>>>> On 24. Apr 2019, at 17:31, Christian Schneider <
>>>> chris@die-schneider.net>
>>> wrote:
>>>> I also saw these single line Jenkinsfiles. They are super
>>>> convenient as
>>>> long as your build has no specialities .. but I would have no
>>>> clue what
>>> to
>>>> do if my build is different.
>>>> 
>>>> Btw. How do they work? The Jenkinsfile does not refer to any
>>>> library or
>>>> similar .. so the build does not seem to be fully described by
>>>> the source
>>>> repo. Is this defined in the jenkins build on the server?
>>>> 
>>>> Christian
>>>> 
>>>> 
>>>> Am Mi., 24. Apr. 2019 um 16:44 Uhr schrieb Robert Munteanu <
>>>> rombert@apache.org>:
>>>> 
>>>>>> On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
>>>>>> s/jenkiona/jenkins/ :-)
>>>>> 
>>>>> I like Jenkiona :-)
>>>>> 
>>>>> Other that that - you're right, with the pipeline-based builds
>>>>> we
>>>>> already have the 'build as a code' set up that Travis promises.
>>>>> 
>>>>> Additionally, we are able to have a 'marker' Jenkinsfile of one
>>>>> line (
>>>>> well, +18 of license :-) ) for each repo, which makes the
>>>>> management of
>>>>> builds much much simpler. I would not like to see 300
>>>>> .travis.yml files
>>>>> duplicated across the Sling repos.
>>>>> 
>>>>> Of course, I for one am always open to the option to moving to
>>>>> some
>>>>> other CI platform, granted that it provides tangible benefits
>>>>> over the
>>>>> current setup.
>>>>> 
>>>>> Thanks,
>>>>> 
>>>>> Robert
>>>>> 
>>>>>> Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian
>>>>>> Schneider <
>>>>>> chris@die-schneider.net>:
>>>>>> 
>>>>>>> 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 <
>>>>>>> radu@apache.org>:
>>>>>>> 
>>>>>>>> Hi Christian,
>>>>>>>> 
>>>>>>>>> On 24 Apr 2019, at 10:32, Christian Schneider <
>>>>>>>>> chris@die-schneider.net>
>>>>>>>> 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
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> --
>>>> 
>>>> --
>>>> --
>>>> Christian Schneider
>>>> http://www.liquid-reality.de
>>>> 
>>>> Computer Scientist
>>>> http://www.adobe.com
>> 
>> -- 
>

Re: Travis builds for sling?

Posted by Robert Munteanu <ro...@apache.org>.

On Thu, 2019-04-25 at 10:10 +0200, Christian Schneider wrote:
> Many thanks. That helps a lot. Maybe that wiki should be linked from
> the
> JenkinsFiles so people have an easier time to understand that concept
> and
> how to tweak it.
> 

Yes, we could. Note however that we have hundreds of Jenkinsfiles to
patch like this :-)

If you feel lucky you can try and apply the changes yourself, something
like:

- generate patch file
- apply patch file to all repos
- commit all repos
- push all repos

should work. For running commands on top of all repositories you can
use

$ repo forall -c "$COMMAND"

Robert

> Christian
> 
> Am Mi., 24. Apr. 2019 um 17:39 Uhr schrieb Konrad Windszus <
> konrad_w@gmx.de
> > :
> > Hi Christian,
> > this is explained in
> > https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup
> > <
> > https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup>;.
> > Konrad
> > 
> > > On 24. Apr 2019, at 17:31, Christian Schneider <
> > > chris@die-schneider.net>
> > wrote:
> > > I also saw these single line Jenkinsfiles. They are super
> > > convenient as
> > > long as your build has no specialities .. but I would have no
> > > clue what
> > to
> > > do if my build is different.
> > > 
> > > Btw. How do they work? The Jenkinsfile does not refer to any
> > > library or
> > > similar .. so the build does not seem to be fully described by
> > > the source
> > > repo. Is this defined in the jenkins build on the server?
> > > 
> > > Christian
> > > 
> > > 
> > > Am Mi., 24. Apr. 2019 um 16:44 Uhr schrieb Robert Munteanu <
> > > rombert@apache.org>:
> > > 
> > > > On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
> > > > > s/jenkiona/jenkins/ :-)
> > > > 
> > > > I like Jenkiona :-)
> > > > 
> > > > Other that that - you're right, with the pipeline-based builds
> > > > we
> > > > already have the 'build as a code' set up that Travis promises.
> > > > 
> > > > Additionally, we are able to have a 'marker' Jenkinsfile of one
> > > > line (
> > > > well, +18 of license :-) ) for each repo, which makes the
> > > > management of
> > > > builds much much simpler. I would not like to see 300
> > > > .travis.yml files
> > > > duplicated across the Sling repos.
> > > > 
> > > > Of course, I for one am always open to the option to moving to
> > > > some
> > > > other CI platform, granted that it provides tangible benefits
> > > > over the
> > > > current setup.
> > > > 
> > > > Thanks,
> > > > 
> > > > Robert
> > > > 
> > > > > Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian
> > > > > Schneider <
> > > > > chris@die-schneider.net>:
> > > > > 
> > > > > > 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 <
> > > > > > radu@apache.org>:
> > > > > > 
> > > > > > > Hi Christian,
> > > > > > > 
> > > > > > > > On 24 Apr 2019, at 10:32, Christian Schneider <
> > > > > > > > chris@die-schneider.net>
> > > > > > > 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
> > > > > > 
> > > > > > 
> > > > > 
> > > > > --
> > > 
> > > --
> > > --
> > > Christian Schneider
> > > http://www.liquid-reality.de
> > > 
> > > Computer Scientist
> > > http://www.adobe.com
> 
> --

Re: Travis builds for sling?

Posted by Christian Schneider <ch...@die-schneider.net>.

Many thanks. That helps a lot. Maybe that wiki should be linked from the
JenkinsFiles so people have an easier time to understand that concept and
how to tweak it.

Christian

Am Mi., 24. Apr. 2019 um 17:39 Uhr schrieb Konrad Windszus <konrad_w@gmx.de
>:

> Hi Christian,
> this is explained in
> https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup <
> https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup>.
> Konrad
>
> > On 24. Apr 2019, at 17:31, Christian Schneider <ch...@die-schneider.net>
> wrote:
> >
> > I also saw these single line Jenkinsfiles. They are super convenient as
> > long as your build has no specialities .. but I would have no clue what
> to
> > do if my build is different.
> >
> > Btw. How do they work? The Jenkinsfile does not refer to any library or
> > similar .. so the build does not seem to be fully described by the source
> > repo. Is this defined in the jenkins build on the server?
> >
> > Christian
> >
> >
> > Am Mi., 24. Apr. 2019 um 16:44 Uhr schrieb Robert Munteanu <
> > rombert@apache.org>:
> >
> >> On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
> >>> s/jenkiona/jenkins/ :-)
> >>
> >> I like Jenkiona :-)
> >>
> >> Other that that - you're right, with the pipeline-based builds we
> >> already have the 'build as a code' set up that Travis promises.
> >>
> >> Additionally, we are able to have a 'marker' Jenkinsfile of one line (
> >> well, +18 of license :-) ) for each repo, which makes the management of
> >> builds much much simpler. I would not like to see 300 .travis.yml files
> >> duplicated across the Sling repos.
> >>
> >> Of course, I for one am always open to the option to moving to some
> >> other CI platform, granted that it provides tangible benefits over the
> >> current setup.
> >>
> >> Thanks,
> >>
> >> Robert
> >>
> >>>
> >>> Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian Schneider <
> >>> chris@die-schneider.net>:
> >>>
> >>>> 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 <
> >>>> radu@apache.org>:
> >>>>
> >>>>> Hi Christian,
> >>>>>
> >>>>>> On 24 Apr 2019, at 10:32, Christian Schneider <
> >>>>>> chris@die-schneider.net>
> >>>>> 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
> >>>>
> >>>>
> >>>
> >>> --
> >>
> >>
> >
> > --
> > --
> > Christian Schneider
> > http://www.liquid-reality.de
> >
> > Computer Scientist
> > http://www.adobe.com
>
>

-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: Travis builds for sling?

Posted by Konrad Windszus <ko...@gmx.de>.

Hi Christian,
this is explained in https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup <https://cwiki.apache.org/confluence/display/SLING/Sling+Jenkins+Setup>.
Konrad

> On 24. Apr 2019, at 17:31, Christian Schneider <ch...@die-schneider.net> wrote:
> 
> I also saw these single line Jenkinsfiles. They are super convenient as
> long as your build has no specialities .. but I would have no clue what to
> do if my build is different.
> 
> Btw. How do they work? The Jenkinsfile does not refer to any library or
> similar .. so the build does not seem to be fully described by the source
> repo. Is this defined in the jenkins build on the server?
> 
> Christian
> 
> 
> Am Mi., 24. Apr. 2019 um 16:44 Uhr schrieb Robert Munteanu <
> rombert@apache.org>:
> 
>> On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
>>> s/jenkiona/jenkins/ :-)
>> 
>> I like Jenkiona :-)
>> 
>> Other that that - you're right, with the pipeline-based builds we
>> already have the 'build as a code' set up that Travis promises.
>> 
>> Additionally, we are able to have a 'marker' Jenkinsfile of one line (
>> well, +18 of license :-) ) for each repo, which makes the management of
>> builds much much simpler. I would not like to see 300 .travis.yml files
>> duplicated across the Sling repos.
>> 
>> Of course, I for one am always open to the option to moving to some
>> other CI platform, granted that it provides tangible benefits over the
>> current setup.
>> 
>> Thanks,
>> 
>> Robert
>> 
>>> 
>>> Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian Schneider <
>>> chris@die-schneider.net>:
>>> 
>>>> 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 <
>>>> radu@apache.org>:
>>>> 
>>>>> Hi Christian,
>>>>> 
>>>>>> On 24 Apr 2019, at 10:32, Christian Schneider <
>>>>>> chris@die-schneider.net>
>>>>> 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
>>>> 
>>>> 
>>> 
>>> --
>> 
>> 
> 
> -- 
> -- 
> Christian Schneider
> http://www.liquid-reality.de
> 
> Computer Scientist
> http://www.adobe.com

Re: Travis builds for sling?

Posted by Christian Schneider <ch...@die-schneider.net>.

I also saw these single line Jenkinsfiles. They are super convenient as
long as your build has no specialities .. but I would have no clue what to
do if my build is different.

Btw. How do they work? The Jenkinsfile does not refer to any library or
similar .. so the build does not seem to be fully described by the source
repo. Is this defined in the jenkins build on the server?

Christian


Am Mi., 24. Apr. 2019 um 16:44 Uhr schrieb Robert Munteanu <
rombert@apache.org>:

> On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
> > s/jenkiona/jenkins/ :-)
>
> I like Jenkiona :-)
>
> Other that that - you're right, with the pipeline-based builds we
> already have the 'build as a code' set up that Travis promises.
>
> Additionally, we are able to have a 'marker' Jenkinsfile of one line (
> well, +18 of license :-) ) for each repo, which makes the management of
> builds much much simpler. I would not like to see 300 .travis.yml files
> duplicated across the Sling repos.
>
> Of course, I for one am always open to the option to moving to some
> other CI platform, granted that it provides tangible benefits over the
> current setup.
>
> Thanks,
>
> Robert
>
> >
> > Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian Schneider <
> > chris@die-schneider.net>:
> >
> > > 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 <
> > > radu@apache.org>:
> > >
> > > > Hi Christian,
> > > >
> > > > > On 24 Apr 2019, at 10:32, Christian Schneider <
> > > > > chris@die-schneider.net>
> > > > 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
> > >
> > >
> >
> > --
>
>

-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: Travis builds for sling?

Posted by Robert Munteanu <ro...@apache.org>.

On Wed, 2019-04-24 at 14:47 +0200, Christian Schneider wrote:
> s/jenkiona/jenkins/ :-)

I like Jenkiona :-)

Other that that - you're right, with the pipeline-based builds we
already have the 'build as a code' set up that Travis promises.

Additionally, we are able to have a 'marker' Jenkinsfile of one line (
well, +18 of license :-) ) for each repo, which makes the management of
builds much much simpler. I would not like to see 300 .travis.yml files
duplicated across the Sling repos.

Of course, I for one am always open to the option to moving to some
other CI platform, granted that it provides tangible benefits over the
current setup.

Thanks,

Robert

> 
> Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian Schneider <
> chris@die-schneider.net>:
> 
> > 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 <
> > radu@apache.org>:
> > 
> > > Hi Christian,
> > > 
> > > > On 24 Apr 2019, at 10:32, Christian Schneider <
> > > > chris@die-schneider.net>
> > > 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
> > 
> > 
> 
> --

Re: Travis builds for sling?

Posted by Christian Schneider <ch...@die-schneider.net>.

s/jenkiona/jenkins/ :-)

Am Mi., 24. Apr. 2019 um 14:47 Uhr schrieb Christian Schneider <
chris@die-schneider.net>:

> 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 <ra...@apache.org>:
>
>> Hi Christian,
>>
>> > On 24 Apr 2019, at 10:32, Christian Schneider <ch...@die-schneider.net>
>> 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
>
>

-- 
-- 
Christian Schneider
http://www.liquid-reality.de

Computer Scientist
http://www.adobe.com

Re: Travis builds for sling?

Posted by Christian Schneider <ch...@die-schneider.net>.

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 <ra...@apache.org>:

> Hi Christian,
>
> > On 24 Apr 2019, at 10:32, Christian Schneider <ch...@die-schneider.net>
> 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

Re: Travis builds for sling?

Posted by Radu Cotescu <ra...@apache.org>.

Hi Christian,

> On 24 Apr 2019, at 10:32, Christian Schneider <ch...@die-schneider.net> 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>