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 2021/12/31 09:44:06 UTC
[ofbiz-tools] branch master updated: Documented: misc. updates in BuildBot.md (OFBIZ-12456)
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 d4d3579 Documented: misc. updates in BuildBot.md (OFBIZ-12456)
d4d3579 is described below
commit d4d35796aeccc2b7353ebe52dd638276aba61d77
Author: Jacques Le Roux <ja...@les7arts.com>
AuthorDate: Fri Dec 31 10:44:23 2021 +0100
Documented: misc. updates in BuildBot.md (OFBIZ-12456)
Related to BuildBot migration from 0.8 to 3.2 version (INFRA-22279) and more.
---
documentation/BuildBot/BuildBot.md | 25 +++++++++++++------------
1 file changed, 13 insertions(+), 12 deletions(-)
diff --git a/documentation/BuildBot/BuildBot.md b/documentation/BuildBot/BuildBot.md
index 11d115c..6f99d41 100644
--- a/documentation/BuildBot/BuildBot.md
+++ b/documentation/BuildBot/BuildBot.md
@@ -22,29 +22,29 @@ There is also [a file in Git for project paths](https://github.com/apache/infras
## OFBiz and BuildBot
-[Here is the OFBiz BuildBot script](https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf). If you are interested on modifying it, please understand its content and read the BuildBot documentation. Note that the Infra team is always there to help you.
+[Here is the OFBiz BuildBot script (ofbiz.py)](https://svn.apache.org/repos/infra/infrastructure/buildbot2/projects). If you are interested on modifying it, please understand its content and read the BuildBot documentation. Note that the Infra team is always there to help you. If you modify ofbiz.py be sure to be subscribed to private@infra.apache.org before. It's where the syntax checker can help you in case of issues. I think that not everybody can be subscribed, at least ASF members, [...]
### Schedulers and Builders
BuildBot uses schedulers and builders. Schedulers decide which builders to trigger on Git commits.
-You can see the OFBiz builders and their states in the [common Buildbot waterfall view](https://ci.apache.org/waterfall) (look for "ofb").
+You can see the OFBiz builders and their states in the [common Buildbot builders view](https://ci2.apache.org/#/builders) (look for "ofb" or just scroll down).
-The [ofbizTrunkFramework](https://ci.apache.org/builders/ofbizTrunkFramework) builder is triggered on commits in the trunk framework branch. Then only the framework integration tests are run. This also triggers the [ofbizTrunkFrameworkPlugins](https://ci.apache.org/builders/ofbizTrunkFrameworkPlugins) if the build succeed. 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-frame [...]
+The ofbizTrunkFramework builder is triggered on commits in the trunk framework branch. Then only the framework integration tests are run. This also triggers the ofbizTrunkFrameworkPlugins if the build succeed. 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 component [...]
Of course a commit into the trunk plugins also triggers the ofbizTrunkFrameworkPlugins.
-The same apply to the [ofbizBranch17Framework](https://ci.apache.org/builders/ofbizBranch17Framework) and the [ofbizBranch17FrameworkPlugins](https://ci.apache.org/builders/ofbizBranch17FrameworkPlugins) and next releases branches, they follows the same structure than the trunk.
+The same apply to the current stable version (eg ofbizBranch18Framework and ofbizBranch18FrameworkPlugins) and next releases branches, they follows the same structure than the trunk.
-In an OFBiz builder page you can see [an history of the builds up to 100+](https://ci.apache.org/builders/ofbizTrunkFramework?numbuilds=100). OFBiz randomly uses 3 servers (except for RAT which always only uses asf945_ubuntu) to build. 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://ci2.apache.org/#/builders/49). You can see more by using [the settings page](https://ci2.apache.org/#/settings). You may want to explore more to get acquainted with the tool...
-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/site/trunk/rat-output.html). There are also RAT builders for the current [next](https://ci.apache.org/projects/ofbiz/site/next/rat-output.html) and [stable](https://ci.apache.org/projects/ofbiz/site/stable/rat-output.html) release branches.
+There is also the RAT builder. It checks the licenses in OFBiz. You can find the trunk results [here](https://ci.apache.org/projects/ofbiz/site/trunk/rat-output.html). There are also RAT builders for the next and stable release branches.
### tests results
-Here are the [test results](https://ci.apache.org/projects/ofbiz/logs/). The folders structure reflects the current Git repo structure.
+Here are the [trunk test results](https://nightlies.apache.org/ofbiz/trunk/tests-results/). You can find the same for the next and stable release branches.
### Technical information
-When you create a new branch you need to let know BuildBot about it. This because BuildBot uses Git hooks to triggers builds on commits. [The file to change is here](https://github.com/apache/infrastructure-p6/blob/production/modules/subversion_server/files/hooks/buildbot_project_paths). You can't clone, but you can make PRs inside it AIUI, via the github UI, just make a new branch and PR it.
+When you create a new branch you need to let know BuildBot about it. This because BuildBot uses Git hooks to triggers builds on commits. [The file to change is here](https://github.com/apache/infrastructure-p6/blob/production/modules/subversion_server/files/hooks/buildbot_project_paths). You can't clone, but you can make PRs via the github UI, just make a new branch and PR it.
## 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.
@@ -56,9 +56,9 @@ Some other errors may happen, like
* upload not working
* you name it...
-In such case you can trigger a build from IRC to see if the problem resolves by itself. Most of the time tests and G issues are resolved this way. If it does not then the best is to ask Infra help, either on [Infra Slack channel](https://the-asf.slack.com/archives/CBX4TSBQ8) or by creating an [Infra Jira issue](https://issues.apache.org/jira/projects/INFRA/summary).
+In such case you can trigger a build from IRC to see if the problem resolves by itself. Most of the time tests and issues are resolved this way. If it does not then the best is to ask Infra help, either on [Infra Slack channel](https://the-asf.slack.com/archives/CBX4TSBQ8) or by creating an [Infra Jira issue](https://issues.apache.org/jira/projects/INFRA/summary).
-+When something like that happens, I get to IRC (I use https://kiwiirc.com/nextclient/irc.freenode.net/#ofbiz, of course you can pick your own). There using a recognisable username (I use jleroux) I get to the ofbiz channel (#ofbiz, you are normally on it using the previous link). I wait for ofbiz-bot to appear in participant panel, click on it, click on query and then I can make a request in the chat line to restart a build.
+When something like that happens, I get to IRC (I use https://web.libera.chat/, of course you can pick your own). There using a recognisable username (I use jleroux) I get to the #ofbiz channel. I use ofbiz-bot to make a request in the chat line at bottom to restart a build.
A request is of the form
@@ -75,11 +75,12 @@ So the whole request is of the form
Note that with our last config (see [INFRA-15394](https://issues.apache.org/jira/browse/INFRA-15394)) the plugins builders are dependent and automatically launched by the framework 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 Git commit.
### Random 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 one of 3 the servers BuildBot uses for OFBiz, hence the random aspect. In such case we need to ask infra to manually disable Tomcat on this server. This happened 4th times already, last case was [INFRA-15829](https://issues.apache.org/jira/browse/INFRA-15829) where things are best explained.
+Though today (2021-12-31) this seems to not happen anymore, 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 one of 3 the servers BuildBot uses for OFBiz, hence the random aspect. In such case we need to ask infra to manually disable Tomcat on this server. This happened 4th times already, last case was [INFRA-15829](https://issues.apache.org/jira/browse/INFRA-15829) where things ar [...]
+
### Creating a new branch
1. Copy and adapt an existing branch scheduler and builder in [the OFBiz BuildBot script](https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/ofbiz.conf).
2. Ask Infra for a new directories structure for the tests (eg https://issues.apache.org/jira/browse/INFRA-17513)
-3. Adds the new branches [in the Git file for project paths](https://github.com/apache/infrastructure-p6/blob/production/modules/subversion_server/files/hooks/buildbot_project_paths). You can't clone, but you can make PRs inside it AIUI, via the github UI, just make a new branch and PR it.
+3. Adds the new branches [in the Git file for project paths](https://github.com/apache/infrastructure-p6/blob/production/modules/subversion_server/files/hooks/buildbot_project_paths). You can't clone, but you can make PRs via the github UI, just make a new branch and PR it.
4. Remove old branches if no longer supported.