Re: Moving the website repo from svn to git

Thank you Vinod for driving this! The automatic updates are a huge improvement :) On Wed, Aug 9, 2017 at 1:49 PM, Vinod Kone wrote: > To close the loop on this, the website automation is now live! > > Any changes to the mesos repo will trigger the Mesos-Websitebot CI job

Re: Moving the website repo from svn to git

To close the loop on this, the website automation is now live! Any changes to the mesos repo will trigger the Mesos-Websitebot CI job that builds and publishes an updated website that gets reflected on http://mesos.apache.org Enjoy! On Tue, Jun 13, 2017 at 12:24 PM, Vinod Kone

Re: Moving the website repo from svn to git

Tim, with the 2 repo option, the idea is that the source of the website will still reside in the main repo even if we keep the publish contents in a different repo. @vinodkone > On Jun 1, 2017, at 8:42 PM, Timothy Anderegg > wrote: > > Just to chime in, I'm

Re: Moving the website repo from svn to git

Thanks for the analysis Benjamin. Really appreciate it. You bring up good points esp about size bump for supporting multiple versions. Btw, do the numbers change if publish content is only in a branch ? Guess not? Maybe we can start with a separate git repo and see if it's painful enough to

Re: Moving the website repo from svn to git

Hi Vinod, > *Implementation details: * > > We have an option to move to > 1) a standalone git repo (say "mesos-site") which will be mirrored on > github. > 2) just use our "mesos" git repo and publish a "asf-site" branch with > website contents (say at 'site/publish' directory) > > I'm leaning

Re: Moving the website repo from svn to git

So is the extra branch only used to limit the frequency that the bot sees new commits? Or to hide website publishing commits from the master branch? Trying to understand why we wouldn't include the publish directory directly in the master branch. On Thu, Jun 1, 2017 at 2:48 PM, Vinod Kone

Re: Moving the website repo from svn to git

On Thu, Jun 1, 2017 at 2:24 PM, Benjamin Mahler wrote: > Curious to know more about what 2) looks like. > We would be maintaining a remote branch called "asf-site", similar to how we maintain remote release branches (1.0.x etc) today. The only difference would be that this

Moving the website repo from svn to git

Hi folks, I propose that we move our website repo from svn to git. The main motivation for this is to automate the website building process! I know this has been a pain in the past for release managers. Moving to git allows us to leverage ASF