Hi, Philip,
Your guess is not wrong. The Core Gerrit job runs the Tooling tests to ensure that changes in the Core don’t break Tooling. Ideally, it would run the tests as previously built by the main Tooling build job, so that it would not have to build them itself and thereby find your new test class. However, our builds do not publish their tests in p2 repositories and so you get what you’re seeing.
I think it would be best to actually publish the tests in a separate p2 repository in every main build’s Hudson archive so that dependent builds can find and run those tests. This should be quite simple to do, especially as the only build that (currently) publishes its output to the download server is the Product build.
In the mean time, you could work around this by putting your tooling changes in a separate Gerrit patch and merging it to master before proceeding with your Core changes?
On 24 November, 2016 at 04:58:52, Philip Langer (planger@xxxxxxxxxxxxxxxxx) wrote:
Hi everyone,
I have a question about the Papyrus-RT-Gerrit-Core job,
because we are having problems with the build of a change [1]. It
looks like this job builds the tooling tests, but doesn't rebuild
the tooling plug-ins (see a snippet of the console output
below):
[INFO] Reactor Build Order:
[INFO]
[INFO] Papyrus RT
[INFO] Papyrus RT Target Platforms
[INFO] org.eclipse.papyrusrt.targetplatform.neon.rt.included
[INFO] Core
[INFO] org.eclipse.papyrusrt.core
[INFO] org.eclipse.papyrusrt.umlrt.system.profile
[INFO] org.eclipse.papyrusrt.umlrt.core
[INFO] org.eclipse.papyrusrt.umlrt.core.sync
[INFO] org.eclipse.papyrusrt.umlrt.core.validation
[INFO] org.eclipse.papyrusrt.umlrt.system.profile.validation
[INFO] org.eclipse.papyrusrt.umlrt.core.feature
[INFO] org.eclipse.papyrusrt.core.core.p2
[INFO] org.eclipse.papyrusrt.core.tests
[INFO] org.eclipse.papyrusrt.junit
[INFO] org.eclipse.papyrusrt.umlrt.core.tests
[INFO] org.eclipse.papyrusrt.umlrt.core.validation.tests
[INFO] org.eclipse.papyrusrt.tooling.tests
[INFO]
org.eclipse.papyrusrt.umlrt.tooling.diagram.common.tests
[INFO] org.eclipse.papyrusrt.umlrt.tooling.ui.tests
[INFO] org.eclipse.papyrusrt.umlrt.tooling.types.tests
[INFO] org.eclipse.papyrusrt.umlrt.tooling.compare.tests
[INFO]
org.eclipse.papyrusrt.umlrt.tooling.diagram.statemachine.tests
[INFO]
org.eclipse.papyrusrt.umlrt.tooling.modelexplorer.tests
[INFO] org.eclipse.papyrusrt.migration.tests
[INFO] org.eclipse.papyrusrt.umlrt.migration.rsa.tests
If this is correct, we run into a problem, because when we add
a class in a tooling plug-in and use this class in a test, the new
class cannot be resolved, at least that's what the console output
of [1] says... but I might be wrong with my guess.
Thanks a lot for your help in advance!
Best wishes,
Philip
[1]
https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Gerrit-Core/162/consoleFull
--
Philip Langer
Senior Software Architect / General Manager
EclipseSource Services GmbH
_______________________________________________
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
|
