Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider removing the need for a subdirectory for plugin packages #227

Open
SwooshyCueb opened this issue Aug 7, 2024 · 3 comments
Open

Comments

@SwooshyCueb
Copy link
Member

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.

@korydraughn
Copy link
Contributor

The use case for this is not clear.

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.

@SwooshyCueb
Copy link
Member Author

So we have it written down somewhere:

Distro os_specific_directory
Debian 11 Debian gnu_linux_11
Debian 12 Debian gnu_linux_12
Ubuntu 20.04 Ubuntu_20
Ubuntu 22.04 Ubuntu_22
Ubuntu 24.04 Ubuntu_24
CentOS 7 Centos linux_7
Almalinux 8 Almalinux_8
Almalinux 9 Almalinux_9
Rocky Linux 8 Rocky linux_8
Rocky Linux 9 Rocky linux_9

@trel
Copy link
Member

trel commented Aug 19, 2024

ew, those spaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants