<feed xmlns='http://www.w3.org/2005/Atom'>
<title>openstack/kolla.git/tools/validate-json.sh, branch version-m2</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<id>https://git.platform-os.org/openstack/kolla.git/atom?h=version-m2</id>
<link rel='self' href='https://git.platform-os.org/openstack/kolla.git/atom?h=version-m2'/>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/'/>
<updated>2014-10-14T19:21:22+00:00</updated>
<entry>
<title>add better validation checks (part 1)</title>
<updated>2014-10-14T19:21:22+00:00</updated>
<author>
<name>Lars Kellogg-Stedman</name>
<email>lars@redhat.com</email>
</author>
<published>2014-10-14T16:17:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=bfbf1b8c9b3a0abba86474aeb72b950142723d73'/>
<id>urn:sha1:bfbf1b8c9b3a0abba86474aeb72b950142723d73</id>
<content type='text'>
This patch adds a script for validating YAML files, and replaces the
existing JSON checks with one largely identical to the YAML check.

This also provides a script that can be installed as a pre-commit hook
that will perform this checks when you commit changes.  You can install
the hook by running tools/pre-commit-hook --install.

Change-Id: Ib4742a9db062362cfa61d669c691151bc1ca376c
</content>
</entry>
<entry>
<title>Rename validate-json target as pep8 and improve it</title>
<updated>2014-10-03T19:18:12+00:00</updated>
<author>
<name>Chmouel Boudjnah</name>
<email>chmouel@enovance.com</email>
</author>
<published>2014-10-03T19:05:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=5aa235066c9628540445b0772eb5332877fde594'/>
<id>urn:sha1:5aa235066c9628540445b0772eb5332877fde594</id>
<content type='text'>
When discussing with the infra guys they have mentioned it would be
easier to call our linting job pep8, it's indeed badly named but that
target has been used all over openstack for linting projects. As a bonus
point it would make things easier to add the job to the gate. To make
that patch much more interesting than a three characters change I have
improved the validate-samples script to detect if jsonlint was present
and if not fallback to the standard python -mjson.tool which give you
less details but nonetheless works if jsonlint is present.

Change-Id: I8d71a229917004dfd7223a16e4f270101cf2f0a8
</content>
</entry>
<entry>
<title>Add validate-json tox target</title>
<updated>2014-10-03T09:59:19+00:00</updated>
<author>
<name>Chmouel Boudjnah</name>
<email>chmouel@enovance.com</email>
</author>
<published>2014-10-03T09:26:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.platform-os.org/openstack/kolla.git/commit/?id=ac0b2a797f3a279fb15728def4016f6156ccfe0a'/>
<id>urn:sha1:ac0b2a797f3a279fb15728def4016f6156ccfe0a</id>
<content type='text'>
This is a simple JSON validation script based on demjson python library,
we do some shell script trickeries to exit properly if there is a
failure for tox (should probably patch demjson to properly exit
instead).

Change-Id: I930908336deef7daeaab5b55ba2031c64698d880
Implements: blueprint json-validation-gate
</content>
</entry>
</feed>
