-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
prow: investifgate not exposing any job configuration to the test container #7810
Comments
Our jobs definitely consume:
Other than |
Right but why are they?
|
|
I don't think the podutils should handle these cases. And by exposing these we prevent jobs trying to produce them on their own. |
Those are perfect use-cases, thanks :) The point of this is just to investigate how we are using them and if there is room for another util or not. |
As explained by Ben, we should keep exposing this info to tests. /close |
Follow-up to #7594
We should try to understand the current set of uses that jobs have for the Prow environment variables like
$JOB_SPEC
and determine if all of those use cases are solved by the pod utilities. If they are not, we should write more utilities to handle those cases. Test jobs should not really need infra level config exposed them./area prow
/kind enhancement
/assign
The text was updated successfully, but these errors were encountered: