Skip to content

fix: build-scripts/get_labels_expr.py needs to output "true" in case no labels are found (3.27)#2217

Draft
craigcomstock wants to merge 1 commit intocfengine:3.27.xfrom
craigcomstock:ent-14025/3.27
Draft

fix: build-scripts/get_labels_expr.py needs to output "true" in case no labels are found (3.27)#2217
craigcomstock wants to merge 1 commit intocfengine:3.27.xfrom
craigcomstock:ent-14025/3.27

Conversation

@craigcomstock
Copy link
Copy Markdown
Contributor

e.g. when a build will not include exotics a partial expression is pre-pended to the output of this script

EXOTIX_CONFIGURATIONS_FILTER: (!label.contains("mingw") && !label.contains("HUB") && !label.contains("hpux") && !label.contains("aix") && !label.contains("solaris")) && \

so a true at the end of that expression will be a no-op and appropriate.

Ticket: ENT-14025
Changelog: none
(cherry picked from commit 810e1f9)

…no labels are found

e.g. when a build will not include exotics a partial expression is pre-pended to the output of this script

EXOTIX_CONFIGURATIONS_FILTER: (!label.contains("mingw") && !label.contains("_HUB_") && !label.contains("hpux") && !label.contains("aix") && !label.contains("solaris")) && \

so a true at the end of that expression will be a no-op and appropriate.

Ticket: ENT-14025
Changelog: none
(cherry picked from commit 810e1f9)
@craigcomstock
Copy link
Copy Markdown
Contributor Author

trying this at https://ci.cfengine.com/job/pr-pipeline/13640/

@craigcomstock
Copy link
Copy Markdown
Contributor Author

This is the wrong fix. It causes our exotics testing-pr to build ALL labels available. Will fix.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants