"No field label conversion function found" issue in Deploy DEV stage

[acuto]

Running the README pristine configuration. Now I'm facing the following No field label conversion function found issue in the Deploy DEV stage:

[Pipeline] stage
[Pipeline] { (Deploy DEV)
[Pipeline] sh

[cicd-tasks-pipeline] Running shell script
+ rm -rf oc-build
+ mkdir -p oc-build/deployments
[Pipeline] sh
[cicd-tasks-pipeline] Running shell script
+ cp target/openshift-tasks.war oc-build/deployments/ROOT.war
[Pipeline] sh

[cicd-tasks-pipeline] Running shell script
+ oc delete bc,dc,svc,route -l app=tasks -n dev

No resources found
[Pipeline] sh

[cicd-tasks-pipeline] Running shell script
+ oc new-build --name=tasks --image-stream=jboss-eap70-openshift:1.5 --binary=true --labels=app=tasks -n dev
--> Found image 0bb6aa7 (4 weeks old) in image stream "openshift/jboss-eap70-openshift" under tag "1.5" for "jboss-eap70-openshift:1.5"

    JBoss EAP 7.0 
    ------------- 
    Platform for building and running JavaEE applications on JBoss EAP 7.0

    Tags: builder, javaee, eap, eap7

    * A source build using binary input will be created
      * The resulting image will be pushed to image stream "tasks:latest"
      * A binary build was created, use 'start-build --from-dir' to trigger a new build

--> Creating resources with label app=tasks ...
    imagestream "tasks" created
    buildconfig "tasks" created
--> Success
[Pipeline] sh
[cicd-tasks-pipeline] Running shell script
+ oc start-build tasks --from-dir=oc-build --wait=true -n dev
Uploading directory "oc-build" as binary input for the build ...

build "tasks-1" started
Error from server (BadRequest): No field label conversion function found for version: build.openshift.io/v1
[Pipeline] }
[Pipeline] // stage

[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE

JBoss imagestreams are imported. Using branch ocp-3.6 with minishift v1.9.0+a511b25. Windows 10 with 16GB RAM. Any ideas? Thanks in advance!

EDITED: problem occurring also using Container Development Kit 3.2.0-1.

[madhushesharam]

I'm stuck here too....