DevOps Tools/CI/Jenkins/Configuration
(Created page with "Overview | Continuous Integration (CI) | Source Control Management (SCM) | [[DevOps_Tools/Containerization|C...") |
|||
| Line 1: | Line 1: | ||
[[DevOps_Tools/Overview|Overview]] | [[DevOps_Tools/CI|Continuous Integration (CI)]] | [[DevOps_Tools/SCM|Source Control Management (SCM)]] | [[DevOps_Tools/Containerization|Containerization]] | [[DevOps_Tools/Configuration|Configuration]] | [[DevOps_Tools/Overview|Overview]] | [[DevOps_Tools/CI|Continuous Integration (CI)]] | [[DevOps_Tools/SCM|Source Control Management (SCM)]] | [[DevOps_Tools/Containerization|Containerization]] | [[DevOps_Tools/Configuration|Configuration]] | ||
=[[DevOps_Tools/CI/Jenkins/Configuration|Jenkins Configuration]]= | =[[DevOps_Tools/CI/Jenkins/Configuration|Jenkins Configuration]]= | ||
| + | The goal of this page is to provide some examples of '''post-installation''' configurations. | ||
| + | |||
| + | ==Post-Installation== | ||
| + | Immediately after finishing installation of Jenkins and restarting Tomcat, when you browse to the page, you'll be greeted with a page asking for an administrator secret code. You can obtain this code easily: | ||
| + | <nowiki>~$ sudo cat /opt/jenkins/secrets/initialAdminPassword | ||
| + | 8dj28DH83d0DJ30h8d1uhd1skdfd</nowiki> | ||
| + | Jenkins will then ask you if you want to install some common plug-ins from a pre-defined list, which i've always done, or manually select what you want (or don't want).<br> | ||
| + | '''Note:''' I would recommend that you install at least (1) plug-in to make sure Jenkins can successfully write to the directories it needs and create files/make changes. Better to find out now than later on. | ||
| + | |||
| + | ==Common Additional Plugins== | ||
| + | Below are some common plugins which i've installed. | ||
| + | ;Gitlab Authentication plugin | ||
| + | :This is the an authentication plugin using gitlab OAuth. | ||
| + | ;Gitlab Hook Plugin | ||
| + | :Enables Gitlab web hooks to be used to trigger SMC polling on Gitlab projects | ||
| + | ;GitLab Logo Plugin | ||
| + | :Display GitLab Repository Icon on dashboard | ||
| + | ;GitLab Plugin | ||
| + | :This plugin allows GitLab to trigger Jenkins builds and display their results in the GitLab UI. | ||
| + | ;Safe Restart Plugin | ||
| + | :This plugin allows you to restart Jenkins safely. | ||
Revision as of 09:47, 4 January 2019
Overview | Continuous Integration (CI) | Source Control Management (SCM) | Containerization | Configuration
Jenkins Configuration
The goal of this page is to provide some examples of post-installation configurations.
Post-Installation
Immediately after finishing installation of Jenkins and restarting Tomcat, when you browse to the page, you'll be greeted with a page asking for an administrator secret code. You can obtain this code easily:
~$ sudo cat /opt/jenkins/secrets/initialAdminPassword 8dj28DH83d0DJ30h8d1uhd1skdfd
Jenkins will then ask you if you want to install some common plug-ins from a pre-defined list, which i've always done, or manually select what you want (or don't want).
Note: I would recommend that you install at least (1) plug-in to make sure Jenkins can successfully write to the directories it needs and create files/make changes. Better to find out now than later on.
Common Additional Plugins
Below are some common plugins which i've installed.
- Gitlab Authentication plugin
- This is the an authentication plugin using gitlab OAuth.
- Gitlab Hook Plugin
- Enables Gitlab web hooks to be used to trigger SMC polling on Gitlab projects
- GitLab Logo Plugin
- Display GitLab Repository Icon on dashboard
- GitLab Plugin
- This plugin allows GitLab to trigger Jenkins builds and display their results in the GitLab UI.
- Safe Restart Plugin
- This plugin allows you to restart Jenkins safely.
