Project

General

Profile

bug #7579

Set up pipelines in Jenkins to replace the build pipelines

Added by Andreas Kohlbecker almost 3 years ago. Updated 3 months ago.

Status:
New
Priority:
Priority14
Category:
devOps
Target version:
Start date:
07/24/2018
Due date:
% Done:

0%

Severity:
normal
Found in Version:
Tags:

Description

Our jenkins setup are using the build-pipeline-plugin.

Since Jenkins 2 there is a much better tool to setup pipelines, Jenkins Pipeline

see the following resources for information on how to use it:


Jenkinsfile should be used:

Creating a Jenkinsfile and committing it to source control provides a number of immediate benefits:

  • Automatically creates a Pipeline build process for all branches and pull requests.
  • Code review/iteration on the Pipeline (along with the remaining source code).
  • Audit trail for the Pipeline.
  • Single source of truth [3] for the Pipeline, which can be viewed and edited by multiple members of the project.

History

#1 Updated by Andreas Kohlbecker almost 3 years ago

  • Description updated (diff)

#2 Updated by Andreas Kohlbecker almost 3 years ago

  • Description updated (diff)

#3 Updated by Andreas Kohlbecker 6 months ago

  • Description updated (diff)
  • Category changed from server-maintenance to devOps
  • Priority changed from New to Priority14
  • Target version changed from Unassigned CDM tickets to Release 5.21

Due to the repeated problems during the last relases it has become more important to switch to the "Jenkins Pipelines"

#4 Updated by Andreas Kohlbecker 6 months ago

  • Subject changed from Set up pipelines in Jenkins to relace the build pipelines to Set up pipelines in Jenkins to replace the build pipelines

#5 Updated by Andreas Kohlbecker 5 months ago

  • Tags set to jenkins
  • Target version changed from Release 5.21 to Release 5.22

#6 Updated by Andreas Kohlbecker 3 months ago

  • Target version changed from Release 5.22 to Release 5.26

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)