From the course: Software Testing Foundations: Continuous Testing and DevOps
Join today to access over 22,600 courses taught by industry experts or purchase this course individually.
Credentials and sensitive data - Jenkins Tutorial
From the course: Software Testing Foundations: Continuous Testing and DevOps
Credentials and sensitive data
- [Instructor] In continuous testing strategies it's important to save your credentials and sensitive data somewhere that your test can access them from within the CI solution. It's a good general rule not to save your credentials in your code base. If your test code runs against multiple servers, you don't want hard coded credentials. And of course, no one wants to risk credentials being exposed when access changes to the source code repo. Most continuous integration solutions include a feature for securely storing credentials. Jenkins for example, has built in functionality to store usernames and passwords as secret encrypted credentials and then pass them off to the individual build tasks. Credentials are usually injected through environment variables. This makes it easier to have different credentials and different configurations for different environments. An environment variable is a variable that can be set in…
Download courses and learn on the go
Watch courses on your mobile device without an internet connection. Download courses using your iOS or Android LinkedIn Learning app.