How to publish Software
– From GitLab
- Include a
codemeta.jsonmetadata file into the root directory of your project.
- You will need to link your GitLab project with Zenodo.
- Learn how to easily do it in few clicks here.
- Let the GitLab Continuous Integration (CI) work for you !
- Once your GitLab project is connect with Zenodo, copy the following code snippet
- Once your GitLab project is connect with Zenodo, copy the following code snippet into your
– From GitHub
- Include a
codemeta.jsonmetadata file (optional although advised stage).
- Check how to trigger the GitHub-Zenodo automatically integration.
CI integration between GitLab and Zenodo;
Summary / general (and evolving) view of the process:
What happens during the GitLab-Zenodo CI process
– Trigger the GitLabCI and ‘deploy’ your project to Zenodo.
- If you have included the
deploystage into your
.gitlab-ci.ymlfile, the gitlab runner will download and use a Docker container specifically created for this purpose.
- The Docker container is available at the GitLab ESCAPE container registry.
- In this container, there are installed the following packages;
- The distant runner will perform the following stages:
- Search for the last release / commit of your project.
- Search for a CodeMeta metadata file and convert it to the Zenodo compliant format.
- Upload a new entry / version to the ESCAPE2020 community. The entry will contain the information within the metadata files.
– Build an image within the CI/CD gitlab pipeline
- You can also build a Docker and/or a Singularity image within the CI process and upload them to the OSSR
together with the project release.
- See the containerisation page.
You can also check this general quick descriptive maze on how to make an upload to the repository; ESCAPE the maze.