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

Custom resource generation should always use a fixed tooling version #5903

Closed
squakez opened this issue Oct 24, 2024 · 0 comments · Fixed by #5966
Closed

Custom resource generation should always use a fixed tooling version #5903

squakez opened this issue Oct 24, 2024 · 0 comments · Fixed by #5966
Labels
area/continuous integration Related to CI and automated testing
Milestone
2.6.0

Comments

@squakez
Copy link
Contributor

squakez commented Oct 24, 2024

Originally posted by @squakez in #5865 (comment)

The problem is that we assume the user has already the software required to make generate. This may not be true or, the version used by the user may be different. We must find a way to align and have always the same version instead.
@squakez squakez added the area/continuous integration Related to CI and automated testing label Oct 24, 2024
@squakez squakez added this to the 2.6.0 milestone Oct 24, 2024
squakez added a commit to squakez/camel-k that referenced this issue Nov 28, 2024
@squakez
chore(ci): install tooling to keep the same version
774a6e4 
Closes apache#5903
@squakez squakez mentioned this issue Nov 28, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/continuous integration Related to CI and automated testing
Projects
None yet
Milestone
2.6.0
Development

Successfully merging a pull request may close this issue.

chore(ci): install tooling to keep the same version squakez/camel-k
1 participant
@squakez