...
- Supporting technical aspects of the FOLIO release management
- Maintaining technical documentation (dev.folio.org) and supporting (e.g. api-lint, api-doc, and dev.f.o/reference/api)
- Maintaining CI/CD pipelines for folio-org repos (Jenkins/Github actions)
- Administering Confluence/JIRA
- Administering folio-org Github Github organization
- Maintaining FOLIO reference environments (folio-snapshot, folio-testing, release-based environments etc)
- Development support:
- Vagrant box dev environment
- FOLIO system integration (new modules, new supporting infrastructure)
...
- Please use the FOLIO Slack channel #hosted-reference-envs for urgent matters regarding hosted reference environments folio-snapshot, folio-testing, etc (build failures, logs, request to rebuild)
- Please use FOLIO Jira FOLIO project for filing tickets with requests for changing configuration or adding new modules or infrastructure into reference environments
- If you are planning to request inclusion of a new module to the reference environment, make sure to prepare the code correctly: https://dev.folio.org/guides/devops-install-backend-module/
What are we working on now?
...
Team member | Organization | Area * |
---|---|---|
Uni Mainz | GitHub, CI/CD Pipelines, Infrastructure | |
Index Data | GitHub, Jira, Jenkins, RefEnv builds, docs | |
Index Data | Infrastructure, Jenkins, GitHub, etc | |
Index Data | Infrastructure (Ansible), Vagrant, etc | |
Index Data | System integration, Infrastructure | |
Index Data | Lead |
Note: area is for information only, please use the public Slack channels or Jira for contacting DevOps and not the engineers directly