Log In | Users | Register
Edit | Attach | New | Raw | Diff | Print | | Tools
You are here: CM » JenkinsOverview

Automated Testing using Jenkins

Jenkins is a useful tool that allows automatic testing of applications on different machines/HPC-centres. It is used to test large Codebases like COSMO or ICON.

Prerequisites

Your Code or appliaction needs to be accessible as a Git repository on either GitHub or GitLab@dkrz. A valid Jenkins account to visit the Jenkins webpage jenkins-mch.cscs.ch to configure your tests is required too.

Why use Jenkins

Scientific applications often run in many different configurations and on different computers accross multiple HPC-centres. Therefore it is very time-consuming to always test all configurations manually. Jenkins helps you the automate the testing of your application and therefore can help to save you a lot of time. Jenkins also helps to ensure the correct functioning of your Code after major refactoring, to avoid surprises that would be discovered at a later stage.

Who should use Jenkins

In general, Jenkins can be used by all people.

Setting up your own Jenkins plan

  • Access - How is the access to Jenkins organized
  • Beginners - Step-by-step guide to your first Jenkins plan
  • Advanced - Jenkins has some nice advanced features

Slaves in Jenkins

  • Slaves - What are slaves in Jenkins

General recommendations

Maintenance (for Jenkins admin)

Jenkins Maintenance page (requires to be in MeteoSwiss group)

CM Web Utilities

spacer
This site is managed by the Center for Climate Systems Modeling (C2SM).
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems? Send feedback!