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
commit bd3b3e418cc1139f8a7599117defebf3f16bfcd9 Author: Jacques Le Roux <[email protected]> AuthorDate: Fri Jul 3 12:08:36 2020 +0200 Improved: Updates the doc, notably links but not only --- documentation/BuildBot/BuildBot.md | 37 +++++++++++++++++-------------------- 1 file changed, 17 insertions(+), 20 deletions(-) diff --git a/documentation/BuildBot/BuildBot.md b/documentation/BuildBot/BuildBot.md index 761ea2f..11d115c 100644 --- a/documentation/BuildBot/BuildBot.md +++ b/documentation/BuildBot/BuildBot.md @@ -18,37 +18,33 @@ under the License. --> ## What is BuilbBot and why using it? OFBiz uses [BuilbBot](https://en.wikipedia.org/wiki/Buildbot) as its Continuous Integration (CI) tool. There are other CI tools [used at the ASF](https://ci.apache.org/). +There is also [a file in Git 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. More information about creating a new branch below. ## 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. -There is also [a file in Git for project paths](C:\projectsASF\infrastructure-puppet\modules\subversion_server\files\hooks\buildbot_project_paths "buildbot_project_paths"). - ### Schedulers and Builders -BuildBot uses schedulers and builders. Schedulers decide which builders to trigger on svn commits. +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"). -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) 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 ofbi [...] -Of course a commit into the trunk plugins also triggers the ofbizTrunkFrameworkPlugins. +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 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 now. +Of course a commit into the trunk plugins also triggers the ofbizTrunkFrameworkPlugins. -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. +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. -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... +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... -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) +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. ### tests results -Here are the [test results](https://ci.apache.org/projects/ofbiz/logs/). The folders structure reflects the current svn repo structure. +Here are the [test results](https://ci.apache.org/projects/ofbiz/logs/). The folders structure reflects the current Git 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) -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. - +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. ## 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. @@ -60,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 svn issues are resolved this way. If it does not then the best is to ask Infra help, either on [HipChat infra room](https://apache.hipchat.com/chat/room/669587) or through the [service desk](https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3) +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). -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 (#ofbiz). 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://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. A request is of the form @@ -76,13 +72,14 @@ 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 schedu [...] +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. -### 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. +### 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. -### Adding a new branch +### 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](C:\projectsASF\infrastructure-puppet\modules\subversion_server\files\hooks\buildbot_project_paths "buildbot_project_paths"). +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. +4. Remove old branches if no longer supported.
