Thanks for the responses.
The problem of triggering the Product build on Tooling-only changes is, of course, an orthogonal one. The Hudson Join Plug-in that we are using to avoid redundant builds of the Product when components higher up the dependency lattice (Core, Profile) are built has this unfortunate limitation. To address it, we would have to look for an update of this plug-in that fixes the problem, look for a better plug-in, create our own plug-in (!), or else look for another build dependency strategy.
For the disk usage problem, to avoid going back to a shared repository (I prefer not to, not just because of the concerns raised by Camille) I did prepare an implementation of regular private maven repository clean-up:
https://git.eclipse.org/r/#/c/99537/
Review and feed-back are welcome. It seems to work (I tested it in a feature branch build job and, of course, in the Releng Gerrit job) but perhaps there is a better way to achieve the same result, that I have not seen.
On Jun 19, 2017, 04:24 -0400, Camille Letavernier <cletavernier@xxxxxxxxxxxxxxxxx>, wrote:
Hi,
You need to be careful with shared repositories, as sometimes, Tycho will resolve artifacts in the repo (If they can't be found in the current reactor). This can lead to false positive or false negative builds, especially when dependencies are loosely specified and you use the same shared repo for, say, Neon and Oxygen (It's less likely to be an issue in a pure-Oxygen repo).
(Note that Tycho behavior may have changed since I observed this. Especially, we didn't use target platforms at this time - maybe it's a little bit more strict, now that we do, as we should have less "lazy" resolution - hopefully)
Camille
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
