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

Improve identification of workflow runs to generate packages #187

Closed
Tostti opened this issue May 28, 2024 · 0 comments · Fixed by #188
Closed

Improve identification of workflow runs to generate packages #187

Tostti opened this issue May 28, 2024 · 0 comments · Fixed by #188
Assignees
Labels
level/task Task issue type/enhancement New feature or request

Comments

@Tostti
Copy link
Member

Tostti commented May 28, 2024

@wazuh/devel-qa team asked to improve the identification of the workflows runs that generate packages for wazuh-dashboard by adding the OS and Architecture to the titles.

For example:

run-name: Build ${{ inputs.system }} wazuh-manager on ${{ inputs.architecture }} ${{ inputs.is_stage && '- is stage' || '' }} ${{ inputs.checksum && '- checksum' || '' }} ${{ inputs.debug && '- debug' || '' }} ${{ inputs.id }}

Currently, no information is shown at all
image

@Tostti Tostti added type/bug Bug issue level/task Task issue labels May 28, 2024
@Tostti Tostti self-assigned this May 28, 2024
@Tostti Tostti added type/enhancement New feature or request and removed type/bug Bug issue labels May 28, 2024
@Tostti Tostti linked a pull request May 28, 2024 that will close this issue
7 tasks
@wazuhci wazuhci moved this to In progress in Release 4.9.0 May 28, 2024
@wazuhci wazuhci moved this from In progress to Pending review in Release 4.9.0 May 28, 2024
@wazuhci wazuhci moved this from Pending review to Done in Release 4.9.0 May 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
level/task Task issue type/enhancement New feature or request
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant