[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-dev] GeneratePomFileTest fails
|
I have good and bad news.
The good news, I remembered how it's supposed to work ;-) Main "tycho"
build *deploys* build results to repository.sonatype.org and
"tycho-its*" jobs resolve tycho artifacts from r.s.o. tycho-its* jobs
run on multiple systems, i.e. linux and windows, so sharing build
results via maven local repository was not an option. I am not too
familiar with r.s.o configuration, but I guess the setup has special
rules for groupdId=org.spnatype.* and does not work with Tycho new
groupId=org.eclipse.tycho.
The bad news... we will have to move tycho CI jobs to Eclipse Foundation
infrastructure. Sonatype wants to disable public access to its CI build
servers for various reasons. I can setup tycho CI job(s) on our
internal/closed servers for now, so we at least get new SNAPSHOT builds
published.
--
Regards,
Igor
On 11-04-18 05:51 PM, Igor Fedorenko wrote:
On 11-04-18 10:19 AM, Oberlies, Tobias wrote:
Oberlies, Tobias wrote:
One remaining problem is the integration test "GeneratePomFileTest"
(see attached log file). It fails because Maven fails to determine
the version of the maven-tycho-plugin. I guess that the problem
will disappear once we have org.eclipse.tycho deployed to a Maven
repository. But how should we handle this failure until then? Also
I have doubts that the test is correct, if it depends on what is
deployed rather than always testing what just has been built.
I just figured that this may even be a feature and not a bug: Maven
can't find the build plug-in in any of the configured
pluginRepositories and hence fails. It could be intentional, that
Maven doesn't use the plug-in that is only available in the local
Maven repository.
However I still ask myself if this means that the test verifies the
correct version of Tycho: a deployed snapshot or the one that has
just been built.
Yup. That's what I wonder too...
--
Regards,
Igor
