[JBoss JIRA] (JBIDE-10670) JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build
8:49 a.m.
Nick Boldt created JBIDE-10670:
----------------------------------
Summary: JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
See TODO in
http://anonsvn.jboss.org/repos/jbosstools/trunk/build/aggregate/soa-site/...
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:58 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
As discussed via chat, sounds like the best option here is to depend on the composite
staging site from the previous milestone.
Thus, to override this value in trunk's parent pom:
{code}
<jbosstools-nightly-staging-composite>http://download.jboss.org/jbossto...
{code}
We need to set this in the jobs:
{code}
-Djbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
{code}
And we need to couple your _trunk jobs to the upstream _stable_branch jobs instead of the
_trunk ones.
Eg.,
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.ag...
should depend on upstream
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggreg...
instead of
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.aggregate/
similarly for esb:
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indig...
should depend on
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compon...
(and so on for common, jst, tests, usage components)
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:50 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10670:
---------------------------------------------
what I dont get is why we can't have SOA builds just depend on aggregate site and
integrate often that way ?
Building of latest milestone is fine for non-development-cycles, but that isn't where
we are at now.
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
Yeah, that's another option. Have soa tooling components and aggregate depend on
upstream nightly core site, instead of the upstream components / composite staging site.
Therefore instead of
<jbosstools-nightly-staging-composite>http://download.jboss.org/jbossto...
we'd use
<jbosstools-nightly-staging-composite>http://download.jboss.org/jbossto...
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10670 at 2/10/12 10:47 AM:
--------------------------------------------------------------
I've added this to the JBT SOA aggregate job - need to now roll it out to the various
components too.
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-46-15/config.xml
@@ -101,106 +99,106 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
was (Author: nickboldt):
I've added this to the JBT SOA aggregate job - need to now roll it out to the
various components too.
# use latest upstream nightly Core update site instead of "wild components" in
the composite staging site
jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-46-15/config.xml
@@ -101,106 +99,106 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:48 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
I've added this to the JBT SOA aggregate job - need to now roll it out to the various
components too.
# use latest upstream nightly Core update site instead of "wild components" in
the composite staging site
jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-46-15/config.xml
@@ -101,106 +99,106 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:02 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10670 at 2/10/12 11:02 AM:
--------------------------------------------------------------
Added to the following job:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.a...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-01_22-41-53/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-10_11-01-14/config.xml
@@ -65,72 +65,70 @@
</hudson.model.ChoiceParameterDefinition>
</parameterDefinitions>
</hudson.model.ParametersDefinitionProperty>
- <hudson.plugins.disk__usage.DiskUsageProperty/>
- <hudson.plugins.build__publisher.ExternalProjectProperty/>
</properties>
<scm class="hudson.scm.SubversionSCM">
<locations>
@@ -107,112 +105,112 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>aggregate/soa-site/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
and to
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-t...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-09_22-33-24/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-10_11-01-11/config.xml
@@ -112,118 +111,121 @@
# define correct URLs for upstream M5 bits
jbosstools-target-site=http://download.jboss.org/jbosstools/updates/targe...
local.site=/home/hudson/static_build_env/jbds/target-platform_3.3.indigo/e371-wtp331.target/
-jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
+# use latest upstream nightly Core update site instead of "wild
components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/
+#jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
local.composite=file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/3.3.indigo/
jboss-requirements-composite-mirror=http://download.jboss.org/jbosstools/...
jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
{code}
was (Author: nickboldt):
I've added this to the JBT SOA aggregate job - need to now roll it out to the
various components too.
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-01-31_15-16-12/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/devstudio-5.0_trunk.soa-tooling.updatesite/config-history/2012-02-10_10-46-15/config.xml
@@ -101,106 +99,106 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>${WORKSPACE}/sources/product-soa/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10670 at 2/10/12 11:03 AM:
--------------------------------------------------------------
Added to the following job:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.a...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-01_22-41-53/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-10_11-01-14/config.xml
@@ -107,112 +105,112 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>aggregate/soa-site/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
and to
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-t...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-09_22-33-24/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-10_11-01-11/config.xml
@@ -112,118 +111,121 @@
# define correct URLs for upstream M5 bits
jbosstools-target-site=http://download.jboss.org/jbosstools/updates/targe...
local.site=/home/hudson/static_build_env/jbds/target-platform_3.3.indigo/e371-wtp331.target/
-jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
+# use latest upstream nightly Core update site instead of "wild
components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/
+#jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
local.composite=file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/3.3.indigo/
jboss-requirements-composite-mirror=http://download.jboss.org/jbosstools/...
jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
{code}
was (Author: nickboldt):
Added to the following job:
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.a...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-01_22-41-53/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_trunk.soa-tooling.aggregate/config-history/2012-02-10_11-01-14/config.xml
@@ -65,72 +65,70 @@
</hudson.model.ChoiceParameterDefinition>
</parameterDefinitions>
</hudson.model.ParametersDefinitionProperty>
- <hudson.plugins.disk__usage.DiskUsageProperty/>
- <hudson.plugins.build__publisher.ExternalProjectProperty/>
</properties>
<scm class="hudson.scm.SubversionSCM">
<locations>
@@ -107,112 +105,112 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>aggregate/soa-site/pom.xml</pom>
+ <properties># use latest upstream nightly Core update site instead of
"wild components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
and to
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-t...
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-09_22-33-24/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-10_11-01-11/config.xml
@@ -112,118 +111,121 @@
# define correct URLs for upstream M5 bits
jbosstools-target-site=http://download.jboss.org/jbosstools/updates/targe...
local.site=/home/hudson/static_build_env/jbds/target-platform_3.3.indigo/e371-wtp331.target/
-jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
+# use latest upstream nightly Core update site instead of "wild
components" in the composite staging site
+jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/
+#jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools/builds/staging/_composite_/core/3.3.indigo/
+
local.composite=file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/3.3.indigo/
jboss-requirements-composite-mirror=http://download.jboss.org/jbosstools/...
jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/c...
{code}
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:10 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10670:
------------------------------------
@Doug:
The remaining TODO for you here is to implement similar linking for the components in JBT
SOA, so that they too depend on [1] instead of [2].
[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
Then repeat those steps for the _stable_branch jobs (which we'll need in a week after
we freeze) where you'll swap s/trunk/3.3.indigo/ in the URLs [1], [2] noted above.
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-10670 at 2/10/12 11:16 AM:
--------------------------------------------------------------
@Doug:
The remaining TODO for you here is to implement similar linking for the components in JBT
SOA, so that they too depend on [1] instead of [2].
[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
Then repeat those steps for the _stable_branch jobs (which we'll need in a week after
we freeze) where you'll swap s/trunk/3.3.indigo/ in the URLs [1], [2] noted above.
was (Author: nickboldt):
@Doug:
The remaining TODO for you here is to implement similar linking for the components in JBT
SOA, so that they too depend on [1] instead of [2].
[1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
[2] http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooli...
Then repeat those steps for the _stable_branch jobs (which we'll need in a week after
we freeze) where you'll swap s/trunk/3.3.indigo/ in the URLs [1], [2] noted above.
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:51 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Douglas Palmer resolved JBIDE-10670.
------------------------------------
Resolution: Done
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:01 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Vlado Pakan commented on JBIDE-10670:
-------------------------------------
Nick/Douglas could you verify and close this Jira please.
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:09 a.m.
[
https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-10670.
------------------------------
These 4 jobs looks to be set up correctly.
devstudio-5.0_trunk.soa-tooling.updatesite
devstudio-5.0_stable_branch.soa-tooling.updatesite
jbosstools-3.3_trunk.soa-tooling.aggregate
jbosstools-3.3_stable_branch.soa-tooling.aggregate
JBT SOA Tooling aggregate build should depend on upstream already
aggregated JBT Core aggregate build
-----------------------------------------------------------------------------------------------------
Key: JBIDE-10670
URL: https://issues.jboss.org/browse/JBIDE-10670
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, updatesite
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 3.3.0.Beta1
Currently, SOA Tooling aggregate build for JBT builds based on upstream components and
also duplicates some content in JBT Core (see JBDS-1993).
In future, we should make the JBT SOA Tooling aggregate build simply reuse content from
the upstream JBT Core aggregate build.
1. link Jenkins jobs so Core causes SOA to fire
2. remove common components like Runtime and Usage from build/soa-site/site.xml
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5133
days inactive
5188
days old
jbosstools-issues@lists.jboss.org
13 comments
4 participants
participants (4)
-
Douglas Palmer (JIRA) -
Max Rydahl Andersen (JIRA)
-
Nick Boldt (JIRA)
-
Vlado Pakan (JIRA)