You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@ofbiz.apache.org by jl...@apache.org on 2020/06/08 11:32:50 UTC
[ofbiz-tools] branch master updated: Updates wiki files
This is an automated email from the ASF dual-hosted git repository.
jleroux pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/ofbiz-tools.git
The following commit(s) were added to refs/heads/master by this push:
new 6ccc854 Updates wiki files
6ccc854 is described below
commit 6ccc854ff8dd70c09d0cdeb3afe9c5e73e8f4c12
Author: Jacques Le Roux <ja...@les7arts.com>
AuthorDate: Mon Jun 8 13:32:45 2020 +0200
Updates wiki files
---
wiki-files/BuildBot/BuildBot.md.html | 5 +++--
wiki-files/demos/README.md.html | 16 ++++++++++++++--
2 files changed, 17 insertions(+), 4 deletions(-)
diff --git a/wiki-files/BuildBot/BuildBot.md.html b/wiki-files/BuildBot/BuildBot.md.html
index 3bf540d..47c9d30 100644
--- a/wiki-files/BuildBot/BuildBot.md.html
+++ b/wiki-files/BuildBot/BuildBot.md.html
@@ -53,9 +53,10 @@ under the License.
<h2 id="handling-issues">Handling issues</h2>
<p>Sometimes (rarely) you can get transient tests errors in BuildBot. This mean tests don’t all pass in BuildBot, though they pass in your local instance. In such case, it’s most certainly an issue with servers. Those are hard workers and make errors from time to time, which shows that not only human make errors.</p>
<p>Before doing anything it’s best to check which BuildBot step is impacted, and if it exists have a look at the logfile (stdio)</p>
-<p>Some other errors may happen, like * svn not updating * upload not working * you name it…</p>
+<p>Some other errors may happen, like * Git not updating * upload not working * you name it…</p>
<p>In such case you can trigger a build from IRC to see if the problem resolves by itself. Most of the time tests and svn issues are resolved this way. If it does not then the best is to ask Infra help, either on <a href="https://apache.hipchat.com/chat/room/669587">HipChat infra room</a> or through the <a href="https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3">service desk</a></p>
-<p>When something like that happens, I get to IRC (using https://webchat.freenode.net). There using a recognisable username (I use jleroux) I get to the ofbiz channel. I wait for ofbiz-bot to appear, click on it, click on query and then I can make a request in the chat line to restart a scheduler. A request is of the form</p>
+<p>When something like that happens, I get to IRC (using https://webchat.freenode.net). There using a recognisable username (I use jleroux) I get to the ofbiz channel. I wait for ofbiz-bot to appear, click on it, click on query and then I can make a request in the chat line to restart a build.</p>
+<p>A request is of the form</p>
<pre><code>force build ofbizTrunkFramework</code></pre>
<p>you can put the text you want to appear in builder, after this expression, something like</p>
<pre><code>forces manual build after weird error</code></pre>
diff --git a/wiki-files/demos/README.md.html b/wiki-files/demos/README.md.html
index 8ee4128..6b0891c 100644
--- a/wiki-files/demos/README.md.html
+++ b/wiki-files/demos/README.md.html
@@ -20,8 +20,8 @@
<p>Three instances of OFBiz run on the OFBiz demo VM3 at https://ofbiz-vm3.apache.org.</p>
<ul>
<li>trunk: the trunk version</li>
-<li>stable: the last stable version (currently 16.11)</li>
-<li>old: the previous stable version (currently 13.07)</li>
+<li>stable: the last stable version (currently 17.12)</li>
+<li>old: the previous stable version (currently 16.11)</li>
</ul>
<p>This is the 3rd instance of VM we use hence the 3 in its domain name. The root of https://ofbiz-vm3.apache.org is the so called bigfiles directory which is actually at /var/www/ofbiz/big-files.</p>
<p>We own 3 Apache sub domains</p>
@@ -54,6 +54,18 @@ being run as - it should say ofbizDemo (UID).
Type 'exit' to exit the ofbizDemo user and return to your username.</code></pre>
<p>Also note that the demos are usually updated and started/stopped automatically using the check-svn-update.sh script in this directory. It is run by an ofbizDemo cron job every 24 hours at 3 AM. You should therefore only need to start/stop manually if there is a problem.</p>
+<h2 id="letsencrypt-certificate-update">Letsencrypt certificate update</h2>
+<p>Every 3 months we need to manually update our Letsencrypt certificate. It was automated before, it’s maybe again but I have no news about it. Anyway, it’s quite easy to do so. Simply connect to the demo VM and run</p>
+<pre><code>sudo certbot renew</code></pre>
+<p>I got this message today (2020-04-17):</p>
+<pre><code>Processing /etc/letsencrypt/renewal/ofbiz-vm3.apache.org.conf
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+Cert not yet due for renewal
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
+The following certs are not due for renewal yet:
+ /etc/letsencrypt/live/ofbiz-vm3.apache.org/fullchain.pem expires on 2020-06-08 (skipped)
+No renewals were attempted.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -</code></pre>
<h1 id="current-restriction">Current restriction</h1>
<p><del>If you want to restart only a single instance you can respectively use trunk-manual-nicely.sh stable-manual-nicely.sh old-manual-nicely.sh</del> This does not work, at least for instances using Gradle (currently trunk and stable, ie R16). See why at https://issues.apache.org/jira/browse/OFBIZ-10287 Hence currently R13.07 is not affected you can use <em>old-manual-nicely.sh</em> to only restart the old demo. And you need for now to use <em>all-manual-nicely.sh</em> when trunk or/a [...]
</body>