[ 
https://issues.apache.org/jira/browse/NIFI-2115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15371978#comment-15371978
 ] 

James Wing commented on NIFI-2115:
----------------------------------

Thinking over Joe's comments and reviewing the release procedure, there are at 
least four scenarios this code should address (but maybe not equally):

1. Build binaries from local git repo
2. Build from source not prepared by release process
3. Release build that generates a source bundle from a local git repo
4. Build convenience binaries from the release source bundle

My initial implementation only really supports 1 and maybe 2, but I missed the 
release steps 3 and 4.  Some options for the release process:

A. Ignore the SCM/Git properties in the source release.  Formal releases also 
include Tag, such as {{nifi-0.6.1-RC2}}, which may be specific enough for our 
purpose here.
B. Generate a properties file with commit and branch information as part of the 
source release, then read and apply this info in the source build.

I will include Tag in the about information set, since that's easily available 
and relevant.  I am working on a sample process for B, hopefully without 
requiring any changes to the release checklist or abusing Maven too severely.

> Enhanced About Box Version Information
> --------------------------------------
>
>                 Key: NIFI-2115
>                 URL: https://issues.apache.org/jira/browse/NIFI-2115
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core UI, Tools and Build
>    Affects Versions: 1.0.0
>            Reporter: James Wing
>            Assignee: James Wing
>            Priority: Minor
>
> The UI's About dialog and underlying API provide the version of NiFi, like 
> "0.7.0-SNAPSHOT".  For many bug reports and troubleshooting requests, this is 
> not very precise, especially around rapidly changing code or 
> platform-dependent behavior.  It would help if NiFi captured and displayed 
> additional information:  
> * NiFi build commit hash
> * NiFi build branch
> * NiFi build date/time
> * Java Version
> * Java Vendor (Oracle, OpenJDK)
> * OS
> Then a simple copy/paste from the about box would provide very specific 
> information about a particular NiFi installation and which code it was 
> derived from.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to