Auto update of planner version to fabric8-ui is broken

[nimishamukherjee]

After #2749 was fixed, we discovered another issue.

Auto update of planner version to fabric8-ui is broken.

Error on fabric8-npm-dependencies:
https://jenkins.cd.test.fabric8.io/blue/organizations/jenkins/fabric8-ui%2Ffabric8-npm-dependencies/detail/master/178/pipeline

[pranavgore09]

@jaseemabid I know you are aware of it but just mentioning here for others that changes made for planner's workaround are needed in here as well

[jaseemabid]

@pranavgore09 Noted. I'll patch npmUpdateOrganisationDependencies.groovy as well.

[joshuawilson]

Can you fix all the build scripts for each of the repos in https://github.com/fabric8-ui

[rupalibehera]

Here is the PR fabric8io/fabric8-pipeline-library#396 from @jaseemabid , need to test it and merge it.

[joshuawilson]

I thought this was NOT going to get merged due to the risk of breaking upstream external projects.

[joshuawilson]

This has started working again, magically.
This also should not be a P0 as the user never sees this.

[piyush-garg]

The release of Fabric8 Kubernetes Model is also facing the issue. Reopening it.

[joshuawilson]

I didn't know we had Fabric8 Kubernetes Model auto releasing to fabric8-ui.

[piyush-garg]

Here is the link to the job I just started after your comment @joshuawilson https://jenkins.cd.test.fabric8.io/job/fabric8io/job/kubernetes-model/job/master/20/console

[pradeepto]

@joshuawilson This is p0 because it blocks releases of few bits - including the jenkins-openshift-sync plugin which is required by Idler.

[joshuawilson]

@pradeepto it looks like you are raising an issue not related to the title. The cause and fix may be related. But does this block Planner (or anything else) from pushing to fabric8-ui?

[jaseemabid]

I probably fixed this as part of #3324. Can we reproduce this again?

@piyush1594 We have fixed k8s-model, right?

[piyush-garg]

@jaseemabid We checked for kubernetes-model and it worked after the fix