[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16957705#comment-16957705
]
Jiri Daněk commented on PROTON-1796:
This is in place in a branch in a separate repository that I have under
control, linked in the previous comment. This seems good enough, I'm giving up
trying to get this under the qpid-proton repository.
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16560634#comment-16560634
]
Jiri Daněk commented on PROTON-1796:
GitHub: https://github.com/msgqe/travisci/tree/qpid-proton-coverity
TravisCI: https://travis-ci.org/msgqe/travisci/builds/40902
Coverity: https://scan.coverity.com/projects/apache-qpid-proton
For some reason I cannot adjust Analysys Settings/Project Components (I get a
404 error when I add components and then click "Save changes"). I wanted to
especially exclude tests from analysis, because it was my experience in
Artemis, that inference of null values is broken if test code is considered
(and there are stub implementations of classes with methods returning null).
The patterns I had in mind were something like (with .* at the end of each):
{noformat}
/qpid-proton/c/src
/qpid-proton/c/examples
/qpid-proton/c/tests
/qpid-proton/cpp/src
/qpid-proton/cpp/examples
/qpid-proton/ruby
/qpid-proton/go
/qpid-proton/python
/qpid-proton-j/proton-j
/qpid-proton-j/examples/
/qpid-proton-j/tests/
{noformat}
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558489#comment-16558489
]
ASF GitHub Bot commented on PROTON-1796:
Github user jdanekrh closed the pull request at:
https://github.com/apache/qpid-proton/pull/133
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558488#comment-16558488
]
ASF GitHub Bot commented on PROTON-1796:
Github user jdanekrh commented on the issue:
https://github.com/apache/qpid-proton/pull/133
I have to agree. Without the ability to have periodic travis build, there
won't be a point. Closing the PR, then.
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558484#comment-16558484
]
ASF GitHub Bot commented on PROTON-1796:
Github user gemmellr commented on the issue:
https://github.com/apache/qpid-proton/pull/133
I meant the PR probably doesnt make sense, i.e we wouldnt have a branch
here, which it seems you agree with.
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558459#comment-16558459
]
ASF GitHub Bot commented on PROTON-1796:
Github user jdanekrh commented on the issue:
https://github.com/apache/qpid-proton/pull/133
It does not have to be placed on this mirror. The Artemis coverity run is
under /msgqe/ organization on github. The only requirement is that the coverity
token needs to be uploaded to travis under that specific account.
So, for example, if I was given rights on coverity website to upload new
builds for the project, I would be able to set up the coverity build. (That is
exactly how it is working for Artemis right now.)
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558454#comment-16558454
]
ASF GitHub Bot commented on PROTON-1796:
Github user gemmellr commented on the issue:
https://github.com/apache/qpid-proton/pull/133
I don't think we have ability to configure periodic builds in Travis on
this mirror, over which we have limited control in which case this doesn't
really make sense.
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-1796) Automated periodic Coverity Scan runs
[
https://issues.apache.org/jira/browse/PROTON-1796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16558379#comment-16558379
]
ASF GitHub Bot commented on PROTON-1796:
Github user jdanekrh commented on the issue:
https://github.com/apache/qpid-proton/pull/133
@ssorj The coverity PR for daily (weekly) build. This is the same thing
that is set up for Artemis,
https://github.com/msgqe/travisci/tree/activemq-artemis-coverity.
> Automated periodic Coverity Scan runs
> -
>
> Key: PROTON-1796
> URL: https://issues.apache.org/jira/browse/PROTON-1796
> Project: Qpid Proton
> Issue Type: Improvement
> Components: build
>Affects Versions: proton-c-0.21.0
>Reporter: Jiri Daněk
>Priority: Major
>
> The attached commit could be added as a new branch. Then, TravisCI can be set
> up
> to build it daily (or weekly).
> What it does is that it
> * checks out the current master branch
> * builds it under the Coverity tool
> * submits the build to Coverity Scan
> The {{COVERITY_SCAN_TOKEN}} would need to be replaced with a correct one.
> The new branch would need to be created.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
