yep probably better to follow up on zipkin-api repo for whatever end. since
people routinely access the swagger through zipkin.io we will need to
address this somehow before telling people too much about zipkin.apache.org
imho

On Mon, Apr 22, 2019, 5:57 PM Zoltán Nagy <[email protected]> wrote:

> Watch out, replies to the GitBox mails to dev@ don't seem to make it back
> to GH :D
>
> > except the missing link to zipkin-api but that's on the burner
>
> I guess you mean the missing content at
> https://zipkin.apache.org/zipkin-api (as
> opposed to not linking to it)? I guess we could also "hotfix" this as
> needed by manually pushing stuff into the asf-site branch in
> incubator-zipkin-website (and update the path the UI uses to fetch the
> Swagger definition to also use zipkin.apache.org). We can do it, if it
> comes to it, but it might also be nice to keep the repo "clean" and
> populate zipkin-api "properly". I don't have a strong opinion on this
> trade-off, happy to leave it to JC and you (and whoever else might actually
> have an opinion).
>
> On Mon, Apr 22, 2019 at 9:37 AM Adrian Cole <[email protected]>
> wrote:
>
> > This is great news, Zoltan.
> >
> > Thanks for all the help. I've noticed the website looks current now
> > (except the missing link to zipkin-api but that's on the burner)
> >
> > On Mon, Apr 22, 2019 at 5:08 PM GitBox <[email protected]> wrote:
> > >
> > > abesto commented on issue #2: Sync changes from openzipkin/
> > openzipkin.github.io
> > > URL:
> >
> https://github.com/apache/incubator-zipkin-website/pull/2#issuecomment-485358535
> > >
> > >
> > >    Happy to report that after some Git wrangling, the build at <
> >
> https://builds.apache.org/view/Z/view/Zipkin/job/GH-incubator-zipkin/job/incubator-zipkin-website/job/master/8/console
> >
> > successfully updated the site (see
> >
> https://github.com/apache/incubator-zipkin-website/commit/339d065b306579a7fa10ca8493e401c0ea13bdb0
> ).
> > Verified the site actually picked up the changes within seconds, for
> > example "Server extensions and choices" is now showing up in the
> side-bar.
> > This _should_ mean that any future changes will also be automatically
> built
> > and published.
> > >
> > > ----------------------------------------------------------------
> > > This is an automated message from the Apache Git Service.
> > > To respond to the message, please log on to GitHub and use the
> > > URL above to go to the specific comment.
> > >
> > > For queries about this service, please contact Infrastructure at:
> > > [email protected]
> > >
> > >
> > > With regards,
> > > Apache Git Services
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to