Dear ONAP team, I have been working on re-writing out CLM job definitions under ci-management/jjb/*
The idea is to isolate the CLM portion of the job similar to how we have it for the Sonar one. This is in preparation for two things: - The new changes that we will be working in global-jjb to allow teams to define an application name for each job so that the entry in IQ looks like "onap-aai-aai-common" for example. As you know, The same IQ server is shared with many projects so adding this prefix will help in cases where 2 projects have the same repo name. This change will be easier to apply on an isolated job block. - CLM works best when running in master. We have had cases where adding several branches in CLM causes the reports to be overwritten since we do not have control of which branch runs first, so the prevailing report will be from the last branch that was ran on. If teams really desire to switch branches, they can still do so in the CLM block but let's keep it running for just 1 branch at a time to avoid confusions with the resulting reports. You can find my work here: https://gerrit.onap.org/r/#/q/topic:clm-project-refactor I will be adding the PTLs to these changes and review them once more. Please help me reviewing and +1 the change if you agree with it. Thank you AAI for having this all in place already :) Thanks so much! Jess -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#13180): https://lists.onap.org/g/onap-discuss/message/13180 Mute This Topic: https://lists.onap.org/mt/27486959/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
