I think we should avoid the expectation that we are in a container if
and only if we are using GCC5. Instead I would prefer we add a boolean
parameter to allows us to explicitly use the included python. So instead
of the GCC check we would have this.
condition: not(eq('${{ parameters.useIn
On Tue, Sep 20, 2022 at 12:41:35PM -0700, Chris Fernald wrote:
> I think we should avoid the expectation that we are in a container if and
> only if we are using GCC5. Instead I would prefer we add a boolean parameter
> to allows us to explicitly use the included python. So instead of the GCC
> che
Use the Python supplied by the container image.
Signed-off-by: Oliver Steffen
---
.azurepipelines/templates/platform-build-run-steps.yml | 1 +
.azurepipelines/templates/pr-gate-steps.yml| 1 +
2 files changed, 2 insertions(+)
diff --git a/.azurepipelines/templates/platform-build-ru
