sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

ref-manual: Edits to bugzilla and deploy class. 

Fixed a link in the deploy class.
Re-wrote the bugzilla class to be clearer.

(From yocto-docs rev: ce4f72644e9da987adb3873c91c14a8e5e8df555)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2013-12-09 07:07:42 -06:00 committed by Richard Purdie
parent 51362f7858
commit 936b8180e3
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
documentation/ref-manual/ref-classes.xml
View File

@ -291,11 +291,11 @@
<title><filename>bugzilla.bbclass</filename></title>
<para>
The <filename>bugzilla</filename> class automatically files bug reports
to a Bugzilla instance in response to build failures.
This class uses Bugzilla's XML-RPC interface.
Consequently, you need to enable the class in the instance of Bugzilla
within which you wish to file reports.
The <filename>bugzilla</filename> class supports setting up an
instance of Bugzilla in which you can automatically files bug reports
in response to build failures.
For this class to work, you need to enable the XML-RPC interface in
the instance of Bugzilla.
</para>
</section>
@ -529,7 +529,7 @@
Recipes that inherit this class should define their own
<filename>do_deploy</filename> function to copy the files to be
deployed to
<link linkend='var-DEPLOY_DIR'><filename>DEPLOYDIR</filename></link>,
<link linkend='var-DEPLOYDIR'><filename>DEPLOYDIR</filename></link>,
and use <filename>addtask</filename> to add the task at the appropriate
place, which is usually after <filename>do_compile</filename> or
<filename>do_install</filename>.