In SKARA-1655 we added a jcheck check to verify the format of .jcheck/conf itself. Unfortunately, this didn't help quite as well as I would have liked. The problem I wanted to solve was that PRs are currently validated using the .jcheck/conf in the target branch, but after being integrated, any change in .jcheck/conf will not have been tested. Simply checking that the .jcheck/conf file can be parsed isn't enough.
The proper fix here is to check if the PR contains a change to .jcheck/conf and if so we have to run Jcheck twice, once with the .jcheck/conf in the target and once with the new one in the source.
The proper fix here is to check if the PR contains a change to .jcheck/conf and if so we have to run Jcheck twice, once with the .jcheck/conf in the target and once with the new one in the source.
- is blocked by
-
SKARA-1716 Revert SKARA-1655
-
- Resolved
-