| Hi Team, we recently upgraded our jenkins to 2.190.3 and after the upgrade, also upgraded the plugins. Our jenkins system is huge(more jobs/branches/builds) and after the upgrade, at the time of jenkins startup, we see that workflow cps plugin is scanning all the builds which eventually taking jenkins to come up after 3-4hrs. Could you please let us know if this is a normal behavior and if yes, what is needed to startup jenkins immediately? Can we disable the scanning? Below are the messages that we see in the logs: 26-Dec-2019 21:08:25.088 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-integration-api/release%2Fmaster-build-81-oct/1:customer-integration-api/release%2Fmaster-build-81-oct #1] heads:1::1:StepStartNode[id=6, exec=CpsFlowExecutionOwner[customer-integration-api/release%2Fmaster-build-81-oct/1:customer-integration-api/release%2Fmaster-build-81-oct #1]]
26-Dec-2019 21:15:40.442 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-service/master/392:customer-service/master #392] heads:empty-heads
26-Dec-2019 21:16:47.823 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[customer-service/project%2Fcoexistence/470:customer-service/project%2Fcoexistence #470] heads:empty-heads
26-Dec-2019 21:34:14.095 INFO [Finalizing set up] org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.onLoad Completed flow without FlowEndNode: CpsFlowExecutionOwner[joe-application/release%2F16.10.0-master-build-Nov-2019/113:joe-application/release%2F16.10.0-master-build-Nov-2019 #113] heads:empty-heads |
