[JBoss JIRA] (JBTIS-27) migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-27?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-27:
----------------------------
Description:
Currently, we have 3 update sites being built which include tests, from various repos.
The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.
These test features are then composited, then aggregated into these sites:
http://download.jboss.org/jbosstools/updates/nightly/coretests/
http://download.jboss.org/jbosstools/updates/nightly/soatests/
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.
Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo:
*jbosstools-integration-stack-itests*
This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:
http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/
New update sites would presumably be here:
http://download.jboss.org/jbosstools/updates/nightly/integration-stack/ (need to migrate the build code and refactor the destination folder - see JBTIS-28)
http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
was:
Currently, we have 3 update sites being built which include tests, from various repos.
The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.
These test features are then composited, then aggregated into these sites:
http://download.jboss.org/jbosstools/updates/nightly/coretests/
http://download.jboss.org/jbosstools/updates/nightly/soatests/
http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.
Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo:
*jbosstools-integration-stack-itests*
This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:
http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/
New update sites would presumably be here:
http://download.jboss.org/jbosstools/updates/nightly/integration-stack/ (need to migrate the build code and refactor the destination folder)
http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
> migrate soa/brms tooling tests from jbosstools-integration-tests to new repo jbosstools-integration-stack-itests
> ----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-27
> URL: https://issues.jboss.org/browse/JBTIS-27
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Fix For: 4.0.0
>
>
> Currently, we have 3 update sites being built which include tests, from various repos.
> The most notable of these is jbosstools-integration-tests, which includes UI and integration tests (and framework code) for both the core and (JBT) the SOA/BRMS (JBTIS) projects. Additionally, the individual JBT and JBTIS project also publish test features/plugins to their respective update sites.
> These test features are then composited, then aggregated into these sites:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/
> http://download.jboss.org/jbosstools/updates/nightly/soatests/
> http://download.jboss.org/jbosstools/updates/nightly/integrationtests/
> Unfortunately, because of conflicting dependencies and version levels (soa is still on Juno, whereas core is on Kepler) not all tests can run against a single target platform/stack.
> Therefore, I propose we move the SOA/BRMS (JBTIS) tests into a new github repo:
> *jbosstools-integration-stack-itests*
> This would allow those tests to be build/run/published against the upstream JBTIS target platform and projects' test code, as well as incorporating shared code from the upstream core projects' tests (and framework code) published here:
> http://download.jboss.org/jbosstools/updates/nightly/coretests/4.0.juno/
> New update sites would presumably be here:
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack/ (need to migrate the build code and refactor the destination folder - see JBTIS-28)
> http://download.jboss.org/jbosstools/updates/nightly/integration-stack-it...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBTIS-28) migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-28:
----------------------------
Description:
JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
So, either you
* need to publish a site from which these can be resolved [1]
** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
* or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
[1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
[2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
[3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
[4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
Both options would work... but I suggest that building a new aggregate might be better.
If you agree, you'll want to therefore migrate the code in
https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat...
to a folder under
https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
was:
JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
So, either you
* need to publish a site from which these can be resolved [1]
** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
* or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
[1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
[2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
[3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
[4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
> migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-28
> URL: https://issues.jboss.org/browse/JBTIS-28
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, ESB, releng, target-platform
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Fix For: 4.0.0
>
>
> JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
> However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
> So, either you
> * need to publish a site from which these can be resolved [1]
> ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
> * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
> ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
> [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
> [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
> [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
> Both options would work... but I suggest that building a new aggregate might be better.
> If you agree, you'll want to therefore migrate the code in
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat...
> to a folder under
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBTIS-28) migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-28:
----------------------------
Summary: migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb... (was: migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb....)
> migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-28
> URL: https://issues.jboss.org/browse/JBTIS-28
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, ESB, releng, target-platform
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Fix For: 4.0.0
>
>
> JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
> However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
> So, either you
> * need to publish a site from which these can be resolved [1]
> ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
> * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
> ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
> [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
> [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
> [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBTIS-28) produce a JBTIS unit tests update site (aggregate or composite)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-28?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-28:
----------------------------
Summary: produce a JBTIS unit tests update site (aggregate or composite) (was: migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...)
> produce a JBTIS unit tests update site (aggregate or composite)
> ---------------------------------------------------------------
>
> Key: JBTIS-28
> URL: https://issues.jboss.org/browse/JBTIS-28
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution, ESB, releng, target-platform
> Affects Versions: 4.0.0
> Reporter: Nick Boldt
> Fix For: 4.0.0
>
>
> JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
> However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
> So, either you
> * need to publish a site from which these can be resolved [1]
> ** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
> * or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
> ** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
> [1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
> [2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
> [3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> [4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
> Both options would work... but I suggest that building a new aggregate might be better.
> If you agree, you'll want to therefore migrate the code in
> https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat...
> to a folder under
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years
[JBoss JIRA] (JBTIS-28) migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/soatests-site to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jbosstools/...
by Nick Boldt (JIRA)
Nick Boldt created JBTIS-28:
-------------------------------
Summary: migrate https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregat... to https://github.com/jbosstools/jbosstools-integration-stack/tree/master/jb....
Key: JBTIS-28
URL: https://issues.jboss.org/browse/JBTIS-28
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: distribution, ESB, releng, target-platform
Affects Versions: 4.0.0
Reporter: Nick Boldt
Fix For: 4.0.0
JBTIS-27 asks that the core and JBTIS integration tests (itests) be split into a new repo.
However, some of those itests depend on upstream tests unit tests (utests)... ESB, for example.
So, either you
* need to publish a site from which these can be resolved [1]
** :: more jobs to maintain, but will make downstream builds resolve p2 deps faster, and facilitate doing headless automated test plugin installation w/ install-grinder or p2.director
* or you need to ensure that when building/running the itests, you point at the composite JBTIS site [2].
** :: requires that you produce a folder somewhere on download.jboss.org, like this one [3], and maintain that composite site... since you can't link to a folder on raw.github.com [4]
[1] http://download.jboss.org/jbosstools/updates/nightly/soatests/
[2] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo...
[3] http://download.jboss.org/jbosstools/updates/integration/juno/integration...
[4] https://raw.github.com/jbosstools/jbosstools-integration-stack/master/jbo... is 404'd
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years