Author: jleroux
Date: Tue Jan 16 16:46:32 2018
New Revision: 1821267
URL: http://svn.apache.org/viewvc?rev=1821267&view=rev
Log:
Better phrasing
Modified:
ofbiz/tools/documentation/BuildBot/BuildBot.md
ofbiz/tools/wiki-files/BuildBot/BuildBot.md.html
Modified: ofbiz/tools/documentation/BuildBot/BuildBot.md
URL:
http://svn.apache.org/viewvc/ofbiz/tools/documentation/BuildBot/BuildBot.md?rev=1821267&r1=1821266&r2=1821267&view=diff
==============================================================================
--- ofbiz/tools/documentation/BuildBot/BuildBot.md (original)
+++ ofbiz/tools/documentation/BuildBot/BuildBot.md Tue Jan 16 16:46:32 2018
@@ -36,14 +36,14 @@ The same apply to the [ofbizBranch17Fram
The current stable branch R16.12 has only [one
builder](https://ci.apache.org/builders/ofbizBranch16). This will be gone in
future. All new releases needs 2 builders.
-In an OFBiz builder page you can see [an history of the builds up to
100+](https://ci.apache.org/builders/ofbizTrunkFramework). OFBiz randomly
(except for RAT which always only uses lares_ubuntu) uses 3 servers to build as
you can see at the bottom of this page. You may want to explore more to get
acquainted with the tool...
+In an OFBiz builder page you can see [an history of the builds up to
100+](https://ci.apache.org/builders/ofbizTrunkFramework). OFBiz randomly uses
3 servers (except for RAT which always only uses lares_ubuntu) to build as you
can see at the bottom of this page. You may want to explore more to get
acquainted with the tool...
-There is also the [RAT
builder](https://ci.apache.org/builders/ofbizTrunkFrameworkRat) which check the
licenses in OFBiz. You can find the result
[here](https://ci.apache.org/projects/ofbiz/rat-output.html)
+There is also the [RAT
builder](https://ci.apache.org/builders/ofbizTrunkFrameworkRat). It checks the
licenses in OFBiz. You can find the result
[here](https://ci.apache.org/projects/ofbiz/rat-output.html)
### tests results
Here are the [test results](ci.apache.org/projects/ofbiz/logs/)
-The folders structure [will soon be
updated](https://issues.apache.org/jira/browse/INFRA-15842) to reflect the new
svn repo structure.
+The folders structure [will soon be
updated](https://issues.apache.org/jira/browse/INFRA-15842) to reflect the
current svn repo structure.
### Technical information
When you create a new branch you need to let know BuildBot about it. This
because BuildBot uses svn hooks to triggers builds on commits. [The file to
change is
here](https://github.com/apache/infrastructure-puppet/blob/deployment/modules/subversion_server/files/hooks/buildbot_project_paths)
@@ -53,7 +53,7 @@ You can't make commit in infrastructure-
## Handling issues
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.
-Before being anything it's best to check which BuildBot step is impacted and
if it exists have a look at the logfile (stdio)
+Before doing anything it's best to check which BuildBot step is impacted, and
if it exists have a look at the logfile (stdio)
Some other errors may happen, like
* svn not updating
@@ -75,7 +75,7 @@ So the whole request is of the form
force build ofbizTrunkFramework forces manual build after weird error
-Note though that with our last config (see
[INFRA-15394](https://issues.apache.org/jira/browse/INFRA-15394)) the
ofbizTrunkFrameworkPlugins and ofbizBranch17FrameworkPlugins builders are
dependent and respectively automatically launched by the ofbizTrunkFramework
and ofbizBranch17Framework builders but only on commits. So if you use an IRC
command like `force build ofbizTrunkFramework` only this builder will be
launched not the dependent ofbizTrunkFrameworkPlugins. We can't call a sheduler
from IRC. It needs a svn commit.
+Note though that with our last config (see
[INFRA-15394](https://issues.apache.org/jira/browse/INFRA-15394)) the
ofbizTrunkFrameworkPlugins and ofbizBranch17FrameworkPlugins builders are
dependent and respectively automatically launched by the ofbizTrunkFramework
and ofbizBranch17Framework builders but only on commits. So if you use an IRC
command like `force build ofbizTrunkFramework` only this builder will be
launched not the dependent ofbizTrunkFrameworkPlugins. We can't call a
scheduler from IRC. It needs a svn commit.
### Randon conflicts on port 8080 during tests
One case which comes back from time to time is a conflit on port 8080 due to
the automatic startup of tomcat. It's due to security patches being applied on
Silvanus (one of 3 the servers BuildBot uses for OFBiz, hence the random
aspect, only Sylvanus is concerned). In such case we need to ask infra to
manually disable Tomcat on Silvanus. This happened 4th already, last case was
[INFRA-15829](https://issues.apache.org/jira/browse/INFRA-15829)) where things
are best explained.
\ No newline at end of file
Modified: ofbiz/tools/wiki-files/BuildBot/BuildBot.md.html
URL:
http://svn.apache.org/viewvc/ofbiz/tools/wiki-files/BuildBot/BuildBot.md.html?rev=1821267&r1=1821266&r2=1821267&view=diff
==============================================================================
--- ofbiz/tools/wiki-files/BuildBot/BuildBot.md.html (original)
+++ ofbiz/tools/wiki-files/BuildBot/BuildBot.md.html Tue Jan 16 16:46:32 2018
@@ -36,15 +36,15 @@ under the License.
<p>The <a
href="https://ci.apache.org/builders/ofbizTrunkFramework";>ofbizTrunkFramework</a>
builder is triggered on commits in the trunk framework branch. Then only the
framework integration tests are run. This also triggers the <a
href="https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins";>ofbizTrunkFrameworkPlugins</a>
and then the whole integration tests are run. To check that a commit in the
framework puts no regressions in plugins and especially because the
dependencies of ofbiz-framework without ofbiz-plugins is different from the
dependencies of ofbiz-framework + ofbiz-plugins (plugins components are Gradle
sub-projects). So testing needs to happen in both scenarios because you might
face library version bugs. Of course a commit into the trunk plugins also
triggers the ofbizTrunkFrameworkPlugins.</p>
<p>The same apply to the <a
href="https://ci.apache.org/builders/ofbizBranch17Framework";>ofbizBranch17Framework</a>
and the <a
href="https://ci.apache.org/builders/ofbizBranch17FrameworkPlugins";>ofbizBranch17FrameworkPlugins</a>
and next releases branches, they follows the same structure than the trunk
now.</p>
<p>The current stable branch R16.12 has only <a
href="https://ci.apache.org/builders/ofbizBranch16";>one builder</a>. This will
be gone in future. All new releases needs 2 builders.</p>
-<p>In an OFBiz builder page you can see <a
href="https://ci.apache.org/builders/ofbizTrunkFramework";>an history of the
builds up to 100+</a>. OFBiz randomly (except for RAT which always only uses
lares_ubuntu) uses 3 servers to build as you can see at the bottom of this
page. You may want to explore more to get acquainted with the tool...</p>
-<p>There is also the <a
href="https://ci.apache.org/builders/ofbizTrunkFrameworkRat";>RAT builder</a>
which check the licenses in OFBiz. You can find the result <a
href="https://ci.apache.org/projects/ofbiz/rat-output.html";>here</a></p>
+<p>In an OFBiz builder page you can see <a
href="https://ci.apache.org/builders/ofbizTrunkFramework";>an history of the
builds up to 100+</a>. OFBiz randomly uses 3 servers (except for RAT which
always only uses lares_ubuntu) to build as you can see at the bottom of this
page. You may want to explore more to get acquainted with the tool...</p>
+<p>There is also the <a
href="https://ci.apache.org/builders/ofbizTrunkFrameworkRat";>RAT builder</a>.
It checks the licenses in OFBiz. You can find the result <a
href="https://ci.apache.org/projects/ofbiz/rat-output.html";>here</a></p>
<h3 id="tests-results">tests results</h3>
-<p>Here are the <a href="ci.apache.org/projects/ofbiz/logs/">test results</a>
The folders structure <a
href="https://issues.apache.org/jira/browse/INFRA-15842";>will soon be
updated</a> to reflect the new svn repo structure.</p>
+<p>Here are the <a href="ci.apache.org/projects/ofbiz/logs/">test results</a>
The folders structure <a
href="https://issues.apache.org/jira/browse/INFRA-15842";>will soon be
updated</a> to reflect the current svn repo structure.</p>
<h3 id="technical-information">Technical information</h3>
<p>When you create a new branch you need to let know BuildBot about it. This
because BuildBot uses svn hooks to triggers builds on commits. <a
href="https://github.com/apache/infrastructure-puppet/blob/deployment/modules/subversion_server/files/hooks/buildbot_project_paths";>The
file to change is here</a> You can't make commit in infrastructure-puppet if
you are not an infra committer. So you need to clone the repo and make a Pull
Request.</p>
<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 being anything it's best to check which BuildBot step is impacted
and if it exists have a look at the logfile (stdio)</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>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>
@@ -53,7 +53,7 @@ under the License.
<pre><code>forces manual build after weird error</code></pre>
<p>So the whole request is of the form</p>
<pre><code>force build ofbizTrunkFramework forces manual build after weird
error</code></pre>
-<p>Note though that with our last config (see <a
href="https://issues.apache.org/jira/browse/INFRA-15394";>INFRA-15394</a>) the
ofbizTrunkFrameworkPlugins and ofbizBranch17FrameworkPlugins builders are
dependent and respectively automatically launched by the ofbizTrunkFramework
and ofbizBranch17Framework builders but only on commits. So if you use an IRC
command like <code>force build ofbizTrunkFramework</code> only this builder
will be launched not the dependent ofbizTrunkFrameworkPlugins. We can't call a
sheduler from IRC. It needs a svn commit.</p>
+<p>Note though that with our last config (see <a
href="https://issues.apache.org/jira/browse/INFRA-15394";>INFRA-15394</a>) the
ofbizTrunkFrameworkPlugins and ofbizBranch17FrameworkPlugins builders are
dependent and respectively automatically launched by the ofbizTrunkFramework
and ofbizBranch17Framework builders but only on commits. So if you use an IRC
command like <code>force build ofbizTrunkFramework</code> only this builder
will be launched not the dependent ofbizTrunkFrameworkPlugins. We can't call a
scheduler from IRC. It needs a svn commit.</p>
<h3 id="randon-conflicts-on-port-8080-during-tests">Randon conflicts on port
8080 during tests</h3>
<p>One case which comes back from time to time is a conflit on port 8080 due
to the automatic startup of tomcat. It's due to security patches being applied
on Silvanus (one of 3 the servers BuildBot uses for OFBiz, hence the random
aspect, only Sylvanus is concerned). In such case we need to ask infra to
manually disable Tomcat on Silvanus. This happened 4th already, last case was
<a href="https://issues.apache.org/jira/browse/INFRA-15829";>INFRA-15829</a>)
where things are best explained.</p>
</body>
