Dear ONAP team I just wanted to add, from the confusion earlier in the TSC meeting.
The CLM job accepts 2 variables in the parameters list: "stream" and "branch". In a project's job block, "stream" is used to just name the job and "branch" defines the value of the revision to check out when the job is executed (branch it will run on). The CLM job in global-jjb has these two variables defined as "master" by default and is up to the teams to change these variables values for jobs not running for master. In case the teams want to define more than one branch, here is the best way to do it in such a way that both name of the job and revision of the job will reflect the proper branch: Here is an example: https://gerrit.onap.org/r/#/c/74599/ For more details, here is the actual CLM job definition: https://github.com/lfit/releng-global-jjb/blob/master/jjb/lf-maven-jobs.yaml#L101 Please let me know for further questions. Thanks! Jess On Wed, Dec 12, 2018 at 2:56 PM <[email protected]> wrote: > Dear ONAP team. > > This is a reminder for adding your Casablanca branch to CLM. > As a reminder from my previous email, you can decide to add just > "casablanca" or have both "master" and "casablanca" > running. That is completely up to the tech team. > > I am still waiting for action on these particular projects who must have > "casablanca" running in CLM: > AAI > APPC > CCSDK > DCAE > Integration > OOM > OOF > Policy > SDC > SDNC > SO > > Thanks so much and please reach out in case you have questions > Jess > > > On Thu, Dec 6, 2018 at 12:33 PM Jessica Wagantall < > [email protected]> wrote: > >> Dear ONAP team and PTLs, >> >> I would like to clarify the current behavior of our Nexus IQ CLM reports >> as of today. >> >> Currently, IT IS possible to run CLM branches for more than one branch at >> a time. >> There is just one limitation which I would like to explain in the >> following example. >> >> If the tech team decides to run maven-clm for more than one branch, please >> keep in mind that the reports would need to be fetched through the >> Jenkins job >> link (for example >> https://jenkins.onap.org/view/CLM/job/aaf-authz-maven-clm-master/24 >> <https://www.google.com/url?q=https://jenkins.onap.org/view/CLM/job/aaf-authz-maven-clm-master/24&sa=D&source=hangouts&ust=1544197805032000&usg=AFQjCNH2mXt9c7Goktd_qPRgtbpAPV_bMA> >> /) >> rather than browsing into >> https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/violations >> <https://www.google.com/url?q=https://nexus-iq.wl.linuxfoundation.org/assets/index.html%23/reports/violations&sa=D&source=hangouts&ust=1544197805032000&usg=AFQjCNFYsPCi5D3ZtOtOxUE-VWZF63-20A> >> directly. The reason behind this, when CLM runs for more than one branch, >> the pool of reports >> in nexus-iq.wl.linuxfoundation.org will display the report for the >> branch that ran last. >> >> For now, we need to make sure the following teams have their casablanca >> branch running in CLM: >> AAI >> APPC >> CCSDK >> DCAE >> Integration >> OOM >> OOF >> Policy >> SDC >> SDNC >> SO >> >> Can the PTL's please help me adding the needed changes to your project's >> yaml files? (Whether is >> running master, casablanca or both I would leave it to the PTL to decide >> which approach is more >> comfortable. I would be happy to review your changes. >> >> Thanks so much again! Please feel free to let me know for any questions. >> Jess >> >> >> > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#14482): https://lists.onap.org/g/onap-discuss/message/14482 Mute This Topic: https://lists.onap.org/mt/28743322/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
