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

Hi Hervé, I could imagine that it could still work. As far as I understand all the gitpubsub and svnpubsub, what generally happens, is that the HTTPD server serving a projects website is just a directory. And the pubsubs just pull changes from a source to the static files directory of the

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

On Fri 11 May 2018 at 09:37, Hervé BOUTEMY wrote: > Le vendredi 11 mai 2018, 01:45:29 CEST Stephen Connolly a écrit : > > On Thu 10 May 2018 at 23:51, Hervé BOUTEMY > wrote: > > > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > >

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

Le vendredi 11 mai 2018, 01:45:29 CEST Stephen Connolly a écrit : > On Thu 10 May 2018 at 23:51, Hervé BOUTEMY wrote: > > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site > >

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

Hi Christofer, Thanks for the sharing: the idea of building on any node, could be interesting in the future if we have performance issues with site commit-enabled nodes. Normally, these nodes are only used for site, which build is quite fast, so I'm not convinced there will be any issues in

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

Hi guys, just stumbled over this thread ... sorry for not noticing it earlier. As I did the same for several other projects here (Apache PLC4X probably being the most advanced site), I thought I might be able to help. When updating to GIT, why not also switch to GitPubSub? Also I just

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

On Thu 10 May 2018 at 23:51, Hervé BOUTEMY wrote: > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > > ob/master/1/console looks good. @Hervé can you delete > >

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

On Thu 10 May 2018 at 23:51, Hervé BOUTEMY wrote: > Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > > ob/master/1/console looks good. @Hervé can you delete > >

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

Le jeudi 10 mai 2018, 10:52:01 CEST Stephen Connolly a écrit : > https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/j > ob/master/1/console looks good. @Hervé can you delete > https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are > happy with it? great

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

Ahh no, https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-site/ is about publishing the maven core test results... we should see about folding that into the core Jenkinsfile with a condition on being master branch only On 10 May 2018 at 09:55, Stephen Connolly

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

https://builds.apache.org/view/M-R/view/Maven/job/maven-3.x-site/ seems like a dead job too On 10 May 2018 at 09:52, Stephen Connolly wrote: > https://builds.apache.org/view/M-R/view/Maven/job/maven- > box/job/maven-site/job/master/1/console looks good. @Hervé

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

https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven-site/job/master/1/console looks good. @Hervé can you delete https://builds.apache.org/view/M-R/view/Maven/job/maven-site/ if you are happy with it? On 10 May 2018 at 09:37, Stephen Connolly

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

On 10 May 2018 at 07:25, Hervé BOUTEMY wrote: > Le mercredi 9 mai 2018, 19:40:54 CEST Karl Heinz Marbaise a écrit : > > Hi, > > > > > > This means if you do a commit in the gitbox repository[1] the job[2] on > > our build server will start and deploy directly to production

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

Le mercredi 9 mai 2018, 19:40:54 CEST Karl Heinz Marbaise a écrit : > Hi, > > > This means if you do a commit in the gitbox repository[1] the job[2] on > our build server will start and deploy directly to production site[3] > without the need to public via cms[4]. yes, you get it > > > Great

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

Hi, This means if you do a commit in the gitbox repository[1] the job[2] on our build server will start and deploy directly to production site[3] without the need to public via cms[4]. Great work... BTW: @Hervé can you explain what is meant to write the Jenkinsfile to make a mvn

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

sites sources migration to Git at GitBox done: now you can edit Maven and Doxia sites directly from GitHub through the edit link The site build and publish Jenkins jobs are still the previous ones: if someone creates a Jenkinsfile, we'll have immediate build in maven-box job. Next step will be

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

Jira issue for source migration to Git opened: https://issues.apache.org/jira/browse/INFRA-16361 Regards, Hervé Le dimanche 15 avril 2018, 01:23:06 CEST Hervé BOUTEMY a écrit : > here it is, now Maven site and Doxia sub-site are published by Jenkins > > CMS is not used any more > We'll just

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

here it is, now Maven site and Doxia sub-site are published by Jenkins CMS is not used any more We'll just need to move components reference documentation out of the CMS svn space: I'll do it later with infra now, I'll work on GitBox migration If someone can write a Jenkinsfile, this would be

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 build) please don't try to publish anything for now: I'll tell once everything is stabilized Regards, Hervé Le vendredi 13 avril 2018, 18:15:21 CEST Karl

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

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

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

Hi, 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

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

w00t On Thu 12 Apr 2018 at 07: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

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

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