You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently working on a project where we're integrating 1Password for credential management in our Jenkins pipelines. Specifically, we're looking to replace the static credentialsId usage in the StashNotifier plugin with dynamically fetched credentials (username/password) from 1Password.
I was wondering if there's an existing way to achieve this with the StashNotifier plugin? Is it possible to override the credential collection method to accommodate dynamic fetching of username and password? Alternatively, would using a temporary Jenkins credential for each build be a recommended approach?
Any guidance or suggestions you could offer would be greatly appreciated. I'm also open to assisting in testing any potential solutions or contributing to the plugin's development to support this feature.
Thank you for your time and for maintaining this valuable resource.
Best regards,
Ademord
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered:
What feature do you want to see added?
Hello StashNotifier Team,
I'm currently working on a project where we're integrating 1Password for credential management in our Jenkins pipelines. Specifically, we're looking to replace the static
credentialsId
usage in the StashNotifier plugin with dynamically fetched credentials (username/password) from 1Password.I was wondering if there's an existing way to achieve this with the StashNotifier plugin? Is it possible to override the credential collection method to accommodate dynamic fetching of username and password? Alternatively, would using a temporary Jenkins credential for each build be a recommended approach?
Any guidance or suggestions you could offer would be greatly appreciated. I'm also open to assisting in testing any potential solutions or contributing to the plugin's development to support this feature.
Thank you for your time and for maintaining this valuable resource.
Best regards,
Ademord
Upstream changes
No response
Are you interested in contributing this feature?
No response
The text was updated successfully, but these errors were encountered: