All documentation can be found on our website.
See the contribution guidelines
See the Code of Conduct
- argos4j
- argos-docker
- argos-domain
- argos-jenkins-base
- argos-jenkins-plugin
- argos-service
- argos-service-adapter-in-rest
- argos-service-adapter-out-mongodb
- argos-service-api
- argos-service-domain
- argos-test
Java client library for creating,signing and sending link files to the Argos service.
Docker compose file and Docker files used for running the Argos service locally and in the drone build pipeline.
Core domain entities shared between the argos4j and the argos service modules.
Jenkins docker base image used in argos-docker
Plugin for jenkins that uses argos4j library to post signed link files with each build step to the argos service.
Spring Boot Java service to expose the REST API
Incoming adapter implementing the open api REST specification. This api is defined in the argos-service-api module. ( See architecture paragraph )
Outgoing adapter using mongo db to implement the repository interfaces defined in the argos-service-domain module. ( See architecture paragraph )
Open api specification for the Argos Service endpoints.
Domain entities and interfaces specifically for the argos service.
Integration test module to run integration tests locally or as step in a drone pipeline.
export DRONE_SERVER=https://drone.argosnotary.com
export DRONE_TOKEN=<drone token>
drone sign --save argosnotary/argos-parent ./drone.yml