Yes. That's clear to me now. Thanks for the update. I checked the CI job and it looks good. Thanks!
Olaf Flebbe <[email protected]> 於 2020年9月22日 週二 上午1:44寫道： > Hi Evans, > > ok, let me explain it in detail: > > * The website was completly static content previously as well. > * I did not (until now) do any change to the pages. > * The website is build by running „mvn site“ in bigtop root. > * The target/site directory has to be put onto a webserver. > > The only thing what is changing is _how_ to put it on a webserver. > Previously bigtop used the maven site plugin to stage it to a CMS via svn. > See <distributionManagement> in pom.xml. > > The now preferred way is to check the html pages into the git repository > (rather svn) on a special branch "asf-site" , together with a file > „.asf.yaml“ in the root with special content. When we push it a special > handler (gitpubsub) is triggered to push the static content to the website. > > On builds.apache.org <http://builds.apache.org/> system this is done in > job „Bigtop/site“. Additionally there is a special node "git-websites“ > which will allow a Jenkins job to push to git, because git credentials are > already injected into the job by INFRA. > > That’s how to push to bigtop.apache.org <http://bigtop.apache.org/> > —— > > For testing purposes I pushed to bigtop.staged.apache.org < > http://bigtop.staged.apache.org/> via branch asf-staging and .asf.yaml , > but the mechanisms are the same. > > > Hope that clarifies the situation, > Olaf > > > > Am 21.09.2020 um 17:34 schrieb Evans Ye <[email protected]>: > > > > Hi Olaf, > > > > Thanks for the work! > > It seems the site code has changed quite a bit. Could you briefly share > > what changes were made? For example, it seems that the pages are all > static > > now. From the CI job it seems that jenkins slave provided by infra has > the > > permission to push to any git repository. Have we done something > > differently? Thanks! > > > > - Evans > > > > > > Olaf Flebbe <[email protected]> 於 2020年9月20日 週日 下午9:51寫道： > > > >> Hi *, > >> > >> Finally found time to look into implementing the workflow for pushing > our > >> website automatically bigtop.apache.org <http://bigtop.apache.org/>. > >> > >> As a test I create a job checkin the git repository once a day for new > >> commits an deploying to bigtop.staged.apache.org < > >> http://bigtop.staged.apache.org/> > >> > >> Please have a look if you see anything weird / unexpected on it and > report. > >> Changing the website is now as easy as having a git commit on src/site . > >> > >> If I get no or positive (gasp!) feedback I will change the job in a few > >> days to update the prod website instead > >> > >> Additional ideas : Using a jenkins pipeline job, refactor pom.xml to > >> remove now obsolete parts. > >> > >> Best > >> Olaf > >
