Merge lp:~milo/linaro-ci-dashboard/xml-chaining-definition into lp:linaro-ci-dashboard

Proposed by Milo Casagrande
Status: Merged
Approved by: Stevan Radaković
Approved revision: 31
Merged at revision: 31
Proposed branch: lp:~milo/linaro-ci-dashboard/xml-chaining-definition
Merge into: lp:linaro-ci-dashboard
Diff against target: 39 lines (+32/-0)
1 file modified
HACKING (+32/-0)
To merge this branch: bzr merge lp:~milo/linaro-ci-dashboard/xml-chaining-definition
Reviewer Review Type Date Requested Status
Stevan Radaković documentation Approve
Review via email:

Description of the change

This adds a section in the HACKING file about loop chaining and the XML format used to exchange information between loops.

XML format will probably be expanded, this is the initial definition.

To post a comment you must log in.
Revision history for this message
Stevan Radaković (stevanr) wrote :

Looks good.
Approve +1.

review: Approve (documentation)

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'HACKING'
2--- HACKING 2012-08-24 08:40:11 +0000
3+++ HACKING 2012-08-30 10:11:37 +0000
4@@ -48,3 +48,35 @@
5 `dashboard/'.
7 Tests should be written and defined inside each sub-application.
9+= Loop Chaining =
11+Loop chaining in the linaro-ci-dashboard is a mechanism to use output from one
12+loop as input for another loop. Loops have to be "chainable", in the sense that
13+output of one must be valid to be used as the input of another one.
15+== XML Format Definition ==
17+This is the XML format definition for loop-chaining, with DTD and simple
20+<?xml version="1.0" encoding="UTF-8"?>
21+<!DOCTYPE loop [
22+ <!ATTLIST loop (name, type) PCDATA #REQUIRED>
23+ <!ATTLIST loop (next) CDATA #OPTIONAL>
24+ <!ELEMENT description (#PCDATA)>
25+ <!ELEMENT restricted (#PCDATA)>
26+ <!ELEMENT official (#PCDATA)>
27+ <!ELEMENT fields (field+)>
28+ <!ELEMENT field (#PCDATA)>
29+ <!ATTLIST field (name, type) PCDATA #REQUIRED>
31+<loop name="" type="" next="">
32+ <restricted></restricted>
33+ <official></official>
34+ <fields>
35+ <field name="" type=""></field>
36+ <field name="" type=""></field>
37+ <field name="" type=""></field>
38+ </fields>


People subscribed via source and target branches