[
https://issues.jboss.org/browse/JBIDE-14711?page=com.atlassian.jira.plugi...
]
Nick Boldt reassigned JBIDE-14711:
----------------------------------
Assignee: Mickael Istria (was: Nick Boldt)
As per the email I sent announcing Beta1b, here's the folder with the build &
metadata:
http://download.jboss.org/jbosstools/builds/development/4.1.0.Beta1b.core/
Updates go in /updates/
Builds go in /builds/
Also...
Discovery goes in /discovery/
Requirements go in /updates/requirements/
Target Platforms go in /targetplatforms/
Promotion process/script loses build metadata?
----------------------------------------------
Key: JBIDE-14711
URL:
https://issues.jboss.org/browse/JBIDE-14711
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: Build/Releng, updatesite
Reporter: Mickael Istria
Assignee: Mickael Istria
Priority: Critical
Fix For: 4.1.0.Beta2
When promoting an aggregation build to nightly, metadata disappear. The only metadata
available is the build ID (that we can read in qualifier) but this is not enough as
Jenkins build are volatile.
Loss of these metadata makes that it's not possible to find out which commit was used
to build an aggregated component.
We should copy metadata along with update-sites.
--
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