<br><br><div class="gmail_quote">On Sun, Aug 19, 2012 at 11:56 AM, Brett Cannon <span dir="ltr"><<a href="mailto:brett@python.org" target="_blank">brett@python.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><div class="gmail_quote"><div class="im">On Sat, Aug 18, 2012 at 11:01 AM, Christian Heimes <span dir="ltr"><<a href="mailto:lists@cheimes.de" target="_blank">lists@cheimes.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Am 18.08.2012 15:08, schrieb Stefan Krah:<br>
<div>> Christian Heimes <<a href="mailto:lists@cheimes.de" target="_blank">lists@cheimes.de</a>> wrote:<br>
>> Yup, my login still works. I can send you a CSV or XML report if you like.<br>
><br>
> Thanks, got the CSV!<br>
><br>
> If anyone has the possibility to create new accounts, I would like to apply<br>
> for one.<br>
<br>
</div>Who usually uploads the necessary files to coverity? The current files<br>
are rather old (patchlevel.h says 3.3.0a0). I was able to create the<br>
report files but the files must be uploaded to a registered location.<br></blockquote><div><br></div></div><div>I think I'm still listed as the main contact and I never uploaded anything. I believe Coverty pulls the files in themselves. </div>
</div>
</blockquote></div><br><div>So when trying to log in (which didn't work; Coverty has changed this system so many times I don't what username/password works anymore) there was a notice that how you submit code has changed:</div>
<div><br></div><div><span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">At the same time, we also have changes in the process to submit the build to Coverity Scan for Open Source Projects.</span><br style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">
<br style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px"><span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">0. With the new version, there are three steps to analyze a codebase: build, analyze, and commit.</span><br style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">
<span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">1. You do the build step, then tar up the intermediate representation and stick it somewhere we can get it by http.</span><br style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">
<span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">2. Our scripts wget it, analyze it, commit it to the DB and send you an email.</span></div><div><span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px"><br>
</span></div><div><span style="font-family:arial,helvetica,clean,sans-serif;font-size:13px;line-height:16px">The link to their build tools is </span><font face="arial, helvetica, clean, sans-serif"><span style="line-height:16px"><a href="http://scan.coverity.com/self-build/">http://scan.coverity.com/self-build/</a> . So it looks like we have to give them the files to analyze now after we have built them with their tool chain on LInux.</span></font></div>