-
Sub-task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
None
-
False
-
False
-
ENTESB-14342 - Remove Camel-K 0.3.4 from Fuse Online 7.x
-
%
-
Undefined
-
I think this is easy and requires a few steps.
1. Remove camel-k stuff from the build configuration. To do so, just remove the camel-k and camel-k-runtime elements from the json files from the build
https://github.com/jboss-fuse/fuse-jenkins-pipelines/blob/master/7.8/projects-sb2.json#L506
https://github.com/jboss-fuse/fuse-jenkins-pipelines/blob/master/7.8/projects-sb2.json#L516
2. Remove camel-k stuff from the build pipeline. To do so, edit the Jenkinsfile for 7.8:
https://github.com/jboss-fuse/fuse-jenkins-pipelines/blob/master/7.8/pipelines/sb2/Jenkinsfile#L614
https://github.com/jboss-fuse/fuse-jenkins-pipelines/blob/master/7.8/pipelines/sb2/Jenkinsfile#L630
3. Remove camel-k stuff from the build yaml configuration (this is used to push the configuration to PNC). Remove the following entry on the YAML configuration:
https://github.com/jboss-fuse/fuse-build-yaml/blob/7.x.redhat-7-x/src/main/resources/springboot2.yaml#L627
Then, send the PRs for each of the projects. I think we will need a review from Tom, but I guess that's all.
Once Tom has reviewed the PR, we still need to disassociate camel-k-runtime from the build group on PNC.
To do so:
Go to the build configuration page at http://orch.psi.redhat.com/pnc-web/#/group-configs/549
Then search for camel-k-runtime. Click on remove. Save if needed (I don't think it's needed, but double check).