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

Automatic Provisioning: Adapt roles to Jenkins provisioning tool #830

Open
Rebits opened this issue Aug 5, 2022 · 0 comments
Open

Automatic Provisioning: Adapt roles to Jenkins provisioning tool #830

Rebits opened this issue Aug 5, 2022 · 0 comments
Assignees
Labels
qa QA qa-thunder QA support: Vulnerability detector, Wazuh DB, Integrator, Log rotation, Labels, Office 365

Comments

@Rebits
Copy link
Member

Rebits commented Aug 5, 2022

Description

We are currently developing a Jenkins library capable of provisioning any type of environment. For the installation of wazuh components, the roles currently defined in the repository are used. However, we must make a number of changes to integrate these roles with the library.
In order to not modified production branches, we are going to use and maintain qa ansible branches (4.4_qa, master_qa)

Support for custom packages

The continuous integration process requires to test not production packages. However, custom package support is limited in defined roles. Is required to increase this support for wazuh-indexer, wazuh-dashboard, and Windows agent.

Increase agent support

QA testing should be performed on every Wazuh-supported OS. macOS and Solaris are not supported currently, so it is required to add macOS and Solaris support. We will implement a custom package install method for this system, in order to integrate them into de CI.

Integration with Jenkins library

work_to_do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qa QA qa-thunder QA support: Vulnerability detector, Wazuh DB, Integrator, Log rotation, Labels, Office 365
Projects
None yet
Development

No branches or pull requests

2 participants