I also proposed to move to git repositories and separate builds some
time ago.
So I fully support this. I think we have an agreement to move on a
subproject basis.
On the other hand we have some project with very low changes. I think
these could safely stay on svn for now.
So I would propose we move out the projects where most of the changes
happen.
A move to git is not a small task (at least if you also want to make the
project releaseable by subproject).
So I propose we start by creating separate builds from svn which should
be easier to achieve.
@Dominik:
Do you already have the rights to do changes on jenkins? I have the
rights but can not give other rights.
Christian
On 28.03.2017 19:25, Dominik Przybysz wrote:
Hi,
our build of Aries-Trunk-JDK17 has been red/yellow since about september
2016. It is about half of year. I think we should do something with this.
Aries components are disjoint and there is no value of build whole aries
project as one. I propose removing Aries-Trunk-JDK17 build and adding small
jobs for each components, e. g. jmx, jpa, blueprint, jndi, etc. Some
projects already have separate jenkins builds and this is great.
I also optionally propose splitting Aries repository to many small (git)
repositroies for each component of aries projects. Current aries repository
could be converted to git repository with only git submodules pointing to
these small aries repositories of single components.
WDYT?
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
