[jbosstools-issues] [JBoss JIRA] (JBIDE-20394) jbosstools integration tests site depends on itself to build; site is not self-cleaning
Martin Malina (JIRA)
issues at jboss.org
Tue Jul 28 10:22:05 EDT 2015
[ https://issues.jboss.org/browse/JBIDE-20394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13093478#comment-13093478 ]
Martin Malina commented on JBIDE-20394:
---------------------------------------
[~nickboldt], yes, using the already existing hudson profile seems like a better option. In the hudson profile, we would effectively duplicate the jbosstools-site repo definition which has zero effect, is that what you mean? Can you add that to the PR if that's not a bother? I would do it myself if I could ;)
Just:
{code}
<profiles>
<profile>
<id>hudson</id>
<properties>
<jbosstools-integrationtests-site>${jbosstools-site}</jbosstools-integrationtests-site>
</properties>
</profile>
</profiles>
{code}
That should do the trick?
> jbosstools integration tests site depends on itself to build; site is not self-cleaning
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-20394
> URL: https://issues.jboss.org/browse/JBIDE-20394
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, integration-platform
> Affects Versions: 4.3.0.Beta2
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> I've found some problems today:
> 1. building JBT integration tests requires the JBT integration tests site [circular dependency]
> {code}
> [INFO] Adding repository http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3.mars
> {code}
> 2. nightly 4.3.mars site [0] contains both Beta2 and CR1 bits, even though it's just the 4.3.mars site and should therefore only have Beta2 bits (CR1 should only be in master site [1]
> [0] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3.mars/
> [1] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/master/
> 3. each time a new build is published into /updates/ [2], [3] it does NOT clean out the old releases, so the site is unnecessarily cluttered with old, orphan artifacts.
> [2] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-tests/4.3.mars/
> [3] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-tests/master/
> 4. The above sites [2], [3] contain content from BOTH branches, which is why we have artifacts from B440 (master) and B25 (4.3.mars) at the same time.
> 5. The check that the build does to determine if it should publish the new bits is failing to find the check script.
> 6. There are two different URLs [0], [2] being used for publishing bits, but the contents appear to be identical.
> [0] http://download.jboss.org/jbosstools/mars/snapshots/updates/integration-tests/4.3.mars/
> [2] http://download.jboss.org/jbosstools/updates/nightly/integrationtests/4.3.mars/
> This is because we have symlinks:
> {code}
> updates/nightly/integrationtests/4.3.mars -> ../../../mars/snapshots/updates/integration-tests/4.3.mars/
> updates/nightly/integrationtests/master -> ../../../mars/snapshots/updates/integration-tests/master/
> {code}
> So this is OK but we should migrate to use the new correct URLs instead of the old ones.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the jbosstools-issues
mailing list