[jbosstools-issues] [JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030000#comment-13030000 ] 

Nick Boldt commented on JBIDE-15135:
------------------------------------

{quote}generate for example a site for openshift module with the mojo, so that buildinfo.json exists, then try to build central similarily{quote}
So for the aggregate sites (site, coretests, webtools, hibernatetools) we'd get all the upstream projects in that section. Cool - that's perfect. 

Re: defaults vs. CLI, the idea is to not have to deduce stuff after the fact (like a month later) but rather store the info when we know it (at build/publish time). That way it's there for archival purposes and future audit needs. Which is also why I think having JVM/OS details for the slaves is useful - it's easier to read the report than to have to go query the slave name for its details, or have to SSH there to get a list of JDKs available ... and then have to guess/assume which is the one used. Many slaves use a "latest" symlink and therefore when you go look at the slave a week after a build, if a new JDK update is released, your assumed JDK version will be wrong if IT/Engops updated the symlink between the time you built and the time you went to check for the info.

Same goes for deducing variables in parent pom... what if the parent pom in Nexus changes after the build? 
 

> Attach metadata during assembly instead of publish time
> -------------------------------------------------------
>
>                 Key: JBIDE-15135
>                 URL: https://issues.jboss.org/browse/JBIDE-15135
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.x
>
>
> In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site.
> Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)