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.

Sign up for GitHub

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

Jump to bottom

Version of bpf_conformance tool should be stored in single location #3427

Open
Alan-Jowett opened this issue Apr 3, 2024 · 0 comments
Open

Version of bpf_conformance tool should be stored in single location #3427

Alan-Jowett opened this issue Apr 3, 2024 · 0 comments
Assignees
@mikeagun
Labels
cleanup Affects API usability or code maintainability but not correctness or applicability P2 triaged Discussed in a triage meeting
Milestone
2405

Comments

@Alan-Jowett
Copy link
Member

Currently the URL for the bpf_conformance tool is present in 3 yaml files, 2 in the public GitHub repo and one in an internal fork repo.

The URL should be stored in a shared location to prevent internal and external pipelines from diverging.
@dthaler dthaler added the cleanup Affects API usability or code maintainability but not correctness or applicability label Apr 8, 2024
@dahavey dahavey added the triaged Discussed in a triage meeting label Apr 15, 2024
@dahavey dahavey added this to the 2404 milestone Apr 15, 2024
@Alan-Jowett Alan-Jowett modified the milestones: 2404, 2405 Apr 29, 2024
@shankarseal shankarseal added the P2 label May 1, 2024
@shankarseal shankarseal assigned mikeagun and unassigned Alan-Jowett May 1, 2024
@mikeagun mikeagun changed the title Version of bpf_conformance tool should be shared between ADO and GitHub YAML files Version of bpf_conformance tool should be stored in single location May 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mikeagun mikeagun

Labels
cleanup Affects API usability or code maintainability but not correctness or applicability P2 triaged Discussed in a triage meeting
Projects
None yet
Milestone
2405
Development

No branches or pull requests
5 participants
@mikeagun @dthaler @Alan-Jowett @dahavey @shankarseal