Pipeline-as-code with Multibranch Workflows in Jenkins
Note: This is a guest post by Kishore Bhatia. Kishore works for CloudBees, building custom frameworks with Open Source software and helping customers solve engineering problems around continuous delivery and DevOps at scale. This year some great new Jenkins features came out of the butler’s goodie bag - amongst them, the most important one being the ability to realize continuous delivery pipeline
Extending with Shared Libraries
As Pipeline is adopted for more and more projects in an organization, common patterns are likely to emerge. Oftentimes it is useful to share parts of Pipelines between various projects to reduce redundancies and keep code "DRY" [1]. Pipeline has support for creating "Shared Libraries" which can be defined in external source control repositories and loaded into existing Pipelines. A Shared Library
Pipeline
This chapter covers all recommended aspects of Jenkins Pipeline functionality, including how to: get started with Pipeline — covers how to define a Jenkins Pipeline (i.e. your Pipeline) through Blue Ocean, through the classic UI or in SCM, create and use a Jenkinsfile — covers use-case scenarios on how to craft and construct your Jenkinsfile, work with branches and pull requests, use Docker with P
Script Console
Jenkins features a Groovy script console which allows one to run arbitrary Groovy scripts within the Jenkins controller runtime or in the runtime on agents. It is very important to understand all of the following points because it affects the integrity of your Jenkins installation. The Jenkins Script Console: Access is controlled by the Administer permission. Is a web-based Groovy shell into the J
Jenkins 2.0 alphas released
The new Pipeline functionality in Jenkins allows you to define configuration as code, which can be checked in and version controlled along with the rest of your project’s source code. Defining your pipeline’s configuration as code makes it easier to create a simple "build and test" pipeline, while enabling more advanced and complex pipelines through the expressive Groovy-based domain specific lang
Jenkins CLI
Jenkins has a built-in command line interface that allows users and administrators to access Jenkins from a script or shell environment. This can be convenient for scripting of routine tasks, bulk updates, troubleshooting, and more. The command line interface can be accessed over SSH or with the Jenkins CLI client, a .jar file distributed with Jenkins. This document assumes Jenkins 2.54 or newer.
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
Access Control
Pipeline: Groovy
GSoC2019 Working Hours Plugin - UI Improvements
Plugin Installation Manager CLI Tool / Library
Role Strategy Plugin performance
https://www.jenkins.io/sigs/cloud-native/
Introducing the AWS Secrets Manager Credentials Provider for Jenkins
https://www.jenkins.io/files/2016/jenkins-world/large-git-repos.pdf
Sending Notifications in Pipeline
https://www.jenkins.io/doc/book/architecting-for-scale/
Project Governance Document
https://www.jenkins.io/doc/pipeline/
Authenticating scripted clients