You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Jaroslav Tulach <ja...@oracle.com> on 2017/10/09 08:40:52 UTC

FYI: Enabling Travis CI for incubator-netbeans repository

Hi.
I've just requested 
issues.apache.org/jira/browse/INFRA-15249

It should help us verify essential aspects of NetBeans are preserved. For 
example that the code will remain buildable after merging a PR.

-jt

Re: Depending on GitHub & Travis was: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Emilian Bold <em...@gmail.com>.
No problem, I understand all this and the GitHub Travis integration is
pretty handy!

What I found odd was that you had to ask INFRA about Travis. But I guess it
has something to do with they premium plan Apache is under vs the free plan
which has more limits.


--emi

On Mon, Oct 9, 2017 at 7:01 PM, Jaroslav Tulach <ja...@oracle.com>
wrote:

> On pondělí 9. října 2017 17:44:12 CEST Emilian Bold wrote:
> > Well, I also find it odd how much Apache depends on GitHub. I'm OK with
> > Hudson / Jenkins since it's open source and you may (and I have) run it
> > yourself. AFAIK Travis is a pure service, no way to run it on my own
> server
> > and compile it from source code.
>
> I see.
>
> Well, in such case we can tell ourselves: GitHub and Travis are just tools
> to
> do our daily job. The core of Apache is Open:
> git-wip-us.apache.org/repos/asf?p=incubator-netbeans-html4j.git
> and
> builds.apache.org/
>
> Nothing will happen if .travis.yml is ignored - at most we get a broken
> Jenkins build later.
>
> -jt
>
>
>
> >
> >
> > --emi
> >
> > On Mon, Oct 9, 2017 at 5:40 PM, Wade Chandler <wa...@apache.org>
> >
> > wrote:
> > > On Oct 9, 2017 05:18, "Emilian Bold" <em...@gmail.com> wrote:
> > >
> > > but I'm
> > > not entirely cool with it being a commercial service after all.
> > >
> > >
> > > As opposed to Github or Jenkins (CloudBees)? I don't follow the use of
> > > "commercial" here.
> > >
> > > Wade
>
>
>

Depending on GitHub & Travis was: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Jaroslav Tulach <ja...@oracle.com>.
On pondělí 9. října 2017 17:44:12 CEST Emilian Bold wrote:
> Well, I also find it odd how much Apache depends on GitHub. I'm OK with
> Hudson / Jenkins since it's open source and you may (and I have) run it
> yourself. AFAIK Travis is a pure service, no way to run it on my own server
> and compile it from source code.

I see.

Well, in such case we can tell ourselves: GitHub and Travis are just tools to 
do our daily job. The core of Apache is Open: 
git-wip-us.apache.org/repos/asf?p=incubator-netbeans-html4j.git
and
builds.apache.org/

Nothing will happen if .travis.yml is ignored - at most we get a broken 
Jenkins build later.

-jt



> 
> 
> --emi
> 
> On Mon, Oct 9, 2017 at 5:40 PM, Wade Chandler <wa...@apache.org>
> 
> wrote:
> > On Oct 9, 2017 05:18, "Emilian Bold" <em...@gmail.com> wrote:
> > 
> > but I'm
> > not entirely cool with it being a commercial service after all.
> > 
> > 
> > As opposed to Github or Jenkins (CloudBees)? I don't follow the use of
> > "commercial" here.
> > 
> > Wade

Re: Enabling Travis CI for incubator-netbeans repository

Posted by Richard Lowery <Ri...@guilding.com>.
I tend to agree… GitLab being very GitHub-ish in nature, but runnable on your own infrastructure.  GitLab-CI is very similar to Travis-CI, but yet on-par with the reporting and visualizations you can get from Jenkins.  Just my opinion though.

--
Richard 

