Skip to content

tkn: update task for azure windows desktop#637

Merged
adrianriobo merged 1 commit into
redhat-developer:mainfrom
anjannath:tkn-update
Oct 16, 2025
Merged

tkn: update task for azure windows desktop#637
adrianriobo merged 1 commit into
redhat-developer:mainfrom
anjannath:tkn-update

Conversation

@anjannath
Copy link
Copy Markdown
Collaborator

@anjannath anjannath commented Oct 16, 2025

replace the use of flag --vmsize with --compute-sizes
flag name was updated in bd2d626

Copy link
Copy Markdown
Collaborator

@adrianriobo adrianriobo left a comment

Choose a reason for hiding this comment

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

Can we switch this to compute-sizes

if [[ "$(params.compute-sizes)" != "" ]]; then
that should be offered there. But I forgot to change here.

@albfan
Copy link
Copy Markdown
Collaborator

albfan commented Oct 16, 2025

In any case, this should use -n (not empty string) instead of -z (empty string) for:

if [[ -z $(params.vmsize) ]]; then cmd+="--vmsize $(params.vmsize) "; fi

@adrianriobo
Copy link
Copy Markdown
Collaborator

@albfan is this breaking your pipelines????

@albfan
Copy link
Copy Markdown
Collaborator

albfan commented Oct 16, 2025

I'm not sure what happens, probably related with fixing empty strings:

#613

In any case, problems with git resolvers on our openshift cluster, make us apply all this task, so we modify manually until we resolve network problems

@adrianriobo
Copy link
Copy Markdown
Collaborator

But are you seeing issues with how those are treated now? he said he tested this with RHEL 🤔

@adrianriobo
Copy link
Copy Markdown
Collaborator

@ppitonak #613 (comment) do you recall what test did you do,...I mean did you test both....compute-size based and non compute-size based?

replace the use of flag `--vmsize` with `--compute-sizes`
flag name was updated in bd2d626
@ppitonak
Copy link
Copy Markdown
Collaborator

@adrianriobo Frankly, I don't remember but this is for Azure and Windows. I definitely didn't test neither of those.

@adrianriobo
Copy link
Copy Markdown
Collaborator

adrianriobo commented Oct 16, 2025

Yeah I know but I am asking them to back port here your code for checking it... so I would trust the AWS work around it :)

Anyway I will give a try, just to ensure as it is not clear to me, and at this moment mostly:

  • CPUs are managed based on params (CPU, Memory,..)
  • GPUs are managed based on compute-sizes

So I need to ensure both options work as expected

@ppitonak
Copy link
Copy Markdown
Collaborator

AWS RHEL task gives top priority to compute-sizes if set. If it is not set, then it propagates other params

if [[ "$(params.compute-sizes)" != "" ]]; then
    cmd+="--compute-sizes '$(params.compute-sizes)' "
else
    cmd+="--arch '$(params.arch)' "
    cmd+="--cpus '$(params.cpus)' "
    cmd+="--memory '$(params.memory)' "
    cmd+="--gpus '$(params.gpus)' "
    cmd+="--gpu-manufacturer '$(params.gpu-manufacturer)' "
fi

Copy link
Copy Markdown
Collaborator

@adrianriobo adrianriobo left a comment

Choose a reason for hiding this comment

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

LGTM

@adrianriobo adrianriobo merged commit e641eef into redhat-developer:main Oct 16, 2025
7 checks passed
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.

4 participants