Details
-
Bug
-
Status: Closed
-
Medium
-
Resolution: Won't Do
-
Amsterdam Release
Description
I understand that all projects - even ones providing infrastructure/documentation only should have an amsterdam branch
I should not have to go through this as an architect/developer - ideally verification and our CI system has run through these
There are 4 problematic cases - no amsterdam/release-1.1.0, release-1.1.0 only, or dual amsterdam/release-1.1.0, only master because feature not deployed in amsterdam
For developers the issue is there is no real way to know if a project is beijing only or if the branch is just missing, and for dual release-1.1.0/amsterdam - which branch to commit to
In the process of prototyping the blind tagging poc in OOM-500 ran into
https://gerrit.onap.org/r/#/admin/projects/dcaegen2/analytics,branches
the subproject is OK
https://gerrit.onap.org/r/#/admin/projects/dcaegen2/analytics/tca,branches
Actually there are a lot of projects without branches or with the older release-1.1.0
- posting the list - may will require a LF job
Missing amsterdam because repo should be locked
aai/aai-service - see https://lists.onap.org/pipermail/onap-discuss/2017-November/006191.html
Capitalization (Amsterdam should be amsterdam)
vnfrqts/requirements
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
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
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 alexis.de_talhouet@bell.ca 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
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
clone script being used (old version is still on git - will update shortly) - https://github.com/obrienlabs/onap-root/blob/master/git_recurse.sh
Assigning to myself temporarily - as per TSC discussion 20171221 - but the work needs to be done by each team
Raw data from script obrienbiometrics:onap_1219_11 michaelobrien$ ./git_recurse.sh clone michaelobrien # need to lock this repo - it is not used and was failing Cloning into 'aai-service'... Cloning into 'registrator'... Cloning into 'adaptors'... Cloning into 'core'... Cloning into 'plugins'... Cloning into 'ui'... Cloning into 'dmaapbc'... Cloning into 'authz'... Cloning into 'cadi'... Cloning into 'inno'... Cloning into 'luaplugin'... Cloning into 'babel'... Cloning into 'champ'... Cloning into 'gizmo'... Cloning into 'dashboard'... Cloning into 'esaas'... Cloning into 'blueprints'... Cloning into 'plugins'... Cloning into 'dashboard'... Cloning into 'analytics'... Cloning into 'collectors'... Cloning into 'snmptrap'... Cloning into 'platform'... Cloning into 'registrator'... Cloning into 'buscontroller'... Cloning into 'dbcapi'... Cloning into 'datarouter'... Cloning into 'tools'... Cloning into 'nbi'... Cloning into 'modelspec'... Cloning into 'azure'... Cloning into 'cmso'... Cloning into 'has'... Cloning into 'osdf'... Cloning into 'api'... Cloning into 'gui'... Cloning into 'pap'... Cloning into 'pdp'... Cloning into 'architecture'... Cloning into 'features'... Cloning into 'parent'... Cloning into 'university'... Cloning into 'epics'... Cloning into 'guidelines'... Cloning into 'requirements'... Cloning into 'testcases'... Cloning into 'usecases'... Cloning into 'compliance'... Cloning into 'functest'... Cloning into 'lctest'... Cloning into 'pkgtools'... Cloning into 'validation'... Cloning into 'ansible-ice-bootstrap'... Cloning into 'cms'... Cloning into 'devkit'... Cloning into 'documentation'... Cloning into 'engagementmgr'... Cloning into 'gitlab'... Cloning into 'image-scanner'... Cloning into 'jenkins'... Cloning into 'portal'... Cloning into 'postgresql'... Cloning into 'test-engine'... Cloning into 'validation-scripts'...
Attachments
Issue Links
- blocks
-
INT-359 Versioning For Stable ONAP HEAT/Kubernetes Deployment
- Closed
-
LOG-300 CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
- Closed
-
OOM-471 amsterdam branch
- Closed
-
INT-300 CI-CD For ONAP master branch
- Closed
- is blocked by
-
OOM-529 OOM release-1.1.0 switch to amsterdam branch 20171220 - wiki/links/ followup
- Closed
-
CIMAN-120 Amsterdam Branching for ONAP repos
- Done
- mentioned in
-
Page Loading...