User Requirements for Access to Hosted Subversion

I've been trying to setup an automated release system, by using Bamboo build plans to orchestrate the required steps to release via Maven's release plugin. To this end, I had created a user within our hosted instance, and put that user in both the users and developers groups. My understanding of the support docs suggested this was the critical factor for read/write access, and I do believe it's at least a piece of the puzzle.

However, adding the user to those groups, and then only granting them application access to Bamboo did not allow that user to do even read-only checkouts. I eventually discovered (by trial-and-error) that granting the user Fisheye/Crucible access allowed checkouts (and checkins). While we can keep these permissions, this user is only meant for automation, and we'd prefer to limit the applications it has access to (especially since extra licensing is required for it to have access to Fisheye/Crucible, which it doesn't otherwise need). For instance, though it needs write access to Subversion (due to requirements of the Maven release plugin), but will never need to make any changes that require code reviews, and really doesn't need access to any of the front-end apps at all.

So is this actually a requirement, to grant application access to Fisheye/Crucible for users that need read/write access to Subversion? Or have I missed some wrinkle that would allow us to do this without such access?

If it is required, may I recommend adding something explicit about that in the user docs, as it just wasn't clear to me, even after attempting to find an answer to this in the various forms of online documentation.

1 answer

Hi Jeff,

Note tha FishEye is an interface to embedded OnDemand Subversion, so Subversion users must have FishEye permissions too.


Lucas Lima

Atlassian Support

Suggest an answer

Log in or Join to answer
Community showcase
Renan Battaglin
Published May 18, 2017 in Bamboo

FAQ: How to Upgrade Bamboo Server

Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...

1,096 views 0 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot