From 48dc9e03f4f25e9062efbab71496fe44dd742a7f Mon Sep 17 00:00:00 2001 From: Junchun Guan Date: Tue, 11 Mar 2014 14:42:40 +0800 Subject: [PATCH] Update jenkins jobs configuration Change-Id: I40b16621ec3390cf78e55e44af2b11dc71140364 Signed-off-by: Junchun Guan --- .../GBS-local-build-with-package-list/config.xml | 165 +++++++++++---------- .../configs/GBS-local-full-build/config.xml | 137 +++++++++-------- 2 files changed, 164 insertions(+), 138 deletions(-) diff --git a/jenkins-jobs/configs/GBS-local-build-with-package-list/config.xml b/jenkins-jobs/configs/GBS-local-build-with-package-list/config.xml index df7a4ef..b245c96 100644 --- a/jenkins-jobs/configs/GBS-local-build-with-package-list/config.xml +++ b/jenkins-jobs/configs/GBS-local-build-with-package-list/config.xml @@ -1,76 +1,83 @@ - This jenkins job is used to build Tizen sources. -This job is based on <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> and <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system">GBS</a>. Developers can reconfigure -this job to run periodically, of course can be triggered at anytime needed.</p> -<p>Using this job, developers can specify a list of packages, which just have + <p>This job is designed for Tizen package building, image creation and build +artifacts publishing by using <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> and <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system">GBS</a> as basis. It can be reconfigured +to run periodically or be manually triggered whenever needed.</p> +<p>With <strong>PUBLISH</strong> option enabled, build artifacts, including build reports, +repos and images, will be synchronized to respective download servers.</p> +<p>Before using this job, it is highly recommended that <a class="reference external" href="https://source.tizen.org/documentation/developer-guide/creating-tizen-image-scratch">Creating a Tizen Image +from Scratch</a> , which is the manual equivalent of this job, is read and well +understood.</p> +<p>This job is designed for building part of the packages based on users’ +customization, that is , developers can specify a list of packages which just have been updated in remote repos, and check if the final image can work well -with these changes of packages. To use this job, one remote repo must be -specified, which can be used to get ks file and required by <cite>gbs build</cite>. -An example of remote repo is shown below:</p> -<pre class="literal-block"> -http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/ -</pre> -<p>With <strong>PUBLISH</strong> enabled, build artifacts, including build reports, repos and -images, will be synchronized to respective download servers.</p> -<p><strong>Note:</strong> To get a better understanding of this job, it is highly recommended -that the following document, which provides instructions of the corresponding -manual operations, is read and well understood: -<a class="reference external" href="https://source.tizen.org/documentation/developer-guide/creating-tizen-image-scratch">Creating a Tizen Image from Scratch</a></p> -<p>The following options are supported by this jenkins job:</p> +with these changes of packages.</p> +<p>To use this job, one remote repo must be specified, from which the building +packages required by GBS and the ks file required by MIC can be obtained.</p> +<p>An example of remote repo is shown below:</p> +<blockquote> +<a class="reference external" href="http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/">http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/</a></blockquote> +<p>Supported options are shown below:</p> <dl class="docutils"> <dt><tt class="docutils literal">MANIFEST_URL</tt></dt> -<dd><p class="first">The manifest url, which should be recognized by <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, -for example: <cite>review.tizen.org:scm/manifest</cite>, where <cite>review.tizen.org</cite> -is the alias name set in ~/.ssh, like:</p> -<pre class="literal-block"> -Host review.tizen.org +<dd><p class="first">This option specifies the manifest URL, which will be recognized by the +<a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, for example, in <cite>tizen:scm/manifest</cite>, +<cite>scm/manifest</cite> is the manifest path in remote tizen.org Gerrit, whereas +<cite>tizen</cite> is the alias set in ~/.ssh/config, an example of +~/.ssh/config is shown below:</p> +<pre class="last literal-block"> +Host tizen review.tizen.org Hostname review.tizen.org Port 29418 User &lt;username&gt; #ProxyCommand connect -S &lt;proxy&gt;:&lt;port&gt; %h %p </pre> -<p class="last">and, <cite>scm/manifest</cite> is the manifest path in remote tizen.org gerrit.</p> </dd> -<dt><tt class="docutils literal">MANIFEST_BRANCHES</tt></dt> -<dd>This option specifies the manifest branch used for syncing code, this +<dt><tt class="docutils literal">MANIFEST_BRANCH</tt></dt> +<dd>This option specifies the manifest branch used for synchronizing code, this value will be passed to <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command directly.</dd> <dt><tt class="docutils literal">PROFILE</tt></dt> -<dd>This option specifies the target profile, valid values: <cite>IVI</cite>, <cite>Mobile</cite>.</dd> +<dd>This option specifies the profile used for building, currently, the valid +values are <cite>IVI</cite> and <cite>Mobile</cite></dd> <dt><tt class="docutils literal">ARCH</tt></dt> -<dd>This option specifies the arch to be built, valid values: <cite>i586</cite> and -<cite>armv7l</cite>.</dd> +<dd>This option specifies the arch to be built, currently the valid values are +i586 and armv7l.</dd> <dt><tt class="docutils literal">REMOTE_REPOS</tt></dt> -<dd>The remote repos for doing local full build using gbs, and get ks file for -image creation.</dd> +<dd>This option specifies the remote repos from which packages are obtained +during package building. Valid remote repos must contans tizen repo data, +including buildata, images and repos in it, for example: +<a class="reference external" href="http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/">http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/</a></dd> <dt><tt class="docutils literal">KS</tt></dt> -<dd>Specify the ks file name used to create images. The avaliable names -should be in <strong>REMOTE_REPO</strong> specified above, multiple ks can be -specified seperate by space.</dd> -<dt><tt class="docutils literal">PACKAGE_LIST</tt></dt> -<dd>This option specifies the package list, in which the full path of each -package is listed line by line.</dd> +<dd>This option specifies the ks file based on which MIC performs the image +creation. Valid values are the ones contained in the specified remote repo. +List of multiple ks files, in which the names are separated by spaces, +is supported as well.</dd> <dt><tt class="docutils literal">BUILD_RDEPS</tt></dt> -<dd>This option enables the building with dependency,that is, packages that -depend on packages in <cite>PACKAGE_LIST</cite> will be built in correct dependency -order.</dd> +<dd>This option enables the building with dependency, that is, packages that +have dependent packages will be built in correct dependency order.</dd> +<dt><tt class="docutils literal">PACKAGE_LIST</tt></dt> +<dd>This option specifies the package list in which packages to be built are +listed per line. The format must be the full path in remote Gerrit.</dd> <dt><tt class="docutils literal">PARALEL_THREADS</tt></dt> -<dd>This option determines how many builder gbs should run in parallel</dd> +<dd>This option specifies the number of builders GBS runs in parallel. Valid +value is non-negative integer.</dd> <dt><tt class="docutils literal">EXCLUDE_PACKAGES</tt></dt> -<dd>This option specifies the packages that does not participate in building. -And also can be used to break dependency cycles.</dd> +<dd>This option specifies the packages that will be excluded during package +building. This option also can be used to break dependency cycles. Multiple +packages must be separated by comma(,)</dd> <dt><tt class="docutils literal">BUILD_ARGS</tt></dt> -<dd>Specify more gbs build options. For more gbs build options and usage -refer to <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. Default value: empty.</dd> +<dd>This option specifies more GBS build options, which will be passed to <cite>gbs +build</cite> command. Multiple options are supported, different options must be +seperated by space, For more information about gbs build options, refer to +<a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>.</dd> <dt><tt class="docutils literal">PUBLISH</tt></dt> -<dd>This option enables the publishing of build artifacts to respective -download servers. Build artifacts include report, images and repos.</dd> +<dd>This option enables the publishing of build artifacts, including build +reports, images and repos.</dd> <dt><tt class="docutils literal">PUBLISH_URL</tt></dt> -<dd>Specify the URL address to publish build artifacts. The format of -<cite>PUBLISH_URL</cite> should be the same as rsync format which can be a local -path or remote url like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. -This option only take effect if PUBLISH is enabled.</dd> +<dd>This option specifies the URL address to publish build artifacts. The +format of PUBLISH_URL must be the same as rsync format, which can be a +local path or remote URL like: <cite>user&#64;hostname:/path/to/publish_dir</cite>.</dd> </dl> false @@ -78,29 +85,31 @@ This option only take effect if PUBLISH is enabled.</dd> MANIFEST_URL - <p class="first">The manifest url, which should be recognized by <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, -for example: <cite>review.tizen.org:scm/manifest</cite>, where <cite>review.tizen.org</cite> -is the alias name set in ~/.ssh, like:</p> -<pre class="literal-block"> -Host review.tizen.org + <p class="first">This option specifies the manifest URL, which will be recognized by the +<a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, for example, in <cite>tizen:scm/manifest</cite>, +<cite>scm/manifest</cite> is the manifest path in remote tizen.org Gerrit, whereas +<cite>tizen</cite> is the alias set in ~/.ssh/config, an example of +~/.ssh/config is shown below:</p> +<pre class="last literal-block"> +Host tizen review.tizen.org Hostname review.tizen.org Port 29418 User &lt;username&gt; #ProxyCommand connect -S &lt;proxy&gt;:&lt;port&gt; %h %p </pre> -<p class="last">and, <cite>scm/manifest</cite> is the manifest path in remote tizen.org gerrit.</p> review.tizen.org:scm/manifest MANIFEST_BRANCH - This option specifies the manifest branch used for syncing code, this + This option specifies the manifest branch used for synchronizing code, this value will be passed to <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command directly. tizen PROFILE - This option specifies the target profile, valid values: <cite>IVI</cite>, <cite>Mobile</cite>. + This option specifies the profile used for building, currently, the valid +values are <cite>IVI</cite> and <cite>Mobile</cite> ivi @@ -110,9 +119,10 @@ value will be passed to <a class="reference external" href="ht REMOTE_REPOS - The remote repos for doing local full build using gbs, and get ks file for -image creation. Example: -http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/ + This option specifies the remote repos from which packages are obtained +during package building. Valid remote repos must contans tizen repo data, +including buildata, images and repos in it, for example: +<a class="reference external" href="http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/">http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/</a> https://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140214.10 @@ -133,13 +143,12 @@ For multiple ks file use spaces to separate them: PACKAGE_LIST Specify the packages list to be built, and one line for per package. The format should be the detail path in remote gerrit. - apps/core/preloaded/menu-screen -apps/core/preloaded/settings - + apps/core/preloaded/menu-screenapps/core/preloaded/settings ARCH - This option specifies the arch to be built, valid values: <cite>i586</cite> + This option specifies the arch to be built, currently the valid values are +i586 and armv7l. ia32 @@ -149,32 +158,36 @@ apps/core/preloaded/settings PARALEL_THREADS - This option determines how many builder gbs should run in parallel. + This option specifies the number of builders GBS runs in parallel. Valid +value is non-negative integer. 4 EXCLUDE_PACKAGES - This option specifies the packages that does not participate in building. -And also can be used to break dependency cycles. + This option specifies the packages that will be excluded during package +building. This option also can be used to break dependency cycles. Multiple +packages must be separated by comma(,) texinfo,aul,gettext BUILD_ARGS - Specify more gbs build options. For more gbs build options and usage -refer to <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. Default value: empty. + This option specifies more GBS build options, which will be passed to <cite>gbs +build</cite> command. Multiple options are supported, different options must be +seperated by space, For more information about gbs build options, refer to +<a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. PUBLISH - This option enables the publishing of build artifacts to respective download servers. Build artifacts include report, images and repos.. + This option enables the publishing of build artifacts, including build +reports, images and repos. true PUBLISH_URL - Specify the URL address to publish build artifacts. The format of -<cite>PUBLISH_URL</cite> should be the same as rsync format which can be a local -path or remote url like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. -This option only take effect if PUBLISH is enabled. + This option specifies the URL address to publish build artifacts. The +format of PUBLISH_URL must be the same as rsync format, which can be a +local path or remote URL like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. @@ -185,7 +198,7 @@ This option only take effect if PUBLISH is enabled. false false false - + false diff --git a/jenkins-jobs/configs/GBS-local-full-build/config.xml b/jenkins-jobs/configs/GBS-local-full-build/config.xml index e2d63f1..7eb5d58 100644 --- a/jenkins-jobs/configs/GBS-local-full-build/config.xml +++ b/jenkins-jobs/configs/GBS-local-full-build/config.xml @@ -1,57 +1,63 @@ - This jenkins job is used to build Tizen sources. -This job is based on <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> and <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system">GBS</a>. Developers can reconfigure -this job to run periodically, of course can be triggered at anytime needed.</p> -<p>With <strong>PUBLISH</strong> enabled, build artifacts, including build reports, repos and -images, will be synchronized to respective download servers.</p> -<p><strong>Note:</strong> To get a better understanding of this job, it is highly recommended -that the following document, which provides instructions of the corresponding -manual operations, is read and well understood: -<a class="reference external" href="https://source.tizen.org/documentation/developer-guide/creating-tizen-image-scratch">Creating a Tizen Image from Scratch</a></p> -<p>The following options are supported by this jenkins job:</p> + <p>This job is designed for Tizen package building, image creation and build +artifacts publishing by using <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> and <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system">GBS</a> as basis. It can be reconfigured +to run periodically or be manually triggered whenever needed.</p> +<p>With <strong>PUBLISH</strong> option enabled, build artifacts, including build reports, +repos and images, will be synchronized to respective download servers.</p> +<p>Before using this job, it is highly recommended that <a class="reference external" href="https://source.tizen.org/documentation/developer-guide/creating-tizen-image-scratch">Creating a Tizen Image +from Scratch</a> , which is the manual equivalent of this job, is read and well +understood.</p> +<p>Supported options are shown below:</p> <dl class="docutils"> <dt><tt class="docutils literal">MANIFEST_URL</tt></dt> -<dd><p class="first">The manifest url, which should be recognized by <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, -for example: <cite>review.tizen.org:scm/manifest</cite>, where <cite>review.tizen.org</cite> -is the alias name set in ~/.ssh, like:</p> -<pre class="literal-block"> -Host review.tizen.org +<dd><p class="first">This option specifies the manifest URL, which will be recognized by the +<a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, for example, in <cite>tizen:scm/manifest</cite>, +<cite>scm/manifest</cite> is the manifest path in remote tizen.org Gerrit, whereas +<cite>tizen</cite> is the alias set in ~/.ssh/config, an example of +~/.ssh/config is shown below:</p> +<pre class="last literal-block"> +Host tizen review.tizen.org Hostname review.tizen.org Port 29418 User &lt;username&gt; #ProxyCommand connect -S &lt;proxy&gt;:&lt;port&gt; %h %p </pre> -<p class="last">and, <cite>scm/manifest</cite> is the manifest path in remote tizen.org gerrit.</p> </dd> -<dt><tt class="docutils literal">MANIFEST_BRANCHES</tt></dt> -<dd>This option specifies the manifest branch used for syncing code, this +<dt><tt class="docutils literal">MANIFEST_BRANCH</tt></dt> +<dd>This option specifies the manifest branch used for synchronizing code, this value will be passed to <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command directly.</dd> <dt><tt class="docutils literal">PROFILE</tt></dt> -<dd>This option specifies the target profile, valid values: <cite>IVI</cite>, <cite>Mobile</cite>.</dd> +<dd>This option specifies the profile used for building, currently, the valid +values are <cite>IVI</cite> and <cite>Mobile</cite></dd> <dt><tt class="docutils literal">ARCH</tt></dt> -<dd>This option specifies the arch to be built, valid values: <cite>i586</cite> and -<cite>armv7l</cite>.</dd> -<dt><tt class="docutils literal">REMOTE_REPOS</tt></dt> -<dd>The remote repos for doing local full build using gbs, and get ks file for -image creation.</dd> +<dd>This option specifies the arch to be built, currently the valid values are +i586 and armv7l.</dd> +<dt><tt class="docutils literal">REMOTE_REPOS (optional)</tt></dt> +<dd>This option specifies the remote repos from which packages are obtained +during package building. Valid remote repos must contans tizen repo data, +including buildata, images and repos in it, for example: +<a class="reference external" href="http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/">http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/</a></dd> <dt><tt class="docutils literal">PARALEL_THREADS</tt></dt> -<dd>This option determines how many builder gbs should run in parallel</dd> +<dd>This option specifies the number of builders GBS runs in parallel. Valid +value is non-negative integer.</dd> <dt><tt class="docutils literal">EXCLUDE_PACKAGES</tt></dt> -<dd>This option specifies the packages that does not participate in building. -And also can be used to break dependency cycles.</dd> +<dd>This option specifies the packages that will be excluded during package +building. This option also can be used to break dependency cycles. Multiple +packages must be separated by comma(,)</dd> <dt><tt class="docutils literal">BUILD_ARGS</tt></dt> -<dd>Specify more gbs build options. For more gbs build options and usage -refer to <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. Default value: empty.</dd> +<dd>This option specifies more GBS build options, which will be passed to <cite>gbs +build</cite> command. Multiple options are supported, different options must be +seperated by space, For more information about gbs build options, refer to +<a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>.</dd> <dt><tt class="docutils literal">PUBLISH</tt></dt> -<dd>This option enables the publishing of build artifacts to respective -download servers. Build artifacts include report, images and repos.</dd> +<dd>This option enables the publishing of build artifacts, including build +reports, images and repos.</dd> <dt><tt class="docutils literal">PUBLISH_URL</tt></dt> -<dd>Specify the URL address to publish build artifacts. The format of -<cite>PUBLISH_URL</cite> should be the same as rsync format which can be a local -path or remote url like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. -This option only take effect if PUBLISH is enabled.</dd> +<dd>This option specifies the URL address to publish build artifacts. The +format of PUBLISH_URL must be the same as rsync format, which can be a +local path or remote URL like: <cite>user&#64;hostname:/path/to/publish_dir</cite>.</dd> </dl> false @@ -59,29 +65,30 @@ This option only take effect if PUBLISH is enabled.</dd> MANIFEST_URL - <p class="first">The manifest url, which should be recognized by <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, -for example: <cite>review.tizen.org:scm/manifest</cite>, where <cite>review.tizen.org</cite> -is the alias name set in ~/.ssh, like:</p> -<pre class="literal-block"> -Host review.tizen.org + <p class="first">This option specifies the manifest URL, which will be recognized by the +<a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command, for example, in <cite>tizen:scm/manifest</cite>, +<cite>scm/manifest</cite> is the manifest path in remote tizen.org Gerrit, whereas +<cite>tizen</cite> is the alias set in ~/.ssh/config, an example of +~/.ssh/config is shown below:</p> +<pre class="last literal-block"> +Host tizen review.tizen.org Hostname review.tizen.org Port 29418 User &lt;username&gt; #ProxyCommand connect -S &lt;proxy&gt;:&lt;port&gt; %h %p -</pre> -<p class="last">and, <cite>scm/manifest</cite> is the manifest path in remote tizen.org gerrit.</p> - +</pre> review.tizen.org:scm/manifest MANIFEST_BRANCH - This option specifies the manifest branch used for syncing code, this + This option specifies the manifest branch used for synchronizing code, this value will be passed to <a class="reference external" href="http://en.wikipedia.org/wiki/Repo_%28script%29">repo</a> command directly. tizen PROFILE - This option specifies the target profile, valid values: <cite>IVI</cite>, <cite>Mobile</cite>. + This option specifies the profile used for building, currently, the valid +values are <cite>IVI</cite> and <cite>Mobile</cite> ivi @@ -91,14 +98,16 @@ value will be passed to <a class="reference external" href="ht REMOTE_REPOS - The remote repos for doing local full build using gbs, and get ks file for -image creation. Example: -http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/ - https://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140214.10 + This option specifies the remote repos from which packages are obtained +during package building. Valid remote repos must contans tizen repo data, +including buildata, images and repos in it, for example: +<a class="reference external" href="http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/">http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140305.14/</a> + ARCH - This option specifies the arch to be built, valid values: <cite>i586</cite> + This option specifies the arch to be built, currently the valid values are +i586 and armv7l. i586 @@ -108,32 +117,36 @@ http://download.tizen.org/releases/daily/tizen/ivi/ivi/tizen_20140212.7/ PARALEL_THREADS - This option determines how many builder gbs should run in parallel. + This option specifies the number of builders GBS runs in parallel. Valid +value is non-negative integer. 4 EXCLUDE_PACKAGES - This option specifies the packages that does not participate in building. -And also can be used to break dependency cycles. + This option specifies the packages that will be excluded during package +building. This option also can be used to break dependency cycles. Multiple +packages must be separated by comma(,) texinfo,aul,gettext BUILD_ARGS - Specify more gbs build options. For more gbs build options and usage -refer to <a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. Default value: empty. - platform/upstream/image-configurations + This option specifies more GBS build options, which will be passed to <cite>gbs +build</cite> command. Multiple options are supported, different options must be +seperated by space, For more information about gbs build options, refer to +<a class="reference external" href="https://source.tizen.org/documentation/reference/git-build-system/usage/gbs-build">gbs build usage</a>. + PUBLISH - This option enables the publishing of build artifacts to respective download servers. Build artifacts include report, images and repos.. + This option enables the publishing of build artifacts, including build +reports, images and repos. true PUBLISH_URL - Specify the URL address to publish build artifacts. The format of -<cite>PUBLISH_URL</cite> should be the same as rsync format which can be a local -path or remote url like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. -This option only take effect if PUBLISH is enabled. + This option specifies the URL address to publish build artifacts. The +format of PUBLISH_URL must be the same as rsync format, which can be a +local path or remote URL like: <cite>user&#64;hostname:/path/to/publish_dir</cite>. @@ -144,7 +157,7 @@ This option only take effect if PUBLISH is enabled. false false false - + false -- 2.7.4