infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mck (JIRA)" <>
Subject [jira] [Commented] (INFRA-16996) Set up incubator-zipkin website via gitpubsub
Date Wed, 19 Sep 2018 02:18:00 GMT


mck commented on INFRA-16996:

I have created

> Set up incubator-zipkin website via gitpubsub
> ---------------------------------------------
>                 Key: INFRA-16996
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: GitBox, Github, Website
>            Reporter: Zoltán Nagy
>            Assignee: Chris Lambertus
>            Priority: Minor
> The Zipkin podling website is ready to be published. The site is currently hosted via
GitHub Pages + Jekyll from The generated
HTML site is in the `asf-site` branch (scripted, but CI automation pending the migration).
> Please
>  * Create a new GitBox repository (with GitHub primary) to host the site. I assume the
name would be {{incubator-zipkin-website}} by convention. (I tried to request a repo via,
but only “Your PMCs” shows up in the PMC list). I'll be happy to sync the history, no
real need to import it.
>  * Set up the webserver to listen to requests for as well. We currently terminate
HTTPS for the domain by routing through CloudFlare; can we keep that setup?
>  * Set up gitpubsub integration so that pulls from {{incubator-zipkin-website}}
branch {{asf-site}}.
>  * Advise what credentials should be used to automate generating the site from sources
and pushing to {{asf-site}}. I understand giving write access to dedicated automation accounts
can be problematic due to having no CLA. INFRA-14105 and INFRA-14124 seem to suggest using
Jenkins with the label {{git-websites}} is the way to go. Zipkin is not currently using Jenkins,
do you think we can get this working via Travis or Circle CI somehow?
> Incubator proposal:
> Incubator podling page:
> ---
> Details for context, thoughts from ASF Infra on how to do the migration better are appreciated.
> We started with two requirements: keep the downtime caused by the migration low, and
move the repo instead of creating the new one to preserve issues, stars, etc. Moving the repo
into the {{apache}} GitHub org causes downtime, since GitHub doesn't set up redirects when
transferring repositories. To mitigate that, the migration process would be a bit convoluted,
something along these lines:
>  * Get current site contents to _somehow_ (possibly via a temporary
repo and gitpubsub, but maybe just by an Infra member manually uploading the content)
>  * Switch the DNS to point to the ASF-hosted site
>  * Move and rename {{openzipkin/}} to be the ASF website repo
>  * Set up gitpubsub to pull from the new location
> Discussion on the zipkin-dev mailing list starts being relevant at
We settled on letting the current issues and stars go for a simpler setup process.

This message was sent by Atlassian JIRA

View raw message