eagle-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (EAGLE-581) Generate a build number when building the project.
Date Mon, 17 Apr 2017 07:27:41 GMT

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

ASF GitHub Bot commented on EAGLE-581:
--------------------------------------

Github user jhsenjaliya commented on the issue:

    https://github.com/apache/eagle/pull/505
  
    duplicate of #639 
    @pkuwm , can u please close this PR, Thanks


> Generate a build number when building the project.
> --------------------------------------------------
>
>                 Key: EAGLE-581
>                 URL: https://issues.apache.org/jira/browse/EAGLE-581
>             Project: Eagle
>          Issue Type: New Feature
>    Affects Versions: v0.5.0
>            Reporter: Huizhi Lu
>            Assignee: Huizhi Lu
>             Fix For: v0.5.0
>
>
> Use case:
> we need to know what version(latest commit revision) of source code we are using for
the current build so that it will be convenient for us to clarify different builds. So when
you might make 100 builds of version 0.5.0-SNAPSHOT, you can differentiate between them all.
> Solution:
> Use buildnumber-maven-plugin
> 1. Add Maven plugin buildnumber-maven-plugin to pom.xml file
> 2. Add manifest entries to META-INF/MANIFEST.MF
> Build-Branch: EAGLE-581
> Build-Commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c
> Build-Time: 2016-10-02 09:05:31 AM, UTC
> 3. Placehold VERSION.
> The build info is stored in RELEASE File in the root directory. RELEASE is like:
> project.version: 0.5.0-incubating-SNAPSHOT
> build.branch: EAGLE-581
> build.commit: f6fad2ebe8a384a6d17e40c609041ff77f6a692c
> build.time: 2016-10-02 01:39:40 AM, PDT



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message