This document summarizes the development process for the DataverseSSHOC project. It outlines two parallel development tracks - a core development team modifying the Dataverse core functionality, and an application development team creating new tools. Tasks are managed using Trello. Code is stored in GitHub and BitBucket. The development follows a SCRUM process with Docker images available on Docker Hub and a Kubernetes cluster for deployment. Testing includes unit, integration, performance, and A/B testing to comply with CESSDA maturity standards.

1. dans.knaw.nl
DANS is een instituut van KNAW en NWO
The development process in DataverseSSHOC
Vyacheslav Tykhonov
Technical lead,
Senior Information Scientist
(DANS-KNAW, Netherlands)
DataverseEU Kick-Off meeting, 10.04.2019

2. Development teams
DataverseSSHOC project have two parallel tracks of the development:
• Core development team will be working on the modification and extension
of the Dataverse core functionality. All tasks of this team will get label Core.
• The application development team will create new or will integrate existent
tools that will be published on Dataverse App Store website. Tasks of this
team will be labelled as App.

3. Trello for tasks management

4. Source code and issues
• GitHub for the development http://github.com/IQSS/dataverse-docker
• BitBucket for the Cloud infrastructure with secrets

5. Decentralized but centralized development

6. IDE: Eclipse/NetBeans, Maven for building/deployment in containers

7. Development process
We follow SCRUM with quick but small updates, all new functionality will go
through DTAP (Development, testing, acceptance and production ) pipeline:
local (own PC) – test (cloud) – acceptance (cloud) – production (cloud)

8. Docker images
Images will be available on Docker Hub for all collaborators from Dataverse
community and in CESSDA Containers Registry for DataverseSSHOC devops

9. Orchestration
Orchestration is the automated configuration, coordination,
and management of computer systems and software.
(Wikipedia)
DataverseSSHOC tools:
• Docker Compose for the local development and testing
• Kubernetes (K8s) for deployment on Google Cloud (CI/CD
pipeline with Jenkins and Helm on Kubernetes)

10. Testing procedures
• Unit tests (Java) for core development team
• Integration tests (Selenium) for app development team
• Performance/stress tests (Apache JMeter) before Dataverse
will go to Acceptance/Production

11. Testing core functionality and Dataverse apps
Testing process should be compliant with CESSDA services maturity
model https://zenodo.org/record/2591055#.XKR6ny2B2u5
Important: every change of Dataverse functionality should be supplied with
unit test, changes of external functionality should get Selenium scenarios.
Goal: to score as high as possible according to CESSDA maturity model

12. A/B testing