[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[libvirt] [jenkins-ci PATCH 12/12] lcitool: Document build action



Provide some examples and scenarios.

Signed-off-by: Andrea Bolognani <abologna redhat com>
---
 guests/README.markdown | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/guests/README.markdown b/guests/README.markdown
index ddf0149..870619e 100644
--- a/guests/README.markdown
+++ b/guests/README.markdown
@@ -46,6 +46,25 @@ related projects, while running
 will update all hosts and prepare them to build libvirt both as a native
 library and, where supported, as a Windows library using MinGW.
 
+Once hosts have been prepared following the steps above, you can use
+`lcitool` to perform builds as well: for example, running
+
+    lcitool -a build -h '*debian*' -p libvirt-python -b master
+
+will fetch libvirt-python's `master` branch and build it on all Debian
+hosts.
+
+This feature can be used to validate a series you've been working on
+will not introduce any CI failures when merged: assuming you have a
+personal clone of `$project` hosted somewhere and your changes are in
+the `feature` branch, you can tweak the value of `git_url` in
+`playbooks/build/projects/$project.yml` so that it points to your own
+repository and then run
+
+    lcitool -a build -h all -p $project -b feature
+
+to spot issues early.
+
 
 Host setup
 ----------
-- 
2.17.1


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]