Skip to content
Snippets Groups Projects
Verified Commit 1d175161 authored by Ubbo Veentjer's avatar Ubbo Veentjer
Browse files

fix: remove deprecated references to Jenkins

parent c3e8a9c7
No related branches found
No related tags found
1 merge request!72Resolve "CESSDA – Decisions"
......@@ -27,12 +27,12 @@ The generic links for all projects are:
- Link: `https://gitlab.gwdg.de/%{project_path}/commits/%{default_branch}`
- Badge image URL: `https://gitlab.gwdg.de/%{project_path}/badges/%{default_branch}/coverage.svg?style=flat-square`
The workflows we are currently using in Jenkins and the GitLab Runner are:
The workflows we are currently using in the GitLab Runner are:
- Code building
- Testing
- Code analyzer (Sonar)
- Packaging (JAR, WAR, DEB, XAR)
- Code analyzer
- Packaging (JAR, WAR, DEB, XAR, Docker Image)
- Distribution (Nexus, APTLY repo, eXist repo)
- Release Management (via GitLab Environments and gitflow)
......@@ -45,26 +45,6 @@ We RECOMMEND to [use GitLab for CI/CD](https://docs.gitlab.com/ee/ci/quick_start
There is a [full and documented example](https://gitlab.gwdg.de/SADE/SADE/blob/develop/.gitlab-ci.yml) of how the
GitLab Runner is used in SADE.
### Sample Configuration of the Jenkins CI (Multibranch Pipelines)
- On commit and push to a <https://projects.gwdg.de> gitolite repo (such as
<https://projects.gwdg.de/projects/tg-crud/repository>), Jenkins on [ci.de.dariah.eu](https://ci.de.dariah.eu/jenkins)
is notified (see projects' gitolite configuration)
- Jenkins then checks out and builds the configured branches (see projects' Jenkins multibranch pipeline
configuration such as <https://ci.de.dariah.eu/jenkins/job/DARIAH-DE-CRUD-Services>.
- Stage *Preparation*: Prepare things
- Stage *Build*: Build, JAR, WAR, and DEB packages from source code, deploy JAR and WAR packages to the [Nexus
repo](https://nexus.gwdg.de). For further information on Nexus cf. the [CI server
documentation](https://wiki.de.dariah.eu/display/FEAD/ci.de.dariah.eu). Jenkins is configured to deploy JARs and WARs
via Maven and a Nexus deploy-account.
- Stage *Publish*: Publish DEB packages to the [DARIAH-DE Aptly Repo](https://ci.de.dariah.eu/aptly). Jenkins uses
a shared library of scripts and publishing is divided into four conditionals: TG version, DH version, SNAPSHOT version,
or RELEASE version due to given version suffixes!
## Continuous Delivery and Continuous Deployment
Continuous Delivery aims at minimizing the [gap between development and production](https://12factor.net/dev-prod-parity)
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment