Nguyen answer but taking care of not storing secrets in source control. Please note that the build project I created in Jenkins was as a Maven Project. Now in the Build section, provide the following command to take the settings.xml file from the checked out projects path(which jenkins copied there for you to use): clean install -s settings.xml.You can also optionally fill in a variable name if you need the configuration to be used in other parts of the build configuration(These come from the Config file provider plugin). Provide a file name(or path relative to your project if you need it like that). Now the key points is to fill in the Target field.

From the file dropdown, choose the file you added in step 3 above.

Goto your project's build configuration, under Build Environment section, check Provide Configuration files option.Provide a name for easy recognition and comment if necessary, then copy paste the xml content to the content area.Click on Add a new Config > Maven settings.xml > Keep the ID unedited(preferably) > Submit.From Jenkins home, goto Manage Jenkins > Managed Files.This is how I avoided that risk(Step by step): The problem with Anh's solution to the problem was that we had to include the settings.xml which might contain credentials(in my case, it had some confidential information), which shouldn't be a part of repository(as highlighted in the comment by sigi).

I came up with a solution combining the question and answer(both from Anh).

Setup nexus repository