Skip to content

Update release branch UTF test branch - #677

Open
stefan-silabs wants to merge 5 commits into
release_2.9-1.6from
update_utf_test_branch_release
Open

Update release branch UTF test branch#677
stefan-silabs wants to merge 5 commits into
release_2.9-1.6from
update_utf_test_branch_release

Conversation

@stefan-silabs

Copy link
Copy Markdown
Contributor

Issue Link:

Description of Problem/Feature:
Wrong UTF branch for release_2.9-1.6

Description of Fix/Solution:
Update branch name

Testing Done:
CI

@stefan-silabs
stefan-silabs requested a review from a team as a code owner May 6, 2026 13:46
Comment thread jenkins_integration/Jenkinsfile Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be simple to have it only controlled by SQA_UTF_BRANCH variable and no added logic?

if (env.CHANGE_TARGET == null) {
utf_branch_name = SQA_UTF_BRANCH
} else {
if (env.CHANGE_TARGET.startsWith("release_")) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you please explain the logic why we are using main , if its not release_.

for example i have feature branch on release and i have a sub branch on my feature branch, when i try to merge a PR from sub branch into my feature branch,it will pick main right?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

are you expecting to have CI running when you merge your sub branch into your feature branch?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants