Team, When running an automated clone of amsterdam as part of the proposal for blind tagging for CI/CD in https://jira.onap.org/browse/OOM-500 and in general doing development changes. Ran into several issues that either need to be fixed or documented so we can work with the correct branch set - raised the issue at the TSC today.
1) Master only repos - those new to Beijing - which are OK right? 2) Master only repos that should be locked - no longer under development 3) Repos with dual release-1.1.0 and Amsterdam branches - which to use for cherry picks - a plan to switch at release or cherry pick now 4) Repos with only release-1.1.0 - plan for cherry picking to a new Amsterdam and removing release-1.1.0 ? 5) Repos with a capitalized Amsterdam branch The list of 60 repos that need clarification are below https://jira.onap.org/browse/INT-373 [https://jira.onap.org/images/icons/emoticons/add.png] Missing amsterdam because repo should be locked aai/aai-service - see https://lists.onap.org/pipermail/onap-discuss/2017-November/006191.html [https://jira.onap.org/images/icons/emoticons/forbidden.png] Capitalization (Amsterdam should be amsterdam) vnfrqts/requirements [https://jira.onap.org/images/icons/emoticons/forbidden.png] Missing both amsterdam and release-1.1.0 - only has master (some may move to Beijing-only which is OK) oom/registrator https://gerrit.onap.org/r/#/admin/projects/oom/registrator,branches ui aaf/authz aaf/cadi aaf/inno aaf/luaplugin ccsdk/dashboard ccsdk/storage/esaas ccsdk/platform/blueprints ccsdk/platform/plugins dcaegen2/analytics dcaegen2/collectors dcaegen2/collectors/snmptrap dcaegen2/platform dcaegen2/platform/registrator dmaap/buscontroller dmaap/dbcapi dmaap/datarouter doc/tools externalapi/nbi modeling/modelspec multicloud/azure optf/cmso optf/has optf/osdf policy/api policy/gui policy/pap policy/pdp sdnc/parent (deprecated?) university vnfrqts/epics vnfrqts/guidelines vnfrqts/testcases vnfrqts/usecases vnfsdk/compliance vnfsdk/functest vnfsdk/lctest (why amsterdam only in vnfsdk/model ?) vnfsdk/pkgtools vnfsdk/validation [https://jira.onap.org/images/icons/emoticons/forbidden.png] Missing amsterdam but has release-1.1.0 (should cherry pick to amsterdam and delete the release-1.1.0 branch) sdnc/adaptors sdnc/core sdnc/plugins ui/dmaapbc https://gerrit.onap.org/r/#/admin/projects/sdnc/adaptors,branches [https://jira.onap.org/images/icons/emoticons/forbidden.png] Ambiguous - has both release-1.1.0 and amsterdam - which is the active amsterdam branch Some like sdnc/northbound and oom have both (oom release-1.1.0 is being removed Friday) - thanks Borislav for reminding and de Talhouet, Alexis [email protected]<mailto:[email protected]> for the quick-in-meeting fix/cherry-picks https://gerrit.onap.org/r/#/admin/projects/sdnc/northbound,branches https://gerrit.onap.org/r/#/admin/projects/oom,branches [https://jira.onap.org/images/icons/emoticons/add.png] no amsterdam branch - but likely because work is only in Beijing (master) - for some of these there is no container in OOM for example yet aai/babel aai/champ aai/gizmo sdnc/architecture sdnc/features vvp/ansible-ice-bootstrap vvp/cms vvp/devkit vvp/documentation vvp/engagementmgr vvp/gitlab vvp/image-scanner vvp/jenkins vvp/portal vvp/postgresql vvp/test-engine vvp/validation-scripts Michael O'Brien Amdocs Technology 16135955268 55268 [amdocs-a] This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
