Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

This is a draft page to be discussed with Integration team to define priorities for Guilin


X-projects

  • Maintain java11
  • create python3.8 baseline image

Repositories

  • Adopt the approach to create a repo for new use cases / simulators
  • Add linters to all the new repositories
  • Add new linters (tobot, bashate, rst)
  • How to get a consistent view on all the repositories, shall we tag all the repositories,..
  • update xtesting repo and put in place the build chain in ONAP (move from gitlab.com to ONAP)
  • update jave/python3.8 in ONAP (move from gitlab.com to ONAP)

Robot pod

  • Adopt micro-service approach introduced by Daniel (propto in F)
  • move the helm chart back to OOM

Use case support

  • Write an documentation 'Use case guideline"
  • Test creation of an override.yaml per use case to be able to deploy adhoc environment in windriver

Tests

  • update the tests
  • clean? are all the tests still maintained?
  • archive CIST? => projects can bring back their tests in their repository but jenkins CSIT not needed anymore
  • move some of the CIST tests in Daily CI
  • introduction of python_sdk for new tests (deprecate onap-tests)
  • improve security tests (Integration and Built Tests For Releases)
  • How to measure the test coverage?
  • How to get better healthcheck tests and "force" project to update them when they provide a new version of their code

Labs


CI/CD

  • improve CI chains and CI testing gate
  • new smoke use case (vFW CL....CDS, )
  • integration of Portal GUI tests
  • finalize windriver/gitlab.com pipelines
  • introduce a weekly CI chain including robustness tests



  • No labels