Verify Job Xml has the required elements (or automatically add them)

Bug #1385199 reported by Caio Begotti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Capomastro
Triaged
Low
Unassigned

Bug Description

We require a notification plugin element, we could verify that uploaded job xml documents have the necessary elements (or insert them).

From https://github.com/capomastro/capomastro/issues/3

Tags: feature github
Revision history for this message
Daniel Manrique (roadmr) wrote :

I'm not sure why the notification plugin element is required. Also, who does the verification? jenkins or capomastro? If capomastro, we'd have a better idea of where/how to add these things.

I'll set to incomplete so we can discuss this one a bit.

Changed in capomastro:
status: New → Incomplete
importance: Undecided → Critical
importance: Critical → Low
milestone: none → future
Revision history for this message
Caio Begotti (caio1982) wrote :

I think their original idea was to avoid an import of a jobtype into Jenkins with invalid XML data (thus the mention about Notification element), and I suppose it would be Capomastro's job to verify it as the importing is done through it.

Revision history for this message
Daniel Manrique (roadmr) wrote :

ohh fun. So we need capomastro to parse the xml (lxml here we go) and ensure it has the required parameters, and if not, add them itself, or just barf and warn the user? Regardless of behavior, this is clearer now, I think. I'd be interested in seeing whether an xml file produced by lxml still makes jenkins happy. It should!

Changed in capomastro:
status: Incomplete → Triaged
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.