> Maybe CMS commits in SVN on the same in the > background, but if it does then I can do the same in svn even better. yes
> Ideas? I tried to explain it in a simple way and with a figure in http://maven.apache.org/developers/website/deploy-maven-website.html the main thing is to understand that the CMS is an addition of 3 parts/steps: 1. online editing ("CMS edit"): here, like you found, you can edit on your local machine and commit, and you'll get exact same result 2. buildbot (could be called "CMS build"): launched automatically when source svn is modified (be it by CMS or local edit + commit), result (html content) is immediately visible in http://maven.staging.apache.org/ 3. CMS publish: when you hit https://cms.apache.org/maven/publish, html content is copied from staging area to production Perhaps you hit publish before buildbot published staging content, I don't really know what went wrong. Buildbot takes something like 30 seconds to build and stage And CMS publish takes a few seconds (now that we don't use extpaths.txt any more) I hope these explanations will help avoid CMS seen as magic black box. IMHO, if we didn't have the staging step, then require "CMS publish" action, everything would be more natural = publish html content when source is changed If we agree on this, I suppose we should be able to discuss with infra to drop this staging feature that is just not natural IMHO for our process Regards, Hervé Le dimanche 21 juin 2015 02:24:31 Tibor Digana a écrit : > Karl, > > Done. > The steps reflected my changes immediately on public page > http://maven.apache.org/shared/ > No more waiting one day for CMS job. Thanks. > > The only question, for next time release, is what happened after I went > through https://cms.apache.org/maven/publish > > 1. Did the publish take successful svn commit: > svn commit -m "Apache Maven Shared Utils 0.8 Released" > Authentication realm: <https://svn.apache.org:443> ASF Committers > Username: tibordigana > Password for 'tibordigana': ******** > Sending index.apt > Transmitting file data . > Committed revision 1686696. > > 2. or it took the CMS "Staged" from yesterday when I modified the index.apt > in browser Submitted and Staged. There's is document and video describing > how to use CMS bookmark. > > I would say the SVN is more natural way for me, and CMS is what did not work > for me however CMS told me that everything was successful. I was waiting 20 > hours after the CI should process CMS changes which should normally take > one day. What's wrong with the CMS? > It looks like CMS is official and everybody says use it, but it looks like > reality is different and we should commit in SVN like you described instead > of using CMS in browser. Maybe CMS commits in SVN on the same in the > background, but if it does then I can do the same in svn even better. > Ideas? > > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/RESULT-VOTE-Release-Apache-Maven-Shared-Ut > ils-version-0-8-tp5838056p5838243.html Sent from the Maven Developers > mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
