Description of problem:

when executing the build with jenkins pipeline, the latest jenkins-slave-maven-rhel7 image is pulled (currently as 3.9) even for the OCP version 3.6. Workaround would be to change the latest tag to the desired tag.
The latest image contains oc cli tools 3.9 which are causing the build issue (not compatible).

Also, when checking the default jenkins instance running on openshift, I see that there is no tag specified, so it will always use the latest one.

Version-Release number of selected component (if applicable):
Openshift Container Platform 3.6

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
now the jenkins pulls the latest image - not considering the version of OCP
- example - pulling version 3.9/latest on OCP version 3.6, where jenkins image contains different version of CLI tools (not compatible with actual version of OCP)

Expected results:
by default, the jenkins will get the tag same to the major release of openshift (e.g. 3.7 = image:3.7)

Additional info:
it could be up to admin of the jenkins to specify the correct tag, however, assuming in default configuration to always pull the latest image could cause more issues (especially when running different versions of OCP and images)