NEWS file for coverty-submit
+1.5 @
+ Support having the Coverity name to be different from the project name.
+
1.4 @ 20132-01-12
Make it safe for multiple users on the same machine.
Implement a verbosity option.
die("No such project as %s" % project)
# Collect project-specific variables
+ if config.has_option(project, "name"):
+ covname = config.get(project, "name")
+ else:
+ covname = project
if config.has_option(project, "password"):
password = config.get(project, "password")
else:
readme = """\
Name: %(name)s
Email: %(email)s
- Project: %(project)s
+ Project: %(covname)s
Submitted-by: coverity-submit
""" % globals()
if verbose:
if not noexec:
with open(os.path.join(tmpdir, "README"), "w") as wfp:
wfp.write(readme)
- tarball = "%s-scan.tgz" % project
+ tarball = "%s-scan.tgz" % covname
do_or_die("mv cov-int %s; (cd %s; tar -czf %s README cov-int; rm -fr README cov-int)" % (tmpdir, tmpdir, tarball))
print("Posting the analysis request...")
do_or_die('''curl \
--form file=@/tmp/%(tarball)s \
- --form project=%(project)s \
+ --form project=%(covname)s \
--form password=%(password)s \
--form email=%(email)s \
http://scan5.coverity.com/cgi-bin/upload.py \
prebuild: autogen.sh && make clean
build: make -k
postbuild:
+
+[cvs-fast-export]
+name: parsecvs
+password: ZZZZZZZ
+prebuild: make clean
+build: make
+postbuild:
+
</programlisting>
<para>Begin with an [ALL] section giving your name and userid on the
'tools' option to tell <application>coverity-submit</application>
where to find it.</para>
-<para>This configuration describes two different (real) projects, one
-with an scons-based build and one with an autotools-based build. For
-each project you must specifty the Coverity build password and the
-local build command to pass to cov-build. You may optionally specify
-local prebuild and postbuild commands.</para>
+<para>This configuration describes three different (real) projects;
+one with an scons-based build, one with an autotools-based build, and
+one with a plain makefile build. For each project you must specify the
+Coverity build password and the local build command to pass to
+cov-build. You may optionally specify local prebuild and postbuild
+commands.</para>
+
+<para>The third example also illustrates how to describe a project
+that is known to Coverity by a different name (in this case
+<quote>parsecvs</quote>) from the basename of the directory you keep
+it in (in this case <quote>cvs-fast-export</quote>). This can of
+course easily happen if your project's public name changes after
+you register it.</para>
<para>The <option>build</option> and <option>advertise</option>
options of versions 1.1 and previously are no longer needed, as