[jira] [Created] (BIGTOP-2514) Update Zeppelin version to 0.6.1

[Alexander Bezzubov (JIRA)]

Alexander Bezzubov created BIGTOP-2514:
--

 Summary: Update Zeppelin version to 0.6.1
 Key: BIGTOP-2514
 URL: https://issues.apache.org/jira/browse/BIGTOP-2514
 Project: Bigtop
  Issue Type: Bug
Reporter: Alexander Bezzubov


Apache Zeppelin is finalizing new release 0.6.1 under ZEPPELIN-1177

As soon as it is officially released it would be great to get it into the next 
release of BigTop



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [DISCUSS] Unblocking Juju development

[Roman Shaposhnik]

Now my time to be late with a replay, but the good news -- I'm back
from vacation! :-)

On Tue, Aug 2, 2016 at 12:09 PM, Konstantin Boudnik  wrote:
> Sorry for the belated joining of the party - crazy travel schedule an all
> that. I like the idea of making a special branch for this development, so ppl
> working on would have the ability to commit the code as they see fit and, once
> it is ready, we can simply merge it into the master.
>
> Is this something along the lines you had in mind, Roman?

Yes. That's exactly what I had in mind. But if we agree that the
branch is the right
way to proceed, we then need to ask how to enable non-committers to be able
to commit it.

Thanks,
Roman.

[GitHub] bigtop issue #44: BIGTOP-1769. Zeppelin Integration

[c0s]

Github user c0s commented on the issue:

https://github.com/apache/bigtop/pull/44
  
I guess...


---
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] bigtop issue #44: BIGTOP-1769. Zeppelin Integration

[bzz]

Github user bzz commented on the issue:

https://github.com/apache/bigtop/pull/44
  
Shall this one be closed, as soon as 
[BIGTOP-1769](https://issues.apache.org/jira/browse/BIGTOP-1769) is resolved?


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

[Roman Shaposhnik]

The point there is that only builds done on builds.apache.org are capable
of pushing nightly artifacts to official ASF Maven repo for snapshots.

Given the restructuring of the build systems -- somebody has to probably
update those jobs to still be relevant.

Thanks,
Roman.

On Mon, Aug 8, 2016 at 3:23 PM, Konstantin Boudnik  wrote:
> On Mon, Aug 08, 2016 at 08:52PM, Olaf Flebbe wrote:
>> Hi Cos,
>>
>> thanks for jumping in.
>>
>> I am failing to understand the maven repository things involved here.
>>
>> For instance It seems to me that the version in pom.xml are horrible out of
>> sync with bigtop.bom.
>> Reading BIGTOP-1429 I have got the impression that we technically cannot run
>> the mvn deploy things on ci.bigtop.apache.org.  Is this the whole point of
>> running this things on builds.apache.org ?
>
> Yes, mvn deploy is the whole point. And things being out of sync is a problem
> of us still having two different build systems ;(
>
> Cos
>
>> > Am 08.08.2016 um 20:23 schrieb Konstantin Boudnik :
>> >
>> > On Mon, Aug 08, 2016 at 02:07AM, Evans Ye wrote:
>> >> Except for Bigtop-trunk, which we're building the whole set of rpm/deb for
>> >> OS matrix, I've no idea what others are doing.
>> >> Maybe Roman knows better.
>> >>
>> >> 2016-08-07 3:22 GMT+08:00 Olaf Flebbe :
>> >>
>> >>> Hi,
>> >>>
>> >>> can anyone enlighten me what the propose of the jenkins jobs at
>> >>> builds.apache.org is ?
>> >>>
>> >>> I cannot modify nor can I delete these jobs:
>> >>>
>> >>> https://builds.apache.org/view/All/job/Bigtop-trunk-test-execution/
>> >>>
>> >>> Bigtop-Patch-Evaluate
>> >>> Bigtop-tickle-slaves
>> >>> Bigtop-trunk
>> >>> Bigtop-trunk-iTest
>> >>> Bigtop-trunk-test-execution
>> >>> Bigtop-trunk-testartifacts
>> >
>> > At least the last three were supposed to be building and publishing the
>> > snapshots of Bigtop maven artifacts.
>> >
>> > Now sure about #2,3. The first once seems like an attempt to implement some
>> > pre-commit hook.
>> >
>> > Cos
>> >
>>
>
>

Re: builds.apache.org

[Konstantin Boudnik]

On Mon, Aug 08, 2016 at 08:52PM, Olaf Flebbe wrote:
> Hi Cos,
> 
> thanks for jumping in.
> 
> I am failing to understand the maven repository things involved here.
> 
> For instance It seems to me that the version in pom.xml are horrible out of
> sync with bigtop.bom.
> Reading BIGTOP-1429 I have got the impression that we technically cannot run
> the mvn deploy things on ci.bigtop.apache.org.  Is this the whole point of
> running this things on builds.apache.org ?

Yes, mvn deploy is the whole point. And things being out of sync is a problem
of us still having two different build systems ;(

Cos
 
> > Am 08.08.2016 um 20:23 schrieb Konstantin Boudnik :
> > 
> > On Mon, Aug 08, 2016 at 02:07AM, Evans Ye wrote:
> >> Except for Bigtop-trunk, which we're building the whole set of rpm/deb for
> >> OS matrix, I've no idea what others are doing.
> >> Maybe Roman knows better.
> >> 
> >> 2016-08-07 3:22 GMT+08:00 Olaf Flebbe :
> >> 
> >>> Hi,
> >>> 
> >>> can anyone enlighten me what the propose of the jenkins jobs at
> >>> builds.apache.org is ?
> >>> 
> >>> I cannot modify nor can I delete these jobs:
> >>> 
> >>> https://builds.apache.org/view/All/job/Bigtop-trunk-test-execution/
> >>> 
> >>> Bigtop-Patch-Evaluate
> >>> Bigtop-tickle-slaves
> >>> Bigtop-trunk
> >>> Bigtop-trunk-iTest
> >>> Bigtop-trunk-test-execution
> >>> Bigtop-trunk-testartifacts
> > 
> > At least the last three were supposed to be building and publishing the
> > snapshots of Bigtop maven artifacts.
> > 
> > Now sure about #2,3. The first once seems like an attempt to implement some
> > pre-commit hook.
> > 
> > Cos
> > 
> 

Re: builds.apache.org

[Olaf Flebbe]

Hi Cos,

thanks for jumping in.

I am failing to understand the maven repository things involved here.

For instance It seems to me that the version in pom.xml are horrible out of 
sync with bigtop.bom.
Reading BIGTOP-1429 I have got the impression that we technically cannot run 
the mvn deploy things on ci.bigtop.apache.org.  Is this the whole point of 
running this things on builds.apache.org ?

Olaf

> Am 08.08.2016 um 20:23 schrieb Konstantin Boudnik :
> 
> On Mon, Aug 08, 2016 at 02:07AM, Evans Ye wrote:
>> Except for Bigtop-trunk, which we're building the whole set of rpm/deb for
>> OS matrix, I've no idea what others are doing.
>> Maybe Roman knows better.
>> 
>> 2016-08-07 3:22 GMT+08:00 Olaf Flebbe :
>> 
>>> Hi,
>>> 
>>> can anyone enlighten me what the propose of the jenkins jobs at
>>> builds.apache.org is ?
>>> 
>>> I cannot modify nor can I delete these jobs:
>>> 
>>> https://builds.apache.org/view/All/job/Bigtop-trunk-test-execution/
>>> 
>>> Bigtop-Patch-Evaluate
>>> Bigtop-tickle-slaves
>>> Bigtop-trunk
>>> Bigtop-trunk-iTest
>>> Bigtop-trunk-test-execution
>>> Bigtop-trunk-testartifacts
> 
> At least the last three were supposed to be building and publishing the
> snapshots of Bigtop maven artifacts.
> 
> Now sure about #2,3. The first once seems like an attempt to implement some
> pre-commit hook.
> 
> Cos
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: builds.apache.org

[Konstantin Boudnik]

On Mon, Aug 08, 2016 at 02:07AM, Evans Ye wrote:
> Except for Bigtop-trunk, which we're building the whole set of rpm/deb for
> OS matrix, I've no idea what others are doing.
> Maybe Roman knows better.
> 
> 2016-08-07 3:22 GMT+08:00 Olaf Flebbe :
> 
> > Hi,
> >
> > can anyone enlighten me what the propose of the jenkins jobs at
> > builds.apache.org is ?
> >
> > I cannot modify nor can I delete these jobs:
> >
> > https://builds.apache.org/view/All/job/Bigtop-trunk-test-execution/
> >
> > Bigtop-Patch-Evaluate
> > Bigtop-tickle-slaves
> > Bigtop-trunk
> > Bigtop-trunk-iTest
> > Bigtop-trunk-test-execution
> > Bigtop-trunk-testartifacts

At least the last three were supposed to be building and publishing the
snapshots of Bigtop maven artifacts.

Now sure about #2,3. The first once seems like an attempt to implement some
pre-commit hook.

Cos

Re: builds.apache.org

[Olaf Flebbe]

Hi Evans,

Using my PMC Chairs Karma I added you to the jenkins admins for build.apache.org

Please see at the jobs yourself:
https://builds.apache.org/view/B/view/Bigtop/

For instance
The bigtop-trunk job does a mvn deploy with a JDK 1.6 .

We either can remove this altogether or should update it to JDK 1.7

Hi Roman,

could you please enlighten us ? What is the usecase for this?


Olaf





> Am 07.08.2016 um 20:07 schrieb Evans Ye :
> 
> Except for Bigtop-trunk, which we're building the whole set of rpm/deb for
> OS matrix, I've no idea what others are doing.
> Maybe Roman knows better.
> 
> 2016-08-07 3:22 GMT+08:00 Olaf Flebbe :
> 
>> Hi,
>> 
>> can anyone enlighten me what the propose of the jenkins jobs at
>> builds.apache.org is ?
>> 
>> I cannot modify nor can I delete these jobs:
>> 
>> https://builds.apache.org/view/All/job/Bigtop-trunk-test-execution/
>> 
>> Bigtop-Patch-Evaluate
>> Bigtop-tickle-slaves
>> Bigtop-trunk
>> Bigtop-trunk-iTest
>> Bigtop-trunk-test-execution
>> Bigtop-trunk-testartifacts
>> 
>> If noone seems to know about these job I will ask INFRA to give me access
>> rights.
>> 
>> Olaf
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

[jira] [Created] (BIGTOP-2513) Some RAT exclude rules defined in build.gradle are not defined in pom.xml

[Kengo Seki (JIRA)]

Kengo Seki created BIGTOP-2513:
--

 Summary: Some RAT exclude rules defined in build.gradle are not 
defined in pom.xml
 Key: BIGTOP-2513
 URL: https://issues.apache.org/jira/browse/BIGTOP-2513
 Project: Bigtop
  Issue Type: Bug
  Components: build
Reporter: Kengo Seki
Priority: Minor


I ran {{mvn apache-rat:check}} in accordance with ["How to Contribute" wiki 
page|https://cwiki.apache.org/confluence/display/BIGTOP/How+to+Contribute] and 
it failed:

{code}
sekikn@ubuntu:~/bigtop$ mvn apache-rat:check

(snip)

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.807 s
[INFO] Finished at: 2016-08-09T00:49:39+09:00
[INFO] Final Memory: 13M/305M
[INFO] 
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.7:check 
(default-cli) on project bigtop: Too many unapproved licenses: 2 -> [Help 1]
{code}

But [Bigtop-trunk-RAT-check jenkins 
job|https://ci.bigtop.apache.org/job/Bigtop-trunk-RAT-check/] is succeeding. 
This is because some exclude rules are not defined in pom.xml.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (BIGTOP-2512) Wrong help message in docker-hadoop.sh

[Kengo Seki (JIRA)]

Kengo Seki created BIGTOP-2512:
--

 Summary: Wrong help message in docker-hadoop.sh
 Key: BIGTOP-2512
 URL: https://issues.apache.org/jira/browse/BIGTOP-2512
 Project: Bigtop
  Issue Type: Bug
  Components: deployment, vm
Reporter: Kengo Seki
Priority: Trivial


docker-hadoop.sh says:

{code}
  commands:
   -c NUM_INSTANCES, --create=NUM_INSTANCES  Create a Docker based Bigtop 
Hadoop cluster
{code}

but the following command fails:

{code}
sekikn@ubuntu:~/bigtop/bigtop-deploy/vm/vagrant-puppet-docker$ 
./docker-hadoop.sh --create=3
Unknown argument: '--create=3'
{code}

the following works:

{code}
$ ./docker-hadoop.sh --create 3
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)