Hi Vinoth I have created a jira for this https://issues.apache.org/jira/browse/HUDI-2070.
I can assign this to myself and start working on it. Regards, Navinder On Friday, 25 June, 2021, 12:23:26 am IST, Vinoth Chandar <vin...@apache.org> wrote: Hi Navinder, Our site is pushed from the asf-site branch and it has a README with building the site locally etc. that’s a good starting point. I don’t believe there is a open JIRA yet for this. On the example itself, I am not sure myself since this is new. So need to do some sluething and figure out. Please suggest next steps Thanks Vinoth On Thu, Jun 24, 2021 at 8:56 AM Navinder Brar <navinder_b...@yahoo.com.invalid> wrote: > Hi Vinoth, > > I can take this up. Is there any existing jira for this? Sorry I am new > new to Hudi community, if not I can clone an existing one. Please share a > sample. > > Thanks, > Navinder > > On Thursday, 24 June, 2021, 04:10:41 am IST, Vinoth Chandar < > vin...@apache.org> wrote: > > Hi all, > > Looks like this will apply to our site? Any volunteers to help fix this? > > Thanks > Vinoth > > ---------- Forwarded message --------- > From: Daniel Gruno <humbed...@apache.org> > Date: Mon, May 31, 2021 at 6:41 AM > Subject: [NOTICE] Git web site publishing to be done via .asf.yaml only as > of July 1st > To: Users <us...@infra.apache.org> > > > TL;DR: if your project web site is kept in subversion, disregard this > email please. If your project web site is using git, and you have not > deployed it via .asf.yaml, you MUST switch before July 1st or risk your > web site goes stale. > > > > Dear Apache projects, > In order to simplify our web site publishing services and improve > self-serve for projects and stability of deployments, we will be turning > off the old 'gitwcsub' method of publishing git web sites. As of this > moment, this involves 120 web sites. All web sites should switch to our > self-serve method of publishing via the .asf.yaml meta-file. We aim to > turn off gitwcsub around July 1st. > > > ## How to publish via .asf.yaml: > Publishing via .asf.yaml is described at: > https://s.apache.org/asfyamlpublishing > You can also see an example .asf.yaml with publishing and staging > profiles for our own infra web site at: > https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml > > In short, one puts a file called .asf.yaml into the branch that needs to > be published as the project's web site, with the following two-line > content, in this case assuming the published branch is 'asf-site': > > publish: > whoami: asf-site > > > It is important to note that the .asf.yaml file MUST be present at the > root of the file system in the branch you wish to publish. The 'whoami' > parameter acts as a guard, ensure that only the intended branch is used > for publishing. > > > ## Is my project affected by this? > The quickest way to check if you need to switch to a .asf.yaml approach > is to check out site source page at > https://infra-reports.apache.org/site-source/ - if your site is listed > in yellow, you will need to switch. This page will also tell you which > branch you are currently publishing as your web site. This is (should > be) the branch that you must add a .asf.yaml meta file to. > > The web site source list updates every hour. If your project site > appears in green, you are already using .asf.yaml for publishing and do > not need to make any changes. > > > ## What happens if we miss the deadline? > If you miss the deadline, don't fret. Your site will of course still > remain online as is, but new updates will not appear till you > create/edit the .asf.yaml and set up publishing. > > > ## Who do we contact if we have questions? > Please contact us at us...@infra.apache.org if you have any additional > questions. > > > With regards, > Daniel on behalf of ASF Infra. >
