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

ART-11093 add ignore_non_x86_nightlies arg for gen-assembly #1104

Merged
merged 6 commits into from
Dec 19, 2024

Conversation

Ximinhan
Copy link
Contributor

@Ximinhan Ximinhan commented Nov 1, 2024

add ignore_non_x86_nightlies arg, if this arg is checked then it will only use latest accepted x86_64 nightly, default to False.
this arg honors the skip_get_nightlies arg, if skip_get_nightlies is true the input value of nighties set will be used.


Tested with https://art-jenkins.apps.prod-stable-spoke1-dc-iad2.itup.redhat.com/job/hack/job/ximhan/job/build%252Fgen-assembly/5/consoleFull

and it created assembly pr openshift-eng/ocp-build-data#5832
only have x86_64 nightly, but full arch of RHCOS and the brew event come from x86_64 nightly

Copy link
Contributor

@vfreex vfreex left a comment

Choose a reason for hiding this comment

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

Shouldn't this be accomplished by LIMIT_ARCHES?

@Ximinhan
Copy link
Contributor Author

Ximinhan commented Nov 4, 2024

Shouldn't this be accomplished by LIMIT_ARCHES?

they are a little bit different, the LIMIT_ARCH needs to be used with skip_get_nightlies and use the inputted nightly to get candidate_nightlies and rhcos is also limited by that arch config.
but ignore_non_x86_nightlies is trying to skip looking at non-x86_64 nightlies but still gen-assembly as we have full arches, rhcos and builds still use full arches.

if self.skip_get_nightlies:
candidate_nightlies = self.nightlies
elif self.ignore_non_x86_nightlies:
candidate_nightlies = await self._get_latest_accepted_nightly()
Copy link
Contributor

Choose a reason for hiding this comment

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

Looks like setting this option will cause the pipeline completely ignore the --nightly parameter. Is there a way to fix that?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is the design, when ignore_non_x86_nightlies set only use latest accepted x86 nightly.
nightly parameter is used with skip_get_nightlies, if skip_get_nightlies is true the input value of nighties set will be used.

Copy link
Contributor

Choose a reason for hiding this comment

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

you're setting what's supposed to be a var of list of nightlies to a single nightly.. how does that work?
Is this code tested?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

this is what we want, if ignore_non_x86_nightlies is true we only use x86_64 nightly and build the assembly as we did with all arch nightly, we use x86_64 nightly get brew event and get full arch of rhcos from the rhcos version in x86_64 nightly

@Ximinhan Ximinhan added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Nov 19, 2024
Copy link
Contributor

openshift-ci bot commented Dec 19, 2024

@Ximinhan: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 3361b20 link false /test security

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Contributor

@joepvd joepvd left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 19, 2024
Copy link
Contributor

openshift-ci bot commented Dec 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: joepvd

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 19, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit f370fb5 into openshift-eng:main Dec 19, 2024
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants