This is no code changes apart from the supported versions of bitbucket.

Assets3yaml-validator-hook-3.4.1.jar534 KBSource code(zip)Source code(tar.gz)

• © 2020 GitHub, Inc.
• Terms
• Privacy
• Security
• Status
• Help

• Contact GitHub
• Pricing
• API
• Training
• Blog
• About

This release supports multi document yaml files. It's on the existing version of bitbucket, support for later versions to come after testing.

This was a reasonably large update to the plugin to remove dependency on deprecated libraries and update to bitbucket 6

Attempting to delete a branch using git push origin :branchname results in the a failure

Change to check to make sure the path is available before getting the extension in order to avoid a null pointer exception.

Also to fix the display problem identified in Issue #9 - thanks to 9numbernine9 for the pull request.

This was a reasonably large update to the plugin to remove dependency on deprecated libraries and update to bitbucket 6.

Just an update to support the latest version of bitbucket server

The hook fails on pushes with files with no extension

Just a normal update version to the latest version

Normal update of the plugin to the latest version of bitbucket

This can be useful when you are dealing with yaml files with extensions like:

• yml
• sls

For example I could use:

(?i)ya?ml|sls

This is simply an update to the latest version of the plugin to support the latest version of bitbucket server.

Updated the plugin to work with the BitBucket Server 4

Cleaned up unused methodsRemoved having to create a temporary file in order to validate the yaml file, instead using the openfile stream

When a bad file is encountered during an exception condition the finnally clause wasn't being encountered and therefore the input.close() method wasn't being called.

Changing the source compatibility to be 1.7

Fixes issues when a new branch is created so that not all the files are checked - only files on commits that are new.

Minor cosmetic changes to the plugin descriptor.

Links the organisation of the plugin to the source git repository

Removes the individual temp file as opposed to the containing directory in order to attempt to preserve thread safety. With the initial release it was possible for a request to delete the directory while another request is completing the validation.

Initial release