I am facing with this problem. As Veracode User and Veracode Password are set globally in Jenkins configuration, it is not possible for me to parameterized jenkins builds based on these settings.
I explain a bit further: Because of different roles in a developer team, not all of users can have Veracode credentials to submitt code for review. It should be necessary that these parameters can be entered programatically for security reasons and also for tracking actions. As they are globally, someone who can run a task in Jenkins can initiate an upload of code for static review with global settings.
Is it possible in newer versions to add these configurations inside Tasks (like actual Files to scan or Application Name)?
rnt
commented
7 years ago
I am facing with this problem. As Veracode User and Veracode Password are set globally in Jenkins configuration, it is not possible for me to parameterized jenkins builds based on these settings.
I explain a bit further: Because of different roles in a developer team, not all of users can have Veracode credentials to submitt code for review. It should be necessary that these parameters can be entered programatically for security reasons and also for tracking actions. As they are globally, someone who can run a task in Jenkins can initiate an upload of code for static review with global settings.
Is it possible in newer versions to add these configurations inside Tasks (like actual Files to scan or Application Name)?
Thanks in advance. Regards