# Anouncing "pluginval" an open-source cross-platform plugin validation tool

**URL:** <https://forum.juce.com/t/anouncing-pluginval-an-open-source-cross-platform-plugin-validation-tool/27710>\
**Category:** Audio Plugins\
**Created:** [May 17, 2018, 12:01pm UTC](https://forum.juce.com/t/anouncing-pluginval-an-open-source-cross-platform-plugin-validation-tool/27710 "2018-05-17T12:01:28Z")\
**Posts on this page:** 1\
**Showing post:** 172

<div class="post-metadata">

**Author:** ![sudara](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/sudara/32/8071_2.png) [@sudara](https://forum.juce.com/u/sudara)\
**Post date:** [June 27, 2022, 10:31am UTC](https://forum.juce.com/t/anouncing-pluginval-an-open-source-cross-platform-plugin-validation-tool/27710/172 "2022-06-27T10:31:51Z")

</div>

> [@PeterRoos](#):
>
> I am curious what the devs who are using it in their pipleline have done, or not done, in order to use Pluginval. Maybe use a much older version of Juce?

I’m running 0.3.0 successfully on [MacOS/Windows in CI](https://github.com/sudara/pamplejuce/actions/runs/2417689453).

Linux is broken, [due to this issue](https://forum.juce.com/t/crash-on-headless-linux-w-xvfb-or-xorg-dummy/51657), which is unfortunate as it’s the cheapest to run regularly in CI…

> [@dave96](#):
>
> That’s hard to do when you only have a few minutes to look at something.

I’ve mentioned before, but I’m more than willing to invest regular time to help keep the project maintained. Pluginval is a critical piece of my infrastructure and I appreciate it very much!

Happy to chat after you’ve had a chance to look at architecture and I can help more with CI and maintenance issues.

> [@dave96](#):
>
> I did this recently with a PR and it broke a lot of things

Yikes, hopefully this wasn’t my last one… 😇

---

_[View the full topic](https://forum.juce.com/t/anouncing-pluginval-an-open-source-cross-platform-plugin-validation-tool/27710)._
