set SOA Tooling jobs in _stable_branch to source from trunk, but
build against Core from M5
-------------------------------------------------------------------------------------------
Key: JBDS-2007
URL:
https://issues.jboss.org/browse/JBDS-2007
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Build, SOA Tooling / Platform
Affects Versions: 5.0.0.GA-SOA
Reporter: Nick Boldt
Assignee: Douglas Palmer
Fix For: 5.0.0.GA-SOA
Here's a diff showing what you have to change to migrate the jobs over to the new
mechanism (using M5 target platform, reqs mirror, JBT Core bits, and SOA Tooling
sources/binaries from trunk).
You'll want to do the same w/ the other 6 SOA Tooling component builds w/
_stable_branch in their name.
And you'll want to ensure the Drools contribution is 5.3, not 5.2.
{code}
---
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2011-12-23_06-58-39/config.xml
+++
/qa/hudson_master/hudson_home/hudson_workspace/jobs/jbosstools-3.3_stable_branch.soa-tooling.aggregate/config-history/2012-02-09_10-03-09/config.xml
@@ -7,13 +7,13 @@

<h2><a style="color:blue"
href="http://download.jboss.org/jbosstools/builds/cascade/3.3.in...
Job Cascade &amp; Results</a></h2>

-Currently building 3.3.0.M5</description>
+Currently building 3.3.0.Beta1-pre</description>
<logRotator>
<daysToKeep>5</daysToKeep>
<numToKeep>5</numToKeep>
@@ -41,47 +41,47 @@
-q :: quieter output</pre>
</description>
- <defaultValue>clean install -B -U -fae -P
hudson,jbosstools-nightly-staging-composite,local.site,local.composite
-Dmaven.repo.local=${WORKSPACE}/m2-repository</defaultValue>
+ <defaultValue>clean install -B -U -fae -P
hudson,jbosstools-nightly-staging-composite,jbosstools-nightly-staging-composite-soa-tooling,local.site,local.composite
-Dmaven.repo.local=${WORKSPACE}/m2-repository</defaultValue>
</hudson.model.StringParameterDefinition>
<hudson.model.ChoiceParameterDefinition>
<name>RELEASE</name>
@@ -71,77 +70,76 @@
<scm class="hudson.scm.SubversionSCM">
<locations>
<hudson.scm.SubversionSCM_-ModuleLocation>
-
<
remote>http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3...
+
<
remote>http://anonsvn.jboss.org/repos/jbosstools/trunk/build</remot...
<local>sources</local>
</hudson.scm.SubversionSCM_-ModuleLocation>
</locations>
@@ -88,94 +87,93 @@
</scm>
<assignedNode>RHEL&&!ia64</assignedNode>
<canRoam>false</canRoam>
- <disabled>true</disabled>
+ <disabled>false</disabled>
<blockBuildWhenDownstreamBuilding>false</blockBuildWhenDownstreamBuilding>
<blockBuildWhenUpstreamBuilding>true</blockBuildWhenUpstreamBuilding>
<jdk>java16_default</jdk>
@@ -107,112 +106,125 @@
<mavenName>maven-3.0.3</mavenName>
<jvmOptions>-Xms512m -Xmx1024m -XX:PermSize=128m
-XX:MaxPermSize=256m</jvmOptions>
<pom>aggregate/soa-site/pom.xml</pom>
+ <properties>BUILD_ALIAS=Beta1-pre
+
+# 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/
+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/
+jboss-requirements-composite-extras-mirror=http://download.jboss.org/jbosstools/updates/indigo/extras/SR1a/
+
+# pull SOA Tooling bits from trunk instead of 3.3.indigo
+jbosstools-nightly-staging-composite-soa-tooling=http://download.jboss.org/jbosstools/builds/staging/_composite_/soa-tooling/trunk/
+jbosstools-nightly-soa-tooling=http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/</properties>
<usePrivateRepository>false</usePrivateRepository>
</hudson.tasks.Maven>
<hudson.tasks.Shell>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: