Am 19.08.2012 18:02, schrieb Brett Cannon:
The link to their build tools is http://scan.coverity.com/self-build/ . 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.
Yes, that's what I'm talking about. It took me a while to figure out the correct URL and my password, too. The new version of coverity doesn't pull the changes automatically. Instead you have to compile the code with a custom build system and provide a download link for the results:
Coverity Scan Self-Build - updated July 2012
Coverity build tool link is:
Linux-64 6.0.2
Linux-32 6.0.2Downloading and building Do once:
Download and extract the tarball
Add the bin directory to your pathDo for each build:
cd to your build directory
optional: Run any build steps that you don't want to analyze –i.e. ./configure cov-build --dir cov-int [BUILD CMD and ARGS] Create a README file with your name, email, and project's name tar czvf project.tgz README cov-int Upload the project.tgz to your server
For your first build, after making the archive file available on a server, send the URL for it to scan-admin@coverity.com. Once we sort out any issues with the archive processing, you will get project name, and password to submit builds automatically whenever you like. Submitting self-builds Enter project name, password, email and download URL here: http://scan.coverity.com/submit.html
http://scan.coverity.com/self-build/6.0.2/cov-analysis-linux64-6.0.2.tar.gz http://scan.coverity.com/self-build/6.0.2/cov-analysis-linux32-6.0.2.tar.gz
I've tried to upload my build of Python's py3k head but the system doesn't recognize my password for the upload process. I guess we need to get a different password for the upload process. Or you could try your login data. Perhaps I don't have the necessary permissions. My build is available at http://dl.dropbox.com/u/19557108/project.tgz
Christian