<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Em 25/05/2017 03:49, Martin Kletzander escreveu:<br>
<blockquote type="cite" cite="mid:20170525064940.GA5363@wheatley">On
Thu, May 25, 2017 at 01:14:36AM -0300, <a class="moz-txt-link-abbreviated" href="mailto:claudioandre.br@gmail.com">claudioandre.br@gmail.com</a>
wrote:
<br>
<blockquote type="cite">From: Claudio André
<a class="moz-txt-link-rfc2396E" href="mailto:claudioandre.br@gmail.com"><claudioandre.br@gmail.com></a>
<br>
<br>
It builds the code coverage report and uploads the coverage data
to a web service in order to allow to track libvirt's code
coverage over time.
<br>
---
<br>
</blockquote>
<br>
You can add the links from the cover letter right here. It is
below the
<br>
'---' marker, so it won't be part of the commit message, but it is
also
<br>
before the first 'diff --git', so it won't be considered part of
the
<br>
patch either. Just like the stats below.
<br>
<br>
</blockquote>
<br>
Thanks for the information<br>
<br>
<blockquote type="cite" cite="mid:20170525064940.GA5363@wheatley">
<blockquote type="cite">+after_success:
<br>
+ - 'if [ -n "${COVERAGE}" ]; then
<br>
+ make -j3 cov;
<br>
+ coveralls-lcov --repo-token ${COVERALLS_TOKEN}
coverage/libvirt.info;
<br>
</blockquote>
<br>
I like this, but I have no idea where COVERALLS_TOKEN comes from.
<br>
</blockquote>
<br>
The Token comes from coveralls.io site. <br>
1. create your/libvirt account on coveralls (using GitHub
credentials) <br>
2. enable the libvirt repository and you will be able to see a field
named: REPO TOKEN.<br>
3. then, using Travis website (or Travis CLI tool, I prefer the
first for this case) you save the token ciphered.<br>
<br>
For Coveralls, click here and there and you will find your way to
enable the repository and get the token (probably
<a class="moz-txt-link-freetext" href="https://coveralls.io/github/YOUR_NICK/libvirt/settings">https://coveralls.io/github/YOUR_NICK/libvirt/settings</a>)<br>
For Travis: <a class="moz-txt-link-freetext" href="https://travis-ci.org/YOUR_NICK/libvirt/settings">https://travis-ci.org/YOUR_NICK/libvirt/settings</a>, you'll
see "Environment Variables" and the add button.<br>
<br>
<blockquote type="cite" cite="mid:20170525064940.GA5363@wheatley"> How
do we make sure that no user branches will post stuff to the <br>
coveralls.io site?<br>
</blockquote>
<br>
Because Travis save the token ciphered, nobody else can see the
token. In fact, if you save it using the site, it does not exist
even in the .travis.yml file.<br>
And if Travis, Coveralls, ..., are compromised, you can easily
regenerate the Token fast enough to avoid damage.<br>
<br>
Claudio<br>
Sorry if the message sounds, umm, pedantic.<span style="color:
rgb(34, 34, 34); font-family: arial, sans-serif; font-size: 16px;
font-style: normal; font-variant-ligatures: normal;
font-variant-caps: normal; font-weight: normal; letter-spacing:
normal; orphans: 2; text-align: start; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; -webkit-text-stroke-width: 0px;
background-color: rgb(255, 255, 255); text-decoration-style:
initial; text-decoration-color: initial; display: inline
!important; float: none;"></span><br>
<br>
Thanks<br>
</body>
</html>