[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:comment-tabpanel&focusedCommentId=12997546#comment-12997546 ] 

Nick Boldt edited comment on JBIDE-18219 at 9/1/14 12:53 PM:
-------------------------------------------------------------

For JBT, we copy entire build folders so we get all the metadata. For example:

http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-03-18_15-46-19-B706/logs/ALL_REVISIONS.txt
http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.CR1-build-core/2014-08-30_22-46-41-B204/logs/ALL_REVISIONS.txt

Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows:

{code:title=jenkins job name :: github branch at SHA :: github commit/SHA}
jbosstools-vpe_41 :: origin/jbosstools-4.1.x at 86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3ca6614b9ebe5a17205f0244676596fd8f
{code}

For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files:

JBDS entries are simple:
{code:title=github branch at SHA}
origin/jbosstools-4.2.x at 5327ccb62016547090c569dafa272f99e59b4bc8
{code}

But JBT ones are more complex because of how they're collected:

{code:title=project name , plugin whose MANIFEST.MF is checked , plugin version , SHA , github branch at SHA , github URL for the source zip with SHA , source zip w/o path }
jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598 at 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730e761a3e07f2a7bc1f59627c42.zip , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip
...
jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598 at 9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a507c03bb59bfa48cb98d342fb35e99.zip , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip
{code}

The list of plugins whose manifests should be checked is here:

https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregate/site/pom.xml#L138-L157


was (Author: nickboldt):
For JBT, we copy entire build folders so we get all the metadata. For example:

http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-03-18_15-46-19-B706/logs/ALL_REVISIONS.txt
http://download.jboss.org/jbosstools/builds/development/jbosstools-4.2.0.CR1-build-core/2014-08-30_22-46-41-B204/logs/ALL_REVISIONS.txt

Contents of the ALL_REVISIONS.txt file for JBT 4.1 is as follows:

{code:title=jenkins job name :: github branch at SHA :: github commit/SHA}
jbosstools-vpe_41 :: origin/jbosstools-4.1.x at 86607d3ca6614b9ebe5a17205f0244676596fd8f :: https://github.com/jbosstools/jbosstools-jbosstools-vpe_41/commit/86607d3ca6614b9ebe5a17205f0244676596fd8f
{code}

For JBT 4.2 & JBDS 8, the file is more complex, since we aren't tied to jobs but to Eclipse-SourceReferences in manifest.mf files:

JBDS entries are simple:
{code:title=github branch at SHA}
origin/jbosstools-4.2.x at 5327ccb62016547090c569dafa272f99e59b4bc8
{code}

But JBT ones are more complex because of how they're collected:

{code:title=project-name , plugin-whose-MANIFEST.MF-is-checked , plugin-version , SHA , github branch at SHA , github URL for the source zip with SHA , source zip w/o path }
jbosstools-aerogear , org.jboss.tools.aerogear.thym , 1.2.0.CR1-v20140829-2054-B52 , 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598 at 2ccea7330e26730e761a3e07f2a7bc1f59627c42 , https://github.com/jbosstools/jbosstools-aerogear/archive/2ccea7330e26730e761a3e07f2a7bc1f59627c42.zip , jbosstools-aerogear_CR1-v20140829-2054-B52_2ccea7330e26730e761a3e07f2a7bc1f59627c42_sources.zip
...
jbosstools-webservices , org.jboss.tools.ws.core , 1.7.0.CR1-v20140829-1427-B52 , 9eab63009a507c03bb59bfa48cb98d342fb35e99 , origin/8fe5757550f41bb2440a31f4f086948a16c1e598 at 9eab63009a507c03bb59bfa48cb98d342fb35e99 , https://github.com/jbosstools/jbosstools-webservices/archive/9eab63009a507c03bb59bfa48cb98d342fb35e99.zip , jbosstools-webservices_CR1-v20140829-1427-B52_9eab63009a507c03bb59bfa48cb98d342fb35e99_sources.zip
{code}


> 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)