Le dimanche 11 février 2018, 11:51:25 CET sebb a écrit : > On 11 February 2018 at 09:47, Hervé BOUTEMY <[email protected]> wrote: > > Le dimanche 11 février 2018, 01:42:30 CET sebb a écrit : > >> On 10 February 2018 at 21:46, Hervé BOUTEMY <[email protected]> wrote: > >> > Hi, > >> > > >> > Is is possible to add notes on publishing to svnpubsub from Jenkins, > >> > please? > >> > > >> > Gitpubsub is perfect for sites that are build from only one Git repo. > >> > But when a site mixes content from many repositories (like a main site > >> > + > >> > one site per component release), svnpubsub is more suited > >> > >> I'm curious - why is that? > > > > The Maven http://maven.apache.org/ website is composed from: > > - a main content, > > - multiple components reference documentation, published for each > > component release > > > > Currently everything is in svnpubsub, and I'll try to explain why: > > - main content is in > > https://svn.apache.org/repos/infra/websites/production/maven/content/ - > > components reference documentation are in > > https://svn.apache.org/repos/infra/websites/production/maven/components/ > > And to be complete on how it works, there are some symbolic links from > > main content to components > > > > Main content size is classical: would perfectly fit a branch in Git repo, > > then gitpubsub. Each component reference documentation size is classical: > > would be possible also But the issue is that: > > 1. we have ~ 100 components > > 2. for each component, we want to publish simultaneously multiple releases > > see for example > > https://svn.apache.org/repos/infra/websites/production/maven/components/p > > lugins-archives/ > > > > The full content would not fit a single Git repo. > > Not sure what you mean by 'fit' here. The word has more than one meaning. > > Does it mean it's not suitable for Git, or does it mean the content is > too large for a Git repo? second option: would be too large
> > > And instructions for a component to publish its generated html to main > > site Git repo would download everything and checkout everything: would > > not be easy for one to have everything on his computer. With svn & > > svnpubsub, only one component documentation is checked out at a time > > (<id>-LATEST) and svnmucc commands manage the integration directly on the > > svn server. > > > > Please have a look at http://maven.apache.org/developers/website/ for > > details. > Thanks for the info. > > > Regards, > > > > Hervé
