When creating a CI/CD job, what does defining Source Control Management (SCMcredentials enable?

Question

Options

• ARetrieving your project from SCM when its build is triggered
• BManaging your SCM credentials
• CModifying your project source code automatically

• A
  88% (45)
• B
  4% (2)
• C
  8% (4)

Explanation

Defining SCM credentials in a CI/CD job tells the build system how to authenticate with your version control system (Git, SVN, etc.) so it can pull down your source code when a build is triggered - this is option A. Without these credentials, the CI/CD server has no way to clone or checkout your repository, so the pipeline can't even begin. Option B is wrong because CI/CD job configuration uses credentials to access SCM; it doesn't provide a management interface for storing or rotating those credentials (that's handled by a secrets manager or the SCM platform itself). Option C is wrong because CI/CD pipelines read your source code to build and test it - they don't autonomously rewrite it.

Memory tip: Think of SCM credentials as the key to the front door - the CI/CD server needs that key to get in and grab your code before it can do anything else.

No community discussion yet for this question.