infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Rutkowski (JIRA)" <>
Subject [jira] [Commented] (INFRA-14124) Help wanted setup Github repo to deploy web site for OpenWhisk
Date Wed, 31 May 2017 14:03:04 GMT


Matt Rutkowski commented on INFRA-14124:

Why would we want a new repo.?  Since it does not seem viable that the (domain
name) will be paid for by Apache long term (as you indicated separately), why not just publish
from the current repo.?  Also, we should IMO evolve the current site into a community-centric
site (with all the expected Apache project links prominent) and less of a "marketing" site
as several people I came across at ApacheCon have dubbed it.  Plus we do not really need to
maintain 2 sites (as we are struggling with supporting 1 site); we should work to create a
site that serves both developer and user communities that can be jointly maintained.

> Help wanted setup Github repo to deploy web site for OpenWhisk
> --------------------------------------------------------------
>                 Key: INFRA-14124
>                 URL:
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Github
>            Reporter: Carlos Santana
> Hi I want to setup the repo and automation to publish the website for OpenWhisk on the
incubator website
> Talking to folks on hipchat @MCDuck Gavin McDonald
> I think what we want is the following:
> New repo on
> Will have two branches "master" and "asf-site"
> jekyll website source will be in master.
> Configure Jenkins to build the html static site when ever a new commits lands on master
> Jenkins will run on git-websites node and git push the changes to the asf-site
> When new commits arrive to branch asf-sitre gitpubsub integration will kick and publish
the new files to be available on
> --Carlos

This message was sent by Atlassian JIRA

View raw message