[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-7737) Verify savara jobs
[
https://jira.jboss.org/browse/JBIDE-7737?page=com.atlassian.jira.plugin.s...
]
Nick Boldt commented on JBIDE-7737:
-----------------------------------
I'm good w/ sharing the management of the jbosstool-savara* jobs w/ you, but since
it's your code I'm building there needs to be some co-ownership of the
upsteam/downstream relationship so that I can properly flow your hard work into JBT as you
intend.
Going forward my goal is to have reusable jobs called "trunk" or
"stable_branch" (or even a third "maintenance_branch", if necessary)
and just repurpose those rather than creating new ones every time we drop a milestone or
GA.
Anyway, for the moment, this is resolved.
Thanks!
Verify savara jobs
------------------
Key: JBIDE-7737
URL: https://jira.jboss.org/browse/JBIDE-7737
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Savara
Affects Versions: 3.2.0.CR1
Reporter: Nick Boldt
Assignee: Gary Brown
Priority: Trivial
I have two builds for savara right now. One pulls from your 1.1.x branch and builds
towards a 1.1 release (JBoss Tools 3.2.0.CR1 from trunk):
http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-sav...
http://anonsvn.jboss.org/repos/savara/branches/1.1.x
http://anonsvn.jboss.org/repos/jbosstools/trunk/build
The other pulls from a stable branch and builds toward a 3.1 release (JBoss Tools
3.2.0.Beta2 from branch):
http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-sav...
http://anonsvn.jboss.org/repos/savara/tags/jbosstools/1.1.x-jbt3.2.0.beta2
http://anonsvn.jboss.org/repos/jbosstools/branches/jbosstools-3.2.0.Beta2...
My question:
Should there be a savara 1.2 trunk build too, like Teiid has with 7.1/7.2 builds? If so,
I can create one for you called jbosstools-savara-1.2_trunk, building from your trunk.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira