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
Basically, it is so far a requirement for the dashboard-plus macro that the builds information on your jenkins instance can be read anonymously.
Is this an issue for you?
I am not clear what would be the most appropriate solution for that case and where the jenkins credentials should be finally stored on the confluence side. Maybe on the Confluence administration side, meaning your confluence administrator should manage your jenkins credentials there. Would this be an option for you?
I need to push this. There are several scenarios in production where anonymous access to jenkins isn't possible. At least it should be possible to state credentials in the macro setup. Just add an username and password field.
when jenkins need authority, how to use it?
The text was updated successfully, but these errors were encountered: