From dev-return-250-archive-asf-public=cust-asf.ponee.io@zipkin.apache.org Wed Jan 30 16:48:34 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id B1006180652 for ; Wed, 30 Jan 2019 17:48:33 +0100 (CET) Received: (qmail 15984 invoked by uid 500); 30 Jan 2019 16:48:32 -0000 Mailing-List: contact dev-help@zipkin.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@zipkin.apache.org Delivered-To: mailing list dev@zipkin.apache.org Received: (qmail 15973 invoked by uid 99); 30 Jan 2019 16:48:32 -0000 Received: from mail-relay.apache.org (HELO mailrelay2-lw-us.apache.org) (207.244.88.137) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 30 Jan 2019 16:48:32 +0000 Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by mailrelay2-lw-us.apache.org (ASF Mail Server at mailrelay2-lw-us.apache.org) with ESMTPSA id C81062DD3 for ; Wed, 30 Jan 2019 16:48:31 +0000 (UTC) Received: by mail-ed1-f49.google.com with SMTP id h15so167643edb.4 for ; Wed, 30 Jan 2019 08:48:31 -0800 (PST) X-Gm-Message-State: AJcUukfvoCEQaN/ZJj59giwj9I55bLOw3r6sLVGF0zEakibq0PqDSgPO tFqvYKaRsbl1C2J0JD8KOjTCVid392YioW7mb8Q= X-Google-Smtp-Source: ALg8bN6Pvi0y59ePX4o8u7UYRyjDzvLfWLyeVILz7pscohXb3MD7XGuSn1wsvdIfEpUMJcwp0sPAhh/sCvgUCXdDdnE= X-Received: by 2002:a17:906:5501:: with SMTP id r1mr20287454ejp.167.1548866910751; Wed, 30 Jan 2019 08:48:30 -0800 (PST) MIME-Version: 1.0 References: <1649346089.20190128071829@gmail.com> <436056606.20190128213349@gmail.com> <1536227993.20190130114527@gmail.com> In-Reply-To: <1536227993.20190130114527@gmail.com> From: =?UTF-8?B?Wm9sdMOhbiBOYWd5?= Date: Wed, 30 Jan 2019 16:48:19 +0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: The brave-karaf is migrated! To: dev@zipkin.apache.org, Andriy Redko Cc: Adrian Cole , Brian Devins-Suresh Content-Type: multipart/alternative; boundary="00000000000005167a0580afaef6" --00000000000005167a0580afaef6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thanks for the offer, Andriy! I've already set up a pipeline job PoC-ing that we can build and collect test results ( https://builds.apache.org/view/Z/view/Zipkin/job/incubator-zipkin-brave-kar= af-test/), now looking into how test result notifications to GitHub would work. I can't seem to find any installed plugins that would allow for that, but I'm sure I must just be missing something. Any pointers in that would be appreciated :) On Wed, Jan 30, 2019 at 4:45 PM Andriy Redko wrote: > Great progress, Adrian! Sorry, I was not able to join the Gitter, but > followed the PRs. Do you need any > help with creating initial jobs? Or do you want me to help with getting a > few guys to become Jenkins power > users (to be able to create pipelines, jobs, etc). Please let me know! > > Best Regards, > Andriy Redko > > > AC> TL;DR; we are going to try using jenkins as it can magically have > access to deploy snapshots. > > > AC> While some of us are more familiar with Travis or CircleCI, there's a > special feature we get when using ASF managed > AC> infra for builds.. credentials! Basically, we can deploy snapshots > with the implicit credentials. > > > AC> There are some other things to look into, for example getting the > green check marks when pull requests pass.. > AC> whether to use jenkins for this (current assumption) or do one of our > existing things (circleci and/or travis). > AC> There are some constraints because we don't have admin access to the > repos which might make jenkins an easier choice > AC> for us all around. We'll explore this area over the next day or two. > > > AC> Will keep you posted! > AC> -A > > AC> On Wed, Jan 30, 2019 at 3:36 PM Adrian Cole > wrote: > > AC> If anyone is interested, join the gitter channel as we are working on > this now. > > AC> On Tue, Jan 29, 2019 at 3:33 AM Andriy Redko wrote= : > > AC> Hi Brian, > > AC> We do have a JIRA project for Zipkin [1] but as far as I remember, > team was/is > AC> more comfortable with using Github to track the issues (and that's > perfectly fine). > AC> If you guys need any help from mentors, please let us know, I though= t > we wanted to > AC> give Jenkins a try but staying with Travis or/and Circle is not an > issue, as > AC> far as the team feels this is the right choice. > > AC> [1] https://issues.apache.org/jira/projects/ZIPKIN > > AC> Best Regards, > AC> Andriy Redko > > BDS>> I think yeah, probably belongs on the dev list. I've added it in m= y > reply. > > BDS>> As far as Jenkins goes. I think leaving things on Travis/Circle fo= r > now > BDS>> should be our plan, but I do think we will want to move to Jenkins > in > BDS>> the future based on the fragility we have seen with Travis/Circle > (the > BDS>> reason we have both). I have a bunch of experience in the pipeline > work > BDS>> also so I'd be able to lend a hand here, and I could probably > enlist the > BDS>> help of a former colleague who is a bit of a Groovy wizard and > wrote our > BDS>> pipeline component library at my last job. > > BDS>> This brings me to something I've been thinking about. How do we > want to > BDS>> organize these types of tasks/projects? I've been against using > JIRA in the > BDS>> past, but specifically for tracking issues/bugs/feature requests. > Maybe we > BDS>> should have a JIRA created that we use only for project level > initiatives? > BDS>> Like adopting Jenkins for CI, or other infrastructure type things. > I don't > BDS>> know, maybe that is too much structure for things that ultimately > are not > BDS>> delivering value to the greater community but instead are just > helping us > BDS>> stay organized. I had considered Github projects but considering > the Org we > BDS>> have access to at that level is not Apache I would feel weird > coordinating > BDS>> the Apache tasks from the non-Apache org. > > > BDS>> On Mon, Jan 28, 2019 at 8:50 AM Zolt=C3=A1n Nagy > wrote: > > >>> Awesomeness, this is pretty exciting :) > > >>> Re. the CI system, I think the consensus was that we should change o= ne > >>> thing at a time, and keep using Travis / Circle for the time being, > just to > >>> avoid duplicating efforts towards many different CI systems. FWIW, I > like > >>> Jenkins Pipelines a lot, they provide tons of tools and structure > that you > >>> kinda have to script with Bash for Travis / Circle, and there's grea= t > >>> support for Java build systems. That said, methinks 2 CI systems > (Travis, > >>> Circle) is a bit much, and 3 is definitely too much, so I'd propose = we > >>> attack the Jenkins-or-not-to-Jenkins issue with a separate effort if > we > >>> want to go that way, and focus now on the ASF release process. > > >>> The wiki seems to be (back) up now; couple of unresolved questions i= n > >>> there. I think it should be fine to get started with the process, > learn as > >>> we go, and document what we learn / decide afterwards. No need for a > big > >>> up-front planning. > > >>> Meta: shouldn't this go to the dev@ list? (Honest question, I'm as > new to > >>> the ASF as anyone) > > >>> On Mon, Jan 28, 2019 at 12:18 PM Andriy Redko > wrote: > > >>>> Hey guys! > > >>>> The brave-karaf repo is migrated to Apache organization, congrats > guys! > >>>> This is the > >>>> first but certainly not the last. Should we start integrating it > into the > >>>> Apache CI / Jenkins, > >>>> I think I have all the permissions to create the jobs (we probably > need > >>>> JDK8 and JDK11 pipelines)? > >>>> I wanted to reread the Wiki page which Zoltan drafted before but > Apache > >>>> Confluence is down ... rare > >>>> event but happens :( What do you think guys? > > >>>> Thanks! > > >>>> [1] https://github.com/apache/incubator-zipkin-brave-karaf > > >>>> Best Regards, > >>>> Andriy Redko > > > > >>>> -------------------------------------------------------------------= -- > >>>> To unsubscribe, e-mail: private-unsubscribe@zipkin.apache.org > >>>> For additional commands, e-mail: private-help@zipkin.apache.org > > > > > AC> --------------------------------------------------------------------= - > AC> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org > AC> For additional commands, e-mail: dev-help@zipkin.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org > For additional commands, e-mail: dev-help@zipkin.apache.org > > --00000000000005167a0580afaef6--