Skip to content

dsf how to use

travis edited this page Jul 15, 2019 · 10 revisions

How to use it

This is the documentation about shop floor and its different tools. Here you are going to learn how to create new projects, so that they can include continuous integration and continuous delivery processes, and be deployed automatically in different environments.

Prerequisites - Provisioning environment

To start working you need to have some services running in your provisioning environment, such as Jenkins (automation server), GitLab (git repository), SonarQube (program analysis), Nexus (software repository) or similar.

To host those services we recommend to have a Production Line instance but you can use other platforms. Here is the list for the different options:

Step 1 - Configuration and services integration

The first step is configuring your services and integrate them with jenkins. Here you have an example about how to manually configure the next services:

Step 2 - Create the project

Create and integrate git repository

The second is create or git repository and integrate it with Jenkins.

Here you can find a manual guide about how it:

Start new devonfw project

It is time to create your devonfw project:

You can find all that you need about how to create a new devonfw project

cicd configuration

Now you need to add cicd files in your project.

Manual configuration

Jenkinsfile

Here you can find all that you need to know to do your Jenkinsfile.

Dockerfile

Here you can find all that you need to know to do your Dockerfile.

Automatic configuration

cicdgen

If you are using production line for provisioning you could use cicdgen to configure automatically almost everything explained in the manual configuration. To do it see the cicdgen documentation.

Step 3 - Deployment

The third is configure our deployment environment. Here is the list for the different options:

Step 4 - Monitoring

Here you can find information about tools for monitoring:

  • build monitor view for Jenkins. With this tool you will be able to see in real time what is the state of your Jenkins pipelines.

Clone this wiki locally