On 10/9/17, 10:45 AM, "Emilian Bold" <em...@gmail.com> wrote:

    Well, I also find it odd how much Apache depends on GitHub. I'm OK with
    Hudson / Jenkins since it's open source and you may (and I have) run it
    yourself. AFAIK Travis is a pure service, no way to run it on my own server
    and compile it from source code.
    
    
    --emi
    
    On Mon, Oct 9, 2017 at 5:40 PM, Wade Chandler <wa...@apache.org>
    wrote:
    
    > On Oct 9, 2017 05:18, "Emilian Bold" <em...@gmail.com> wrote:
    >
    > but I'm
    > not entirely cool with it being a commercial service after all.
    >
    >
    > As opposed to Github or Jenkins (CloudBees)? I don't follow the use of
    > "commercial" here.
    >
    > Wade
    >

Re: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Emilian Bold <em...@gmail.com>.
Well, I also find it odd how much Apache depends on GitHub. I'm OK with
Hudson / Jenkins since it's open source and you may (and I have) run it
yourself. AFAIK Travis is a pure service, no way to run it on my own server
and compile it from source code.


--emi

On Mon, Oct 9, 2017 at 5:40 PM, Wade Chandler <wa...@apache.org>
wrote:

> On Oct 9, 2017 05:18, "Emilian Bold" <em...@gmail.com> wrote:
>
> but I'm
> not entirely cool with it being a commercial service after all.
>
>
> As opposed to Github or Jenkins (CloudBees)? I don't follow the use of
> "commercial" here.
>
> Wade
>

Re: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Wade Chandler <wa...@apache.org>.
On Oct 9, 2017 05:18, "Emilian Bold" <em...@gmail.com> wrote:

but I'm
not entirely cool with it being a commercial service after all.


As opposed to Github or Jenkins (CloudBees)? I don't follow the use of
"commercial" here.

Wade

Re: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Jaroslav Tulach <ja...@oracle.com>.
Guys, if you like Travis, please approve:

github.com/apache/incubator-netbeans/pull/108


On pondělí 9. října 2017 12:17:41 CEST Emilian Bold wrote:
> Is this part of builds.apache.org or is Travis doing the build in some
> remote corner of the Cloud?
> 
> I really like the GitHub integration and the sanity check on PRs but I'm
> not entirely cool with it being a commercial service after all.

TheASF is paying some money to Travis, to make sure the service is running at 
acceptable speed, as far as I know:

https://blogs.apache.org/infra/entry/apache_gains_additional_travis_ci

In any case Travis seems to be an Apache approved way of verifying our PRs.
-jt

> 
> On Mon, Oct 9, 2017 at 11:40 AM, Jaroslav Tulach <jaroslav.tulach@oracle.com
> > wrote:
> > 
> > Hi.
> > I've just requested
> > issues.apache.org/jira/browse/INFRA-15249
> > 
> > It should help us verify essential aspects of NetBeans are preserved. For
> > example that the code will remain buildable after merging a PR.
> > 
> > -jt

Re: FYI: Enabling Travis CI for incubator-netbeans repository

Posted by Emilian Bold <em...@gmail.com>.
Is this part of builds.apache.org or is Travis doing the build in some
remote corner of the Cloud?

I really like the GitHub integration and the sanity check on PRs but I'm
not entirely cool with it being a commercial service after all.


--emi

On Mon, Oct 9, 2017 at 11:40 AM, Jaroslav Tulach <jaroslav.tulach@oracle.com
> wrote:

> Hi.
> I've just requested
> issues.apache.org/jira/browse/INFRA-15249
>
> It should help us verify essential aspects of NetBeans are preserved. For
> example that the code will remain buildable after merging a PR.
>
> -jt
>
>

AW: Enabling Travis CI for incubator-netbeans repository

Posted by Christian Lenz <ch...@gmx.net>.
Awesome 😊

Gesendet von Mail für Windows 10

Von: Jaroslav Tulach
Gesendet: Montag, 9. Oktober 2017 10:41
An: dev@netbeans.incubator.apache.org
Betreff: FYI: Enabling Travis CI for incubator-netbeans repository

Hi.
I've just requested 
issues.apache.org/jira/browse/INFRA-15249

It should help us verify essential aspects of NetBeans are preserved. For 
example that the code will remain buildable after merging a PR.

-jt