[jira] [Updated] (EAGLE-581) Generate a build number when building the project.

2016-10-02 Thread Huizhi Lu (JIRA) 

 [ 
https://issues.apache.org/jira/browse/EAGLE-581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Huizhi Lu updated EAGLE-581:

Description: 
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


  was:
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 build property placeholders
create a build.properties file (e.g. in  src/main/resources):
build.properties:
build.version=${version}  # Maven version
build.revision=${buildNumber} # Source code revision number 
build.timestamp=${timestamp} # long value of check in time
3. Using build number in web app
@Value(“${build.revision}”)
private String buildRevision;




> 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.4#6332)

[jira] [Commented] (EAGLE-581) Generate a build number when building the project.

2016-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-581:
--

GitHub user pkuwm opened a pull request:

https://github.com/apache/incubator-eagle/pull/469

[EAGLE-581] Generate buildnumber when building the project.



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-581

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/469.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #469


commit 7c31006fb406148e513c44f3e8099da10dc962f6
Author: pkuwm 
Date:   2016-10-02T09:17:23Z

[EAGLE-581] Generate buildnumber when building the project.




> 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.4#6332)

[GitHub] incubator-eagle pull request #469: [EAGLE-581] Generate buildnumber when bui...

2016-10-02 Thread pkuwm 
GitHub user pkuwm opened a pull request:

https://github.com/apache/incubator-eagle/pull/469

[EAGLE-581] Generate buildnumber when building the project.



Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

 - [ ] Make sure the PR title is formatted like:
   `[EAGLE-] Description of pull request`
 - [ ] Make sure tests pass via `mvn clean verify`. (Even better, enable
   Travis-CI on your fork and ensure the whole test matrix passes).
 - [ ] Replace `` in the title with the actual Jira issue
   number, if there is one.
 - [ ] If this contribution is large, please file an Apache
   [Individual Contributor License 
Agreement](https://www.apache.org/licenses/icla.txt).

---


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/pkuwm/incubator-eagle EAGLE-581

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/469.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #469


commit 7c31006fb406148e513c44f3e8099da10dc962f6
Author: pkuwm 
Date:   2016-10-02T09:17:23Z

[EAGLE-581] Generate buildnumber when building the project.




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Created] (EAGLE-585) AlertEngine: create metadata validation api

2016-10-02 Thread Su Ralph (JIRA) 
Su Ralph created EAGLE-585:
--

 Summary: AlertEngine: create metadata validation api
 Key: EAGLE-585
 URL: https://issues.apache.org/jira/browse/EAGLE-585
 Project: Eagle
  Issue Type: Bug
Affects Versions: v0.5.0
Reporter: Su Ralph
Assignee: Su Ralph
 Fix For: v0.5.0


Currently alert engine metadata are inter connected but without strong 
validation. User usually confused by coordinator build failure or even when 
coordinator build succeed but runtime failure. In deployment with traffic 
runtime exception/error often lost in flood of logs.

Step1: Provide metadata validation api so user is able to verify the metadata 
before push data.

Step2: do more validation during coordinator build.

This issue to track step1.



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

[GitHub] incubator-eagle pull request #470: [EAGLE-585] : AlertEngine: create metadat...

2016-10-02 Thread RalphSu 
GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/470

 [EAGLE-585] : AlertEngine: create metadata validation api


Author: ralphsu

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/470.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #470


commit f686b37720fe6191644f289f9fc5190efb24d554
Author: Ralph, Su 
Date:   2016-10-02T16:07:12Z

 [EAGLE-585] : AlertEngine: create metadata validation api

Author: ralphsu




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-585) AlertEngine: create metadata validation api

2016-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-585:
--

GitHub user RalphSu opened a pull request:

https://github.com/apache/incubator-eagle/pull/470

 [EAGLE-585] : AlertEngine: create metadata validation api


Author: ralphsu

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/RalphSu/incubator-eagle master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-eagle/pull/470.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #470


commit f686b37720fe6191644f289f9fc5190efb24d554
Author: Ralph, Su 
Date:   2016-10-02T16:07:12Z

 [EAGLE-585] : AlertEngine: create metadata validation api

