Hi,
I wasn't aware that you are terminating the usage of the CMS sorry for
this noise...so [4] is done.
But I'm not sure why?
Just using the check-in on the site source will be built by
https://ci.apache.org/builders/creadur-site-staging/ and
you can preview the site on https://creadur.staging.apache.org/ and if
you like to publish to life site simply do a publish
(cms.apache.org/creadur/publish)... You don't need to use the cms itself
which I don't like too... On the other hand the VOTE seemed not finished
yet...
With [2] you have started to request informations to use the gitpubsub
or svnpubsub but not yet decided if you need a site for the overall project
creadur-site.git
or only for the RAT part..
creadur-rat-site.git
Based on [1] the content needed to be kept in SVN branch...and will be
replicated to the git site...
Should I request the https://reporeq.apache.org/ the repo ? for the
whole creadur-site.git ?
[1]: http://www.apache.org/dev/project-site.html#generated
[2]: https://issues.apache.org/jira/browse/INFRA-12231
[4]: https://issues.apache.org/jira/browse/INFRA-12528
On 30/08/16 23:45, Karl Heinz Marbaise wrote:
Hi,
I'm just curious why the staging site[1].
is more up-to-date ((Release 0.12 is on this page)
than the main site[2] and why the site build [3] is not working ?
Unmergeable scheduling requested on an entry: Can't add
'/usr/local/websites/creadur/trunk/content/rat/apache-rat/jira-report.html'
to a parent directory scheduled for deletion at
/usr/local/cms/build/lib/ASF/SVNUtil.pm line 69
For the later I have created an INFRA[4] ticket
Apart from that is there a simple way to publish from the staging site
to production (In Maven we have: https://cms.apache.org/maven/publish)
to publish from staging to production...
Kind regards
Karl Heinz
[1]: http://creadur.staging.apache.org/
[2]: http://creadur.apache.org/
[3]: https://ci.apache.org/builders/creadur-site-staging/
[4]: https://issues.apache.org/jira/browse/INFRA-12528
