Skip to content
This repository was archived by the owner on Mar 13, 2021. It is now read-only.

For in-cluster builds, use RUN_IMAGE from build template #1082

Conversation

glyn
Copy link
Contributor

@glyn glyn commented Jan 28, 2019

... rather than hard-coded default

Fixes #1081

@glyn glyn requested a review from scothis January 28, 2019 14:45
@scothis scothis merged commit e0d765f into projectriff:master Jan 28, 2019
@ericbottard
Copy link
Contributor

Isn't that going to break PFS?

@glyn
Copy link
Contributor Author

glyn commented Jan 28, 2019

Isn't that going to break PFS?

Not really. It would only break PFS if in-cluster builds didn't work with the build template, but then the user could edit the build template RUN_IMAGE value rather than attempting to pass a value using an environment variable (which I think should be reserved for local builds).

@ericbottard
Copy link
Contributor

How do we pass the relocated image value now then?

@glyn glyn deleted the 1081-use-RUN_IMAGE-from-build-template-in-cluster branch January 29, 2019 08:54
@glyn
Copy link
Contributor Author

glyn commented Jan 29, 2019

For in-cluster builds, the relocated image value should come from the build template.

@ericbottard
Copy link
Contributor

The build template uses a BuildTemplate variable. How does that variable gets its value is my point.
You're saying it will use the default value (after it has been rewritten by relocation)? If so, then it shouldn't be a BuildTemplate parameter at all, don't you agree?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants