Do we have a timeframe for the 1.2 release? We'll be revving Mahout and would like to get the latest release into yours.
Thanks! On Mon, Mar 20, 2017 at 1:08 PM, Olaf Flebbe <[email protected]> wrote: > Hi, > > --user has the assumption with -v bind mount that the user insider the > container has the same user id within the container than the user id on the > host. The result of the current approach is: Files are created in the > current directory which the user itself may not be allowed to read/write > itself. > > In order to smash the problem forever I created BIGTOP-2679 : Let's create > a source container on top of our build container and use it. The additional > beauty is that the build could be done to scale out with docker swarm, > since no assumption about the underlying filesystem is made. And it is much > easier to use and less error prone. > > Please consider it. > > Olaf > > > Am 20.03.2017 um 06:49 schrieb Konstantin Boudnik <[email protected]>: > > > > On Sun, Mar 19, 2017 at 10:32 PM, Evans Ye <[email protected]> wrote: > >> Hi Cos, > >> > >> I think it would be better to go for Docker native solution by running > as > >> specific user. > > > > Absolutely agree. I guess the option wasn't available around the time. > > Thanks Evans! > > > >> Hi all, > >> > >> I've tested the docker --user jenkins option: > >> > >> https://ci.bigtop.apache.org/view/Packages/job/Bigtop- > trunk-packages-zeppelin/ > >> > >> It seems working well building zeppelin. > >> > >> The ONLY change for our build script in Jenkins is -u jenkins: > >> > >> [BEFORE] > >> docker run --rm -v `pwd`:/ws$DOCKER_SELINUX --workdir /ws -e > >> COMPONENTS=$COMPONENTS -e CONFIGURE_NEXUS=$CONFIGURE_NEXUS $NEXUS > >> bigtop/slaves:trunk-$OS \ > >> bash -c '. /etc/profile.d/bigtop.sh; ./gradlew allclean $CONFIGURE_NEXUS > >> $COMPONENTS-pkg' > >> > >> [AFTER] > >> docker run -u jenkins --rm -v `pwd`:/ws$DOCKER_SELINUX --workdir /ws -e > >> COMPONENTS=$COMPONENTS -e CONFIGURE_NEXUS=$CONFIGURE_NEXUS $NEXUS > >> bigtop/slaves:trunk-$OS \ > >> bash -c '. /etc/profile.d/bigtop.sh; ./gradlew allclean $CONFIGURE_NEXUS > >> $COMPONENTS-pkg' > >> > >> Let me try to adopt this in trunk-packages. > >> > >> > >> > >> > >> 2017-03-20 3:42 GMT+08:00 Konstantin Boudnik <[email protected]>: > >> > >>> Here's a tiny script I put together a while back to do just that > >>> (running builds under a non-privileged account). Feel free to use it > >>> https://is.gd/eMBIcG > >>> > >>> Cos > >>> > >>> > >>> -- > >>> Take care, > >>> Konstantin (Cos) Boudnik > >>> > >>> > >>> On Sat, Mar 18, 2017 at 10:34 PM, 김영우 (YoungWoo Kim) <[email protected] > > > >>> wrote: > >>>> Thanks Cos! > >>>> > >>>> Building Zeppelin 0.7.0 is failing because ci job is building Z as > root > >>>> user on docker. (We have a hack in Tez build to prevent this but the > hack > >>>> does not work for Z) > >>>> > >>>> Evans, Is it possible to start the job on containers as jenkins user > or > >>>> other appropriate user? > >>>> > >>>> Youngwoo > >>>> > >>>> > >>>> 2017. 3. 19. 오전 9:50에 "Konstantin Boudnik" <[email protected]>님이 작성: > >>>> > >>>>> I have combed through the tickets marked against 1.2 and reduced the > >>>>> list to just 40. Here's the link to the query > >>>>> https://is.gd/lij6iI > >>>>> > >>>>> I've commented on most of the tickets that look to be almost ready or > >>>>> require attention and pinged people involved. Please take a look into > >>>>> the tickets assigned to you and either make an effort to finish them > >>>>> or move them to backlog or to the next release if you plan to work on > >>>>> it later. > >>>>> > >>>>> There are still a few blocker, Zep 0.7 is one them - it is broken on > >>>>> every single platform (BIGTOP-2699) and JDK8 Hadoop related issue > >>>>> (BIGTOP-2673). > >>>>> > >>>>> Thanks for your help! > >>>>> Cos > >>>>> -- > >>>>> Take care, > >>>>> Konstantin (Cos) Boudnik > >>>>> > >>>>> > >>>>> On Fri, Mar 17, 2017 at 7:31 PM, Evans Ye <[email protected]> > wrote: > >>>>>> Huge +1 here. > >>>>>> Please ping me either for review or for release related tasks. For > >>> 1.2 to > >>>>>> release I personally would like work on some task to make > provisioner > >>> and > >>>>>> sandbox more mature. > >>>>>> > >>>>>> Amir do you have any input from ppc64le side? > >>>>>> Everything is good for release? > >>>>>> > >>>>>> Konstantin Boudnik <[email protected]>於 2017年3月18日 週六，上午2:29寫道： > >>>>>> > >>>>>>> I would think so, yes > >>>>>>> > >>>>>>> -- > >>>>>>> > >>>>>>> Take care, > >>>>>>> > >>>>>>> Konstantin (Cos) Boudnik > >>>>>>> > >>>>>>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> Disclaimer: Opinions expressed in this email are those of the > author, > >>>>>>> > >>>>>>> and do not necessarily represent the views of any company the > author > >>>>>>> > >>>>>>> might be affiliated with at the moment of writing. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> On Fri, Mar 17, 2017 at 11:27 AM, Andrew Musselman > >>>>>>> > >>>>>>> <[email protected]> wrote: > >>>>>>> > >>>>>>>> We have a new Mahout release coming out hopefully in the next few > >>>>> days; > >>>>>>> is > >>>>>>> > >>>>>>>> there time to get a new rev into Bigtop? > >>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>>> On Fri, Mar 17, 2017 at 11:18 AM, Konstantin Boudnik < > >>> [email protected]> > >>>>>>> wrote: > >>>>>>> > >>>>>>>> > >>>>>>> > >>>>>>>>> Thanks for the push, dude - we really need to release it. It > >>> doesn't > >>>>>>> > >>>>>>>>> even matter what board says on the topic - it is just a common > >>> sense > >>>>>>> > >>>>>>>>> for a viable project like Bigtop. > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>>>> Considering how fast Groovy is moving forward we need to be > >>> upgrading > >>>>>>> > >>>>>>>>> to 2.4.10 at least ;) > >>>>>>> > >>>>>>>>> Same with Ignite - 1.9 is out now, I will update the ticket and > >>> will > >>>>>>> > >>>>>>>>> try to work on it over the weekend. > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>>>> -- > >>>>>>> > >>>>>>>>> Take care, > >>>>>>> > >>>>>>>>> Konstantin (Cos) Boudnik > >>>>>>> > >>>>>>>>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>>>> Disclaimer: Opinions expressed in this email are those of the > >>> author, > >>>>>>> > >>>>>>>>> and do not necessarily represent the views of any company the > >>> author > >>>>>>> > >>>>>>>>> might be affiliated with at the moment of writing. > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>>>> On Fri, Mar 17, 2017 at 8:22 AM, Roman Shaposhnik < > >>>>> [email protected] > >>>>>>>> > >>>>>>> > >>>>>>>>> wrote: > >>>>>>> > >>>>>>>>>> Hi! > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> as was pointed out by the ASF board lately we haven't > >>>>>>> > >>>>>>>>>> had a release in quite some time. They are right -- release > >>>>>>> > >>>>>>>>>> early and release often is the only way to go. So, I'd like > >>>>>>> > >>>>>>>>>> to volunteer to be a co-{release manager} with Cos and > >>>>>>> > >>>>>>>>>> push 1.2 out ASAP. > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> Looking at > >>>>>>> > >>>>>>>>>> https://issues.apache.org/jira/browse/BIGTOP-2282 > >>>>>>> > >>>>>>>>>> makes me think that we're 90% done with formalizing > >>>>>>> > >>>>>>>>>> the BOM. The only two things outstanding are: > >>>>>>> > >>>>>>>>>> Bump Ignite to 1.8 > >>>>>>> > >>>>>>>>>> Bump Groovy version to 2.4.7 > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> With Groovy I can take care of it myself. But with Ignite > >>>>>>> > >>>>>>>>>> I either need somebody to help, or given how long it is > >>>>>>> > >>>>>>>>>> outstanding, may be we can just leave it be. Please chime > >>>>>>> > >>>>>>>>>> in if you'd like to volunteer. > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> Looking at: > >>>>>>> > >>>>>>>>>> > >>>>>>> https://ci.bigtop.apache.org/view/Packages/job/Bigtop- > >>> trunk-packages/ > >>>>>>> > >>>>>>>>>> makes me think that the biggest obstacle there is ARM64 > >>>>>>> > >>>>>>>>>> which we should fix pretty soon. The rest looks reasonable. > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> With all of that in mind, I'd like to shoot for the first RC > >>> made > >>>>>>> > >>>>>>>>>> available over the next weekend. > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> Thoughts? > >>>>>>> > >>>>>>>>>> > >>>>>>> > >>>>>>>>>> Thanks, > >>>>>>> > >>>>>>>>>> Roman. > >>>>>>> > >>>>>>>>> > >>>>>>> > >>>>>>> > >>>>> > >>> > >
