This is an automated email from the ASF dual-hosted git repository.
rzo1 pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tomee-site-generator.git
The following commit(s) were added to refs/heads/master by this push:
new e59374b Adds some notes regarding the automatic publishing via
Jenkins CI Removes legacy / outdated SVN publishing notes
e59374b is described below
commit e59374b921ef0ac5d40b59d2831fb78253c980a8
Author: Richard Zowalla <r...@apache.org>
AuthorDate: Wed May 26 11:12:32 2021 +0200
Adds some notes regarding the automatic publishing via Jenkins CI
Removes legacy / outdated SVN publishing notes
---
README.adoc | 24 +++---------------------
1 file changed, 3 insertions(+), 21 deletions(-)
diff --git a/README.adoc b/README.adoc
index 34ebc21..0ddf7c0 100755
--- a/README.adoc
+++ b/README.adoc
@@ -51,6 +51,7 @@ TIP: the rendering is just a main so if the process doesn't
work for you just en
== Extensions
Build will generate a PDF for each page containing the attribute
`jbake-tomeepdf`.
+**Note**: Currently, the PDF generation is disabled.
== Examples
@@ -71,24 +72,5 @@ Finally note that the site generation will rely on the cache
as well to generate
== Publish (needs an ASF account)
-- To publish the website, you have to add and push the related content to the
https://github.com/apache/tomee-site-pub[TomEE Site Pub] repository.
-
-== Legacy SVN Publish (not working anymore)
-
-`SvnPub` is a main to push to the staging the site content once built, you
need to set the system properties (or properties in ~/.m2/settings.xml)
-`site.password` to your asf password and `site.username` if you user name is
not `USER` environment variable for it to work.
-
-It will checkout/update the site from svn then copy the site folder from
target directory to synchronize it with the svn version
-and finally it will commit everything.
-
-You can set the system property `site.message` to not use the default commit
message.
-
-NOTE: `.content-site-checkout` will be the local copy of the website (if you
need to modify manually the files or delete some old ones.
-
-NOTE: if the process fails unexpectedly (wrong update in the logic or
anything) you can unlock the `.content-site-checkout` executing inside `svn
cleanup`.
-
-To build and deploy on staging at once: `mvn clean compile pre-site`.
-
-Then to deploy to "prod": go on https://cms.apache.org/tomee/publish and hit
"Submit" (note: you can review changes before if you want to check what the CMS
took as changes).
-
-TIP: the staging is available when
https://ci.apache.org/builders/tomee-site-staging build is done (triggered on
commit), you can't deploy before.
+- The website is automatically build and published to
https://github.com/apache/tomee-site-pub[TomEE Site Pub] by a
https://ci-builds.apache.org/job/Tomee/job/site-publish/[Jenkins build job]
every 12 hours.
+- The job can also be triggered manually via the Jenkins website.
\ No newline at end of file