Author: ralphsu




> AlertEngine: create metadata validation api
> ---
>
> Key: EAGLE-585
> URL: https://issues.apache.org/jira/browse/EAGLE-585
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> Currently alert engine metadata are inter connected but without strong 
> validation. User usually confused by coordinator build failure or even when 
> coordinator build succeed but runtime failure. In deployment with traffic 
> runtime exception/error often lost in flood of logs.
> Step1: Provide metadata validation api so user is able to verify the metadata 
> before push data.
> Step2: do more validation during coordinator build.
> This issue to track step1.



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

[GitHub] incubator-eagle issue #470: [EAGLE-585] : AlertEngine: create metadata valid...

2016-10-02 Thread RalphSu 
Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/470
  
Fix to provide validate api in coordinator resource. There are some 
dependency missing cause check skipped: not able to check extension validity 
since extension code might only available in runtime topology.

This fix basically do the inter-reference check and policy QL validity 
check.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-585) AlertEngine: create metadata validation api

2016-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-585:
--

Github user RalphSu commented on the issue:

https://github.com/apache/incubator-eagle/pull/470
  
Fix to provide validate api in coordinator resource. There are some 
dependency missing cause check skipped: not able to check extension validity 
since extension code might only available in runtime topology.

This fix basically do the inter-reference check and policy QL validity 
check.


> AlertEngine: create metadata validation api
> ---
>
> Key: EAGLE-585
> URL: https://issues.apache.org/jira/browse/EAGLE-585
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> Currently alert engine metadata are inter connected but without strong 
> validation. User usually confused by coordinator build failure or even when 
> coordinator build succeed but runtime failure. In deployment with traffic 
> runtime exception/error often lost in flood of logs.
> Step1: Provide metadata validation api so user is able to verify the metadata 
> before push data.
> Step2: do more validation during coordinator build.
> This issue to track step1.



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

[GitHub] incubator-eagle pull request #470: [EAGLE-585] : AlertEngine: create metadat...

2016-10-02 Thread asfgit 
Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/470


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[jira] [Commented] (EAGLE-585) AlertEngine: create metadata validation api

2016-10-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on EAGLE-585:
--

Github user asfgit closed the pull request at:

https://github.com/apache/incubator-eagle/pull/470


> AlertEngine: create metadata validation api
> ---
>
> Key: EAGLE-585
> URL: https://issues.apache.org/jira/browse/EAGLE-585
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> Currently alert engine metadata are inter connected but without strong 
> validation. User usually confused by coordinator build failure or even when 
> coordinator build succeed but runtime failure. In deployment with traffic 
> runtime exception/error often lost in flood of logs.
> Step1: Provide metadata validation api so user is able to verify the metadata 
> before push data.
> Step2: do more validation during coordinator build.
> This issue to track step1.



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

[jira] [Resolved] (EAGLE-585) AlertEngine: create metadata validation api

2016-10-02 Thread Su Ralph (JIRA) 

 [ 
https://issues.apache.org/jira/browse/EAGLE-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Su Ralph resolved EAGLE-585.

Resolution: Fixed

> AlertEngine: create metadata validation api
> ---
>
> Key: EAGLE-585
> URL: https://issues.apache.org/jira/browse/EAGLE-585
> Project: Eagle
>  Issue Type: Bug
>Affects Versions: v0.5.0
>Reporter: Su Ralph
>Assignee: Su Ralph
> Fix For: v0.5.0
>
>
> Currently alert engine metadata are inter connected but without strong 
> validation. User usually confused by coordinator build failure or even when 
> coordinator build succeed but runtime failure. In deployment with traffic 
> runtime exception/error often lost in flood of logs.
> Step1: Provide metadata validation api so user is able to verify the metadata 
> before push data.
> Step2: do more validation during coordinator build.
> This issue to track step1.



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

[EAGLE BUILD FAILED] incubator-eagle-main failed on build #147

2016-10-02 Thread Apache Jenkins Server 
The Apache Jenkins build system has built incubator-eagle-main (build #147) 
Status: Still Failing Check console output at 
https://builds.apache.org/job/incubator-eagle-main/147/ to view the 
results. Test Report is at: Test Result