awatertrevi/infisical
1
0
Fork 0
mirror of https://github.com/awatertrevi/infisical.git synced 2026-09-22 13:39:35 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Fixing some typos

Browse Source
This commit is contained in:
Reza Rahemtola
2023-11-13 15:42:08 +01:00
parent 3aae1b8432
commit 6b334b3103
6 changed files with 53 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
docs/integrations/cicd/jenkins.mdx
View File

@@ -1,11 +1,11 @@
---
title: "Jenkins"
description: "How to effective and securely manage secrets in Jenkins using Infisical"
description: "How to effectively and securely manage secrets in Jenkins using Infisical"
---
Prerequisites:
- Set up and add secrets to [Infisical](https://app.infisical.com).
- Set up and add secrets to [Infisical](https://app.infisical.com).
- You have a working Jenkins installation with the [credentials plugin](https://plugins.jenkins.io/credentials/) installed.
- You have the Infisical CLI installed on your Jenkins executor nodes or container images.
@@ -15,7 +15,7 @@ After setting up your project in Infisical and adding the Infisical CLI to conta
![Jenkins step 1](../../images/integrations/jenkins/jenkins_1.png)
Click on the credential store you want to store the Infisical Service Token in. In this case, we're using the default Jenkins global store.
Click on the credential store you want to store the Infisical Service Token in. In this case, we're using the default Jenkins global store.
<Info>
Each of your projects will have a different INFISICAL_SERVICE_TOKEN though.
@@ -90,7 +90,7 @@ Scroll down to the **Pipeline** section, paste the following into the **Script**
```
pipeline {
agent any
environment {
INFISICAL_SERVICE_TOKEN = credentials('INFISICAL_SERVICE_TOKEN')
}
@@ -99,16 +99,16 @@ pipeline {
stage('Run Infisical') {
steps {
sh("infisical secrets")
// doesn't work
// sh("docker run --rm test-container infisical secrets")
// works
// sh("docker run -e INFISICAL_SERVICE_TOKEN=${INFISICAL_SERVICE_TOKEN} --rm test-container infisical secrets")
// doesn't work
// sh("docker-compose up -d")
// works
// sh("INFISICAL_SERVICE_TOKEN=${INFISICAL_SERVICE_TOKEN} docker-compose up -d")
}
@@ -119,4 +119,4 @@ pipeline {
This is a very basic sample that you can work from. Jenkins injects the INFISICAL_SERVICE_TOKEN environment variable defined in the pipeline into the shell the commands execute with, but there are some situations where that won't pass through properly – notably if you're executing docker containers on the executor machine. The examples above should give you some idea for how that will work.
Finally, click **Build Now** from the navigation sidebar to test your new job.
Finally, click **Build Now** from the navigation sidebar to test your new job.