-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
We have separate AWS accounts for each environment. I've noticed that it's unable to set specific AWS account for each job within "Docker Build and Publish" section.
Any ideas how to fix or bypass this bug?
We are facing the same issue on our production Jenkins server. We have a separate AWS account for staging and production. We initially configured staging AWS credential for staging job. It is working fine for staging job. We faced issue when we try to add the production aws credential for production job. When we click the credential plugin tab,it shows the staging account credential two times .We can't select/use the production aws credential for production job. Any help will be greatly appreciated.