Just some other things I thought of - If you use the credentials file feature you can put all those sensitive properties in a properties file stored as 'jenkins credentials'.
Then pull that props file into your workspace using 'withCredentials' in the pipeline. Next thing is to grab the pipeline utility steps plugin which has a readProperties step (it is not one of the standard pipe plugins - you will need to add it). https://plugins.jenkins.io/pipeline-utility-steps Then you have the file properties loaded as Java properties and you can use them as before. I did this move from Freestyle too and there is a lot to learn but it is worth it. Another recommendation is to look at the declarative pipeline not just scripted pipeline. Declarative has post build handling in the pipeline which you may miss from FreeStyle jobs. In scripted pipeline you have to do a lot of try-catch handling for build errors. Bill On Wednesday, 8 March 2017 08:45:03 UTC, Bill Dennis wrote: > > If you put the pipeline / branch jobs inside a folder, you can scope the > credentials to just that folder. Pretty sure that is available in Jenkins > OSS and not just Enterprise - you need the CloudBees Folders plugin. Have a > look on here, it might have some clues: > https://support.cloudbees.com/hc/en-us/articles/204264974-How-inject-your-Maven-settings-xml-at-folder-level-with-the-Credentials-plugin > > I am not sure if this helps in your branch scenario. I put all my > credentials globally then realised I could scope them to the folder level - > I missed it due to some nuances in the credentials UI. > > Bill > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b3a84fa3-a856-46bb-9356-6c508c97bcf6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
