See our Cytomine-bootstrap project to install it with Docker.
A branch spring-core
has the modification to install the core in its spring version (v4).
WARNING: The current beta version does not support already existing dataset created from previous version. You can only create Cytomine instance with an empty dataset. This will be supported in the final v4.0.0+.
Automated tests require:
- A postgresql with postgis
- A mongodb
- A rabbitMQ
You can simply run the docker-compose configuration from scripts/docker-compose.yml
in order to have all these dependencies up and running with the right configuration.
docker-compose -f scripts/docker-compose-test.yml up -d
Tests can be executed with Gradle:
./gradlew :test
Or via your favorite IDE (right click on /src/test/java
and choose Run Tests in cytomine-core)
After tests, you can shutdown the configuration :
docker-compose -f scripts/docker-compose-test.yml down -v
Execute the main class src/main/java/be/cytomine/CytomineCoreApplication.java
./gradlew bootJar
produce a auto-executable jar under build/libs/cytomine.jar
Run it using:
java -jar /app/cytomine.jar
Default application configuration values are located in src/main/resources/application.yml
.
You can override them by creating a application.yml
or .properties
in the application root directory.
A Jenkins file is provided.
- Retrieve source code from repository
- Compute the current version based on the current commit tag (if a tag has been defined)
git tag -a "v$x.$y.$z"
(e.g. v1.2.3) in order to defne an official releasegit tag -a "v$x.$y.$z-beta.$n"
(e.g. v1.2.3-beta.5) in order to defne an beta release- Otherwise a name will be generated from the branche name and the datetime
- Download core dependencies
- Run postgresql, mongodb and rabbitmq thanks to docker-compose
- Run tests
- Publish tests results reports on Jenkins
- Publish tests coverage reports on Jenkins
- Shutdown postgresql, mongodb and rabbitmq configurations.
- Build and publish a jar
- Build and publish a docker image.
The upgrade only works with a dataset from at least core 3.2.0.
We will provide soon a automated way to upgrade databases
Postgresql database: Regarding Postgresql, nothing to be done. Liquibase should apply changes during the first run.
MongoDB database: As we are moving from MongoDB v2 to v4, the current migration process needs:
- extract the current mongodb database .json / .bson files
- import them using
./scripts/migration/import_mongo.sh
into the new MongoDB 4.x database