You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new script (possibly test.sh or validate.sh?) should be created that will get the latest changes from the repo and run a validator against these changes.
Files changed in the most recent commit can be discovered with the command:
git diff-tree --no-commit-id --name-only -r HEAD
This will give a list of paths. Only changes in the collections/ subfolder should be used. These paths can then be passed off to an XML validator, such as xmllint or jing, and validated against the consolidated TEI schema, as well as checking for well-formedness.
The return value of the script should be either 0 (for success) or 1 (for validation errors).
The intent of this script is to use it in a Continuous Integration environment, to check the most recent commits for any errors, and send the committer a report if the build failed.
As an extension to this, other functionality could be built in as desired, including:
Checking authority files for well-formedness and validity
Running the xQuery scripts over just the changed files (if possible?) and reporting any problems with the index file generation.
Once developed, this script could be rolled out to the other catalogues to provide similar testing and feedback.
The text was updated successfully, but these errors were encountered:
A new script (possibly
test.sh
orvalidate.sh
?) should be created that will get the latest changes from the repo and run a validator against these changes.Files changed in the most recent commit can be discovered with the command:
git diff-tree --no-commit-id --name-only -r HEAD
This will give a list of paths. Only changes in the
collections/
subfolder should be used. These paths can then be passed off to an XML validator, such asxmllint
orjing
, and validated against the consolidated TEI schema, as well as checking for well-formedness.The return value of the script should be either
0
(for success) or1
(for validation errors).The intent of this script is to use it in a Continuous Integration environment, to check the most recent commits for any errors, and send the committer a report if the build failed.
As an extension to this, other functionality could be built in as desired, including:
Once developed, this script could be rolled out to the other catalogues to provide similar testing and feedback.
The text was updated successfully, but these errors were encountered: