Confirm. It is just the at CMS had some nuts issue last night where the build for bigtop website didn't show up at all, but publishing worked just fine.
Anyway - it works for sure! Cos On Thu, Jan 22, 2015 at 12:02PM, Roman Shaposhnik wrote: > Just to close the loop on this from my side, here's what seems to be > working for me: > 1. mvn site-deploy > 2. wait some time > 3. push the staging to prod via https://cms.apache.org/bigtop/publish > > Seems to work like a charm and at this point I'm pretty convinced that > every Bigtop committer can do it. > > Thanks, > Roman. > > On Thu, Jan 22, 2015 at 12:00 PM, Konstantin Boudnik <[email protected]> wrote: > > Thanks Evans. Yup, that's what I found too - CMS works, although both of > > these > > are a bit suboptimal as it requires additional steps in the release flow. I > > guess we can live with this for now, unless someone has a better ideas on > > how > > to improve this without much hassle ;) > > > > Cos > > > > On Thu, Jan 22, 2015 at 09:03PM, Evans Ye wrote: > >> Hi cos, > >> ` > >> Glad you get the site updated. > >> > >> I think currently we have two options to update the bigtop website: > >> > >> 1) mvn site plugin (do not work for me) > >> I was struggling by using the mvn sit:deploy documented in How to release > >> <https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release>. > >> Roman tipped me that this may requires extra karma. > >> I think it's because this will directly upload the content up to the > >> directory located somewhere on [email protected], making additional > >> permission required. > >> > >> 2) CMS (need to commit to svn repo) > >> I was able to update the site by following the steps in Deploying Bigtop's > >> Apache Website > >> <https://cwiki.apache.org/confluence/display/BIGTOP/Deploying+Bigtop%27s+Apache+Website> > >> . > >> The staging site will be updated after the site builder finished its work > >> (triggered by svn commit). > >> Then a click on "publish bigtop site" will update the change up to > >> production. > >> > >> I've updated the wiki, so the CMS way should work:) > >> > >> > >> Evans > >> > >> > >> 2015-01-22 12:32 GMT+08:00 Konstantin Boudnik <[email protected]>: > >> > >> > Ok, please disregard this email - I need to learn how to be patient and > >> > finish > >> > reading 2-lines paragraph to the very end. Apparently, you have to click > >> > Publish link no matter that staging isn't showing correct content, nor > >> > staging > >> > builds reflect latest build. Arhg... I've updated the Wiki release page > >> > to > >> > emphasize the importance of that Publish link clicking... > >> > > >> > Hopefully it will put the matter at rest > >> > Cos > >> > > >> > On Wed, Jan 21, 2015 at 08:09PM, Konstantin Boudnik wrote: > >> > > Ok, looks like I am hitting a similar problem myself. CMS doesn't help > >> > much. > >> > > So, let's get down to it and get this crap fixed once and for all... I > >> > > am > >> > > getting annoyed with CMS and SVN and Git and other non-working or > >> > > non-documented ways of publish out website. > >> > > > >> > > Evans, I see that you were finally able to get the changes out - could > >> > you > >> > > please describe how it was done? Or better yet - create a wiki page > >> > > with > >> > that > >> > > info? > >> > > > >> > > Thanks! > >> > > Cos > >> > > > >> > > On Thu, Jan 08, 2015 at 05:24PM, Evans Ye wrote: > >> > > > My bad. Sorry for those annoying commits. > >> > > > > >> > > > I've tried the solution > >> > > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > >> > > > > >> > > > It looks like the way is to push site contents in our git repo > >> > directly up > >> > > > to www directory on people.apache.org. > >> > > > But I still can not successfully deploy the site. > >> > > > > >> > > > > >> > > > > >> > > > My first step is to disable skiDeploy: > >> > > > > >> > > > <artifactId>maven-site-plugin</artifactId> > >> > > > <version>3.3</version> > >> > > > <configuration> > >> > > > - <skipDeploy>true</skipDeploy> > >> > > > + <skipDeploy>false</skipDeploy> > >> > > > </configuration> > >> > > > > >> > > > > >> > > > > >> > > > Then the first issue I ran into was "Unsupported protocol: 'scm' for > >> > site > >> > > > deployment"; > >> > > > > >> > > > [root@localhost bigtop-site]# (master)$ mvn site:deploy > >> > > > > >> > > > [INFO] Scanning for projects... > >> > > > > >> > > > [INFO] > >> > > > > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > > >> > > > [INFO] Building Bigtop 0.9.0-SNAPSHOT > >> > > > > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > > >> > > > [INFO] > >> > > > > >> > > > [INFO] --- maven-site-plugin:3.3:deploy (default-cli) @ bigtop --- > >> > > > > >> > > > [INFO] Parent project loaded from repository: org.apache:apache:pom:8 > >> > > > > >> > > > [ERROR] > >> > > > > >> > > > Unsupported protocol: 'scm' for site deployment to > >> > > > distributionManagement.site.url=scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/. > >> > > > > >> > > > Currently supported protocols are: scpexe, http, https, file. > >> > > > > >> > > > Protocols may be added through wagon providers. > >> > > > > >> > > > For more information, see > >> > > > > >> > http://maven.apache.org/plugins/maven-site-plugin/examples/adding-deploy-protocol.html > >> > > > > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > > >> > > > [INFO] BUILD FAILURE > >> > > > > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > > >> > > > [INFO] Total time: 3.383s > >> > > > > >> > > > [INFO] Finished at: Thu Jan 08 08:36:07 UTC 2015 > >> > > > > >> > > > [INFO] Final Memory: 11M/86M > >> > > > > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > > >> > > > [ERROR] Failed to execute goal > >> > > > org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-cli) > >> > > > on > >> > > > project bigtop: Unsupported protocol: 'scm' for site deployment to > >> > > > distributionManagement.site.url=scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/. > >> > > > -> [Help 1] > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > So I added following extensions in the pom.xml to inculde scm plugin: > >> > > > > >> > > > + <extension> > >> > > > > >> > > > + <groupId>org.apache.maven.wagon</groupId> > >> > > > > >> > > > + <artifactId>wagon-scm</artifactId> > >> > > > > >> > > > + <version>2.8</version> > >> > > > > >> > > > + </extension> > >> > > > > >> > > > + <extension> > >> > > > > >> > > > + <groupId>org.apache.maven.scm</groupId> > >> > > > > >> > > > + <artifactId>maven-scm-manager-plexus</artifactId> > >> > > > > >> > > > + <version>1.5</version> > >> > > > > >> > > > + </extension> > >> > > > > >> > > > + <extension> > >> > > > > >> > > > + <groupId>org.apache.maven.scm</groupId> > >> > > > > >> > > > + <artifactId>maven-scm-provider-svnexe</artifactId> > >> > > > > >> > > > + <version>1.5</version> > >> > > > > >> > > > + </extension> > >> > > > > >> > > > + <extension> > >> > > > > >> > > > > >> > > > > >> > > > > >> > > > But later went into another issue that is "No such provider: 'svn'": > >> > > > > >> > > > [root@localhost bigtop-site]# (master)$ mvn site:deploy > >> > > > [INFO] Scanning for projects... > >> > > > [INFO] > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > [INFO] Building Bigtop 0.9.0-SNAPSHOT > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > [INFO] > >> > > > [INFO] --- maven-site-plugin:3.3:deploy (default-cli) @ bigtop --- > >> > > > [INFO] Parent project loaded from repository: org.apache:apache:pom:8 > >> > > > [WARNING] No SCM providers configured. > >> > > > scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/ > >> > - > >> > > > Session: Opened > >> > > > [INFO] Pushing /root/bigtop-site/target/site > >> > > > [INFO] >>> to scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/./ > >> > > > Transfer error: > >> > org.apache.maven.scm.manager.NoSuchScmProviderException: > >> > > > No such provider: 'svn'. > >> > > > scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/ > >> > - > >> > > > Session: Disconnecting > >> > > > scm:svn: > >> > > > > >> > https://svn.apache.org/repos/infra/websites/staging/bigtop/trunk/content/ > >> > - > >> > > > Session: Disconnected > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > [INFO] BUILD FAILURE > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > [INFO] Total time: 4.039s > >> > > > [INFO] Finished at: Thu Jan 08 08:43:28 UTC 2015 > >> > > > [INFO] Final Memory: 14M/86M > >> > > > [INFO] > >> > > > > >> > ------------------------------------------------------------------------ > >> > > > [ERROR] Failed to execute goal > >> > > > org.apache.maven.plugins:maven-site-plugin:3.3:deploy (default-cli) > >> > > > on > >> > > > project bigtop: Error uploading site: Error interacting with SCM: No > >> > such > >> > > > provider: 'svn'. -> [Help 1] > >> > > > > >> > > > > >> > > > > >> > > > Now I don't have solution for this yet. > >> > > > Roman could you help to check that this is only my environment > >> > > > problem > >> > or > >> > > > not? > >> > > > > >> > > > Thanks > >> > > > Evans > >> > > > > >> > > > 2015-01-08 4:01 GMT+08:00 Konstantin Boudnik <[email protected]>: > >> > > > > >> > > > > Hi Evans. > >> > > > > > >> > > > > I see three commits from your: > >> > > > > > >> > > > > > >> > ------------------------------------------------------------------------ > >> > > > > r1650116 | evansye | 2015-01-07 08:48:36 -0800 (Wed, 07 Jan 2015) | > >> > 1 line > >> > > > > > >> > > > > Add Evans Ye to the team list > >> > > > > > >> > ------------------------------------------------------------------------ > >> > > > > r1650085 | evansye | 2015-01-07 07:35:39 -0800 (Wed, 07 Jan 2015) | > >> > 1 line > >> > > > > > >> > > > > sync up svn site's release version to git repo > >> > > > > > >> > ------------------------------------------------------------------------ > >> > > > > r1650010 | evansye | 2015-01-07 00:31:26 -0800 (Wed, 07 Jan 2015) | > >> > 1 line > >> > > > > > >> > > > > Add Evans Ye to team list > >> > > > > > >> > > > > I think we've been following this document here > >> > > > > https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release > >> > > > > > >> > > > > check under "Build and Deploy Site" > >> > > > > > >> > > > > Roman, as you've have written the document Evans refers to - could > >> > you > >> > > > > please > >> > > > > comment if this is till relevant? I honestly am very confused about > >> > how > >> > > > > the sites are supposed to be managed in ASF. All the changes around > >> > CMS etc > >> > > > > are really driving me nuts. > >> > > > > > >> > > > > Thanks, > >> > > > > Cos > >> > > > > > >> > > > > On Thu, Jan 08, 2015 at 02:30AM, Evans Ye wrote: > >> > > > > > Hi bigtop, > >> > > > > > > >> > > > > > I was about to update my info on bigtop team list but got no > >> > > > > > luck. > >> > > > > > I followed the guide here: > >> > > > > > > >> > > > > > > >> > > > > > >> > https://cwiki.apache.org/confluence/display/BIGTOP/Deploying+Bigtop%27s+Apache+Website > >> > > > > > > >> > > > > > My local mvn site:run result was perfect, but when I went to > >> > update the > >> > > > > > bigtop svn repo, it looked like the svn repo is out-of-date > >> > > > > > since 2014-07-29. > >> > > > > > The production site updated on 2014-12-04 should be the same with > >> > bigtop > >> > > > > > git repo, but has many diff compared to svn repo. > >> > > > > > I'm wondering is there another way to update our website without > >> > going > >> > > > > > through https://cms.apache.org/bigtop ? > >> > > > > > Since the production site might not be generated from svn repo. > >> > > > > > > >> > > > > > If someone knows how to do that, please give me a hint. > >> > > > > > I can help to sync up the svn repo as long as it's the right way > >> > to go. > >> > > > > > If the document is out-of-date, too, I can update the document as > >> > well. > >> > > > > > >> > > >> > > >> >
