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
At present, when running plugin tests, the testing environment must be pointed at a directory containing a subdirectory that has the plugin packages. The name of this subdirectory comes from a clunky python function copied from ansible. The use case for this is not clear. Let's consider removing this subdirectory requirement.
The text was updated successfully, but these errors were encountered:
That comes from a time when we used Jenkins. The reason we continued to use it is likely due to the fact that it was quicker (at the time) to leverage the plugin build/test hooks for testing instead of building new functionality from the ground up.
Let's consider removing this subdirectory requirement.
Yes please. We've always wanted to remove that requirement, but other things always took priority.
At present, when running plugin tests, the testing environment must be pointed at a directory containing a subdirectory that has the plugin packages. The name of this subdirectory comes from a clunky python function copied from ansible. The use case for this is not clear. Let's consider removing this subdirectory requirement.
The text was updated successfully, but these errors were encountered: