Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [IMPORTANT CHANGE] building and publishing our website from Jenkins and Git instead of CMS

FYI, switch is happening currently, I'm on HipChat with infra

then CMS does not have any effect now: this will be Jenkins job (or manual

please don't try to publish anything for now: I'll tell once everything is



Le vendredi 13 avril 2018, 18:15:21 CEST Karl Heinz Marbaise a écrit :

> Hi Hervé,
> On 12/04/18 08:17, Hervé BOUTEMY wrote:
> > Hi,
> >
> > I'm working with infra for a good time on Git migration for site source,
> > which will de-facto mean that we drop Apache CMS (that only supports svn
> > for source): see INFRA-16088 [1]
> >
> > Today, we got a first visible result: Jenkins was able to build and
> > publish
> > html output of the Maven main website to svn [2]
> >
> > We're now ready to switch to the new Jenkins build, then drop CMS: any
> > objection to do it?
> >
> > The plan will be then to switch source to GitBox, to benefit from
> > immediate
> > commit detection (instead of svn hourly polling): at this step, you'll be
> > able to do easy site source updates through GitHub, with immediate
> > publish. I don't see the value of adding a staging step, but if someone
> > wants staging, it will be a matter of Jenkinsfile tweaking.
> >
> > In the temporary time with Jenkins polling on source from svn , either
> > you'll wait for less than 1 hour or you'll manually launch the Jenkins
> > job
> >
> > any question?
> Jenkins will build the Site (as done before
> and deploys it to the site
> ( it's gets the source of the site from
> svn at the moment ?.
> If I wan't to publish it to live I have to go via
> as before (for now)...
> Kind regards
> Karl Heinz Marbaise

To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]