Announcement: Version 3 of OpenDevStack

With great pride we are announcing version 3 of the OpenDevStack. 7+ months of work, > 1000 commits - in short, close to 100% automated test coverage, make based installation, a fully self contained AMI to get you started in minutes, and so many other large and small fixes, to make enterprise installation just fly.

Major new features:

ODS Core

  1. Configurable Bitbucket and Openshift namespace for ODS - to allow multiple ODS installations on the same cluster, side by side
  2. Full end2end support for HTTP PROXY across all components
  3. make based installation for the entire OpenDevStack
  4. Add automated testing to support the verification of an installation
  5. ods-devenv, allowing to setup a fully self contained developer installation (which is the basis for the AMI generation)
  6. A fully self contained Amazon AMI (ODS in a Box 3.x, ami-0d9426211d748fc65) - that you can just start inside your amazon account

ODS Jenkins Shared Library

  1. Merge mro orchestration pipeline and the “original” shared library - into one ods-jenkins-shared-library and refactor to use common services, and also achieve better automated testing coverage
  2. Sonarqube PR request support
  3. Tailor can now be used to directly deploy Openshift resources
  4. Massive simplification of generated jenkins pipelines, common stages, removal of project and componentId
  5. Add stage to deploy to another cluster withOpenShiftCluster during deployment
  6. Add stage to not rebuild, in case image already exists (odsComponentStageImportOpenShiftImageOrElse)

ODS Quickstarters

  1. Add automated tests for all quickstarters
  2. Add code coverage and unit testing steps to quickstarters
  3. Use ods jenkins shared library accross the stack, for provisioning and build of all quickstarters
  4. Quickstarters for core component contributions, namely ods-provisioning-app and ods-document-generation-svc

ODS Provisioning App

  1. Support for Azure ID as identity provider
  2. Preview of modern, Angular based User interface, instead of the thymeleafone
  3. Better, cleaner, and consistently secured APIs across the provisioning application
  4. Add pre-flight testing to ensure provisioning happens only when users, rights, etc. are available in all target systems, especially Atlassian
  5. Simpler, more extensible configuration for custom quickstarters.