Repository navigation
This release extends bes-schema-validate to Git External Custom Site files and BigFix Inventory signatures, and gives it a new, compact output format.
⚠️ Upgrade notes
bes-schema-validate(and the deprecatedvalidate-besalias) now checks more files:siteConfig.xml,site.xml,digest.xmlandSignatures/*.xml. These can fail where nothing was checked before.- An Eclipse update-site
site.xmlwill fail. Its plain<site>root matchesSite.xsd(names match without regard to case). Add anexclude:for it (see the README). A.xmlfile whose root has no bundled schema, such as a sitemap or a Mavensite.xml, is skipped. - A repo-local
.xsdis no longer used. If you relied on aFoo.xsdin the repo to validate a<Foo>root, that file now fails with "no schema". - The output format changed. Anything that parses the hook's output needs updating (see below).
Added (bes-schema-validate)
- Git External Custom Site files (
siteConfig.xml,site.xml,digest.xml) and BigFix Inventory signatures (Signatures/*.xml) are now validated against the schemas bundled with validate_bes_xml 2.4.0. The schema is picked by the root tag, apart from.ojofiles, which always useBESOJO.xsd. The.xmlnames are matched case-sensitively, and only signatures directly inside aSignatures/folder are matched. Setfiles:in your own config to change that.
Changed (bes-schema-validate)
- One
path:line: messageline per error (path: messagewhen there is no line number), and nothing for files that pass. The name of every checked file and validate_bes_xml's verbose report are no longer printed. The exit code is still the number of failed files. - Only the schemas bundled with validate_bes_xml are used, for
.besand.ojofiles too. A repo-local copy of a bundled schema was already ignored, since the bundled one won the name clash. - This now needs
validate_bes_xml >= 2.4.1, < 3(was>= 2.3.0). 2.4.0 bundles the site and signature schemas, and 2.4.1 maps.ojo/.BESDomainby file name only, not by the folders above it.
Full Changelog: v1.11.1...v1.12.0