Description of problem:
According to this document
I should be able to set parameters in the pipeline build config like this
- name: "FOO"
When ever I do this, I am just seeing it get skipped.
Version-Release number of selected component (if applicable):
[root@drlosm02 ~]# openshift version
Steps to Reproduce:
1.As per description
I am able to set an env var through `oc edit` using a recent version of the client . I was able to reproduce the error received when setting an env var through `oc set env bc/...` however. I will look into this further.
In the meantime, would you mind providing the client version used? (oc version / openshift cli version).
Providing client information for the above comment:
$ oc version
@bparees I am able to use `oc edit` to add an environment variable to a build-config with the `JenkinsPipeline` strategy in a 3.6 and 3.7 cluster.
Per comment 0, it appears that a 3.5 server is being used. I was wondering if we just did not support env vars on JenkinsPipeline build-configs back then, and if we should just recommend using a newer version of the cluster for this?
It looks like we did not support those in 3.5:
however if oc set env is not working with 3.6/3.7, that still sounds like a problem.
Thanks, Origin PR to fix `oc set env` on 3.7:
Will open PR against 3.6 branch as well.
This patch will not be backported to 3.6 due to its lack of severity. See .
Could set env successfully to pipeline bc via 'oc set env' cmd.
$oc set env bc/sample-pipeline FOO=bar -n xiu
buildconfig "sample-pipeline" updated
features: Basic-Auth GSSAPI Kerberos SPNEGO
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.