[jbosstools-issues] [JBoss JIRA] (JBIDE-18219) build info such as used git revisions/tags are not archived for our builds

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-18219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-18219.
--------------------------------
         Assignee: Nick Boldt
    Fix Version/s: 4.2.0.CR1
       Resolution: Done


This metadata is now copied [1] from /builds/staging/ into /builds/development when milestones are being considered for QE. 

[1] https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/69f9982652e520559fa9ef4701af71a6f1ef0ff5#diff-6cff8cb2334da18b9e6a7cb61820024fR53

For example, here are the git revisions for JBDS 8.0.0.CR1:

http://www.qa.jboss.com/binaries/RHDS/builds/development/8.0.0.CR1-build-core/ALL_REVISIONS.txt


> build info such as used git revisions/tags are not archived for our builds
> --------------------------------------------------------------------------
>
>                 Key: JBIDE-18219
>                 URL: https://issues.jboss.org/browse/JBIDE-18219
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>            Reporter: Max Rydahl Andersen
>            Assignee: Nick Boldt
>             Fix For: 4.2.0.CR1
>
>
> JBIDE-6958 and JBIDE-7444 was done to ensure we had the revision info and other results for a release, but seems we haven't archived this consinstelt over the years.
> We should review what info we definitely need but in general I would think archiving as much build info as possible would be a good practice anyway -  at least for the releases (alpha, beta, final, GA etc.)



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)