Le 13/02/2017 à 10:56, Jacques Le Roux a écrit :
I have an idea for that: we create a copy of the trunk in a BuildBot special
branch, say ofbiz-framework-buildbot
This branch must never be used to commit directly (we can always revert in case)
This branch has svn:externals for plugins installed has described previously
In Buildbot, we no longer build the trunk framework and plugins.
But, on a svn commit in ofbiz-framework, or in the ofbiz-plugins, we merge the
commit in ofbiz-framework-buildbot and we run the tests and the rest
I have though still to figure out how to trigger a build on a commit external to this branch, and even if it's possible...
Good news, my Buildbot trick works:
https://ci.apache.org/builders/ofbiz-trunk-framework/builds/3
<https://ci.apache.org/builders/ofbiz-trunk-framework/builds/3>
https://ci.apache.org/builders/ofbiz-trunk-plugins/builds/1
I need to update the snapshots page again by adding the new archive. I'm waiting for a Puppet-Github pull request after cleaning
https://github.com/apache/infrastructure-puppet/pull/180
Actually the trick is to have a ofbiz-framework-buildbot branch which is only constituted of svn:externals. So no need to worry about updating,
merging it, etc.
This branch has a prominent file named "ONLY FOR BUILDBOT TESTS DON'T USE FOR
DEVELOPEMENT" to make things clear
We now just need INFRA-13496 to be fixed :) (the port 8080 issue again)
Have a nice day
Jacques
