[jbosstools-issues] [JBoss JIRA] (JBIDE-10670) JBT SOA Tooling aggregate build should depend on upstream already aggregated JBT Core aggregate build
Nick Boldt (JIRA)
jira-events at lists.jboss.org
Fri Feb 10 11:02:49 EST 2012
[ https://issues.jboss.org/browse/JBIDE-10670?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12665681#comment-12665681 ]
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.aggregate
{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-tooling.aggregate/
{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/target-platform_3.3.indigo/latest/
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/updates/indigo/SR1/
jbosstools-nightly=http://download.jboss.org/jbosstools/updates/nightly/core/3.3.indigo/
{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
More information about the jbosstools-issues
mailing list