yeah. I try nvm in jenkins, but looks like it will install for current user (jenkins) and there are some limitations for global install (PR[1] raised to avoid global install).
I success using docker in apache jenkins to build htmls (refer to build url[2]) The only issue now is how to deploy change (or push changes back to asf-site branch), I already confirmed apache jenkins (node name 'git-website') have access to gitbox, but for github repo, still waiting Infra team to confirm. [1]: https://github.com/apache/dubbo-website/pull/378 [2]: https://builds.apache.org/job/Apache%20Dubbo/job/apache-dubbo-website-deployment/ Ian Luo <[email protected]> > Yunkun, > > The build for dubbo website requires particular node's version. If you want > to automate its build process, you need to consider to use 'nvm'. You can > find more details from website's README > > Thanks, > -Ian. > > > On Mon, May 27, 2019 at 11:01 AM YunKun Huang <[email protected]> wrote: > > > hey, > > > > I'm working on continuous deployment for Dubbo, and want to create a > > jenkins job for building & deploying dubbo-website for each commit. > > > > I think currently we are using some manual process, my understanding is > > > > 1. commit doc change to asf-site branch > > 2. someone will run `docsite build` to generate website and push to > > asf-site branch > > 3. upload new website to somewhere? (a static web server maybe?) > > > > My question is > > 1. for step 1 and step 2, should we keep source for website and generated > > files for website in two different branch > > 2. where do we host static files? in apache server? > > > > > > >
