[
https://issues.jboss.org/browse/JBIDE-11524?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-11524 at 9/7/12 12:19 PM:
-------------------------------------------------------------
Assuming we are just talking about simplifying the profile names in the parent pom,
then...
I like this this simpler scheme. HOWEVER...
a) How is continuous different from snapshot? Are you assuming the staging composite site
is "continuous" as it changes every time a component is respun, whereas snapshot
is when the JBT aggregate (nightly) is respun?
b) where do we use milestone or release today?
c) where does the notion of an "integration" site fit into this?
---
Here are the repos we currently need to reference by some simpler name:
* continuously evolving trunk composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
* aggregate unstable trunk snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
* continuously evolving stable branch composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0....
* aggregate stable branch snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno/ (published to
http://download.jboss.org/jbosstools/updates/development/juno/ )
And going forward with the git migration (JBIDE-12475) we've talked about creating two
more sites to facilitate cross-component integration:
* developer-released integration builds in a composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0....
* aggregate integration snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno_integr... (published
to
http://download.jboss.org/jbosstools/updates/integration/juno/ ?)
So how would you name those 6 sites?
was (Author: nickboldt):
Assuming we are just talking about simplifying the profile names in the parent pom,
then...
I like this this simpler scheme. HOWEVER...
a) How is continuous different from snapshot? Are you assuming the staging composite site
is "continuous" as it changes every time a component is respun, whereas snapshot
is when the JBT aggregate (nightly) is respun?
b) where do we use milestone or release today?
c) where does the notion of an "integration" site fit into this?
---
Here are the repos we currently need to reference by some simpler name:
* continuously evolving trunk composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/
* aggregate unstable trunk snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
* continuously evolving stable branch composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0....
* aggregate stable branch snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno/
And going forward with the git migration (JBIDE-12475) we've talked about creating two
more sites to facilitate cross-component integration:
* developer-released integration builds in a composite site -
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0....
* aggregate integration snapshot site -
http://download.jboss.org/jbosstools/updates/nightly/core/4.0.juno_integr...
So how would you name those 6 sites?
Rename jobs, sites, profiles, variables... to clearer names (remove
reference to nightly)
-----------------------------------------------------------------------------------------
Key: JBIDE-11524
URL:
https://issues.jboss.org/browse/JBIDE-11524
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng
Affects Versions: 4.0.0.Alpha1
Reporter: Mickael Istria
Assignee: Nick Boldt
Priority: Minor
Fix For: 4.0.0.Alpha2
nightly is a very confusing name, that does not reflect at all what really happens.
We should prefer using "staging" in variable, profiles, jobs, url... to make it
clearer
For instance,
* jbosstools-nightly-staging-composite -> jbosstools-staging-composite
* jboostools-nightly -> jbosstools-staging-aggregate
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira