[GitHub] flume pull request #75: Set MAVEN_OPTS for Travis-CI

[bessbd]

GitHub user bessbd opened a pull request:

https://github.com/apache/flume/pull/75

Set MAVEN_OPTS for Travis-CI

Travis builds occasionally fail with Java heap space error.

This commit sets higher limits to fix the issue mentioned above.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bessbd/flume travis-mvn-opts

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flume/pull/75.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #75


commit 6c921b05876d185388c7f4f1e6e6fec74da851c6
Author: Bessenyei Balázs Donát 
Date:   2016-10-22T22:09:28Z

Set MAVEN_OPTS for Travis-CI

Travis builds occasionally fail with Java heap space error.

This commit sets higher limits to fix the issue mentioned above.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: Enabling Travis-CI on Flume

[Balazs Donat Bessenyei]

Infra has enabled Travis-CI for us.

mvn clean install -DskipTests is executed on all PR-s and commits from now on.

However, builds occasionally fail with heap space error.
To fix that issue, I have opened a pull request:
https://github.com/apache/flume/pull/75 . Any reviews and comments are
welcome.


Thank you,

Donat


On Fri, Oct 21, 2016 at 6:14 PM, Mike Percy  wrote:
> Hi Lior!
>
> No, my message was not directed at you, or any person in particular. I
> intended this message for those paying attention to this topic to try and
> set expectations for how decision making for things like this usually (and
> hopefully) works in Apache: If you are willing to do the work to get
> something done, then it will probably get done the way you want!
>
> (Assuming the end result is something that others in the community want --
> in this case, it's very basic pre-commit checks. I think we have consensus
> that pre-commit checks are something that would be a net benefit to
> everyone.)
>
> Sorry for any confusion! And don't let me stop people from voicing their
> views and concerns.
>
> Best,
> Mike
>
> On Fri, Oct 21, 2016 at 4:44 PM, Lior Zeno  wrote:
>
>> Mike, I was not holding Donat back. I was just suggesting ways to configure
>> Jenins, per Donat's request. I'm sorry if my former post delivered the
>> wrong message.
>>
>> On Fri, Oct 21, 2016 at 6:29 PM, Mike Percy  wrote:
>>
>> > Personally I prefer Jenkins over TravisCI for various reasons however if
>> > Donat is willing to do the work of adding pre-commit checks on PRs via
>> > Travis then I say let him do it, in the Apache spirit of "let they that
>> do
>> > the work make the decisions".
>> >
>> > If someone actually spends the time to set up Jenkins and configure it to
>> > do the same thing, then great, let's switch when it's ready.
>> >
>> > Note that only ASF committers have access to Jenkins so non-committers
>> will
>> > need to work with a committer to get it done if they want to help.
>> >
>> > Mike
>> >
>> > On Fri, Oct 21, 2016 at 3:46 PM, Lior Zeno  wrote:
>> >
>> > > There are many ways to do it, for example:
>> > > https://www.theguild.nl/building-github-pull-requests-using-
>> > > jenkins-pipelines/
>> > > or https://www.theguild.nl/building-github-pull-requests-with-jenkins/
>> > for
>> > > earlier versions of Jenkins.
>> > > I do not really care if it would be Jenkins or Travis, but I do think
>> > that
>> > > we can get Jenkins configured faster since we already have it. I can
>> help
>> > > with the configuration.
>> > >
>> > > On Fri, Oct 21, 2016 at 5:17 PM, Balazs Donat Bessenyei <
>> > > bes...@cloudera.com
>> > > > wrote:
>> > >
>> > > > As I haven't received any objections to enabling Travis, I'm going to
>> > > > ask INFRA to enable it for Flume soon.
>> > > >
>> > > > This change would help submitting and reviewing pull requests.
>> > > >
>> > > > If someone figures out how we could use Jenkins for this purpose, we
>> > > > can always disable Travis.
>> > > >
>> > > > PS. there are more projects using Travis:
>> > > > https://issues.apache.org/jira/browse/INFRA-12757?jql=
>> > > > project%20%3D%20INFRA%20AND%20text%20~%20travis%20ORDER%
>> > > > 20BY%20updated%20DESC
>> > > >
>> > > > On Fri, Oct 14, 2016 at 5:41 PM, Attila Simon 
>> > wrote:
>> > > > > Denes I'm happy to help you in this endeavor of setting up jenkins
>> > job
>> > > > for
>> > > > > verifying pull requests.
>> > > > >
>> > > > >
>> > > > > *Attila Simon*
>> > > > > Software Engineer
>> > > > > Email:   s...@cloudera.com
>> > > > >
>> > > > > [image: Cloudera Inc.]
>> > > > >
>> > > > > On Fri, Oct 14, 2016 at 2:47 PM, Denes Arvay 
>> > > wrote:
>> > > > >
>> > > > >> I'd also vote for Jenkins with github PRs.
>> > > > >> I just checked Mesos and the PRs are checked by Travis, or at
>> least
>> > > they
>> > > > >> experienced with it, there's a short discussion regarding to
>> Travis
>> > at
>> > > > >> https://github.com/apache/mesos/pull/165
>> > > > >>
>> > > > >> As for the jenkins pull request job I'd be happy to set it up or
>> > help
>> > > > >> setting it up.
>> > > > >>
>> > > > >> Denes
>> > > > >>
>> > > > >> On Fri, Oct 14, 2016 at 2:15 PM Lior Zeno 
>> > wrote:
>> > > > >>
>> > > > >> Are we switching to PRs from patches + RB? In Apache Mesos, they
>> > have
>> > > a
>> > > > >>
>> > > > >> review bot that can leave a comment on the patch, we could try and
>> > > port
>> > > > it
>> > > > >>
>> > > > >> to Flume. I think they use Jenkins too.
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >> On Fri, Oct 14, 2016 at 3:11 PM, Balazs Donat Bessenyei <
>> > > > >> bes...@cloudera.com
>> > > > >>
>> > > > >> > wrote:
>> > > > >>
>> > > > >>
>> > > > >>
>> > > > >> > If the same function can be achieved with Jenkins and it's easy
>> > > > >>
>> > > > >> > (+quick) to set up, I'm totally happy with that.
>> > > > >>
>> > > > >> >
>> > > > >>
>> > > > >> > What do we have to do to enable Jenkins builds on PR-s?
>> > > > >>
>> > > > >> >
>> > > > >>
>> > >

Jenkins build is back to normal : Flume-trunk-hbase-1 #218

[Apache Jenkins Server]

See 

[GitHub] flume pull request #74: Fix .travis.yml

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/flume/pull/74


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] flume pull request #74: Fix .travis.yml

[bessbd]

GitHub user bessbd opened a pull request:

https://github.com/apache/flume/pull/74

Fix .travis.yml

License was missing from .travis.yml, so RAT checks failed.

This commit adds the license header to .travis.yml.
After this change RAT passes again.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bessbd/flume travis-license-fix

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flume/pull/74.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #74


commit 51aeaa6c1f6681668d2ff0e7e6b0833b114b70c1
Author: Bessenyei Balázs Donát 
Date:   2016-10-22T20:16:22Z

Fix .travis.yml

License was missing from .travis.yml, so RAT checks failed.

This commit adds the license header to .travis.yml.
After this change RAT passes again.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Build failed in Jenkins: Flume-trunk-hbase-1 #217

[Apache Jenkins Server]

See 

Changes:

[bessbd] Add .travis.yml

--
[...truncated 1544 lines...]
[INFO] 
[INFO] Skipping Flume NG ElasticSearch Sink
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume NG Morphline Solr Sink
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Shared Utils
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Shared Kafka Test Utils
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Kafka Sink
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume NG Kite Dataset Sink
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume NG Hive Sink
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Sources
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Scribe Source
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume JMS Source
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Twitter Source
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Kafka Source
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping Flume Taildir Source
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] 
[INFO] Skipping flume-kafka-channel
[INFO] This project has been banned from the build due to previous failures.
[INFO]