[jbosstools-issues] [JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13242962#comment-13242962 ] 

Mickael Istria commented on JBIDE-22443:
----------------------------------------

{quote}If we wold have a build to verify PR's for jbosstools-target-platforms{quote}
You mean https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-target-platform-PRcheck/ ?

{quote} wouldn't a simple compile only build based on your old proposal on having a jenkins job running on a git submodules repo of all components been an excellent way to check this ? {quote}
It would be a good check, however we couldn't automate it as part the plain Maven build, because our submodules are downstream of TP and given a TP, it's not obvious what combination of submodules/branches we want to test.
The purpose of this change is to have something standalone that doesn't require any dependency on downstream jbosstools modules. It could also be used by Integration-Stack to try their TP as well.

> Add to TP build a check that produced TP can be installed in target Eclipse version
> -----------------------------------------------------------------------------------
>
>                 Key: JBIDE-22443
>                 URL: https://issues.jboss.org/browse/JBIDE-22443
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build, target-platform
>            Reporter: Mickael Istria
>
> Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests.
> This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible.
> Technical notes:
> * Trying to install all IUs from the release train site + our TP seems easier to implement
> * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)