Hi Jeremy,
Sorry that this repo is unavailable. However this guide was created for a much older version of Jira several years ago. At the time we did provide a repo with some scripts that you could use to do this kind of performance testing with Jira.
But since that time, the original repo with that name was deleted from the site long ago. Atlassian has not provided this script for several years at this point.
What I just discovered is though that one of our internal development teams, doing performance testing of their own created a new repo with the same name as the old one. As such, yourself and other users trying to follow that guide have been getting this access denied error instead of this repo cannot be found error.
Either way, this isn't going to work and we currently do not have open source version of this code that could be used. So we're kind of stuck here at the moment. However this KB should have been updated to reflect this information long ago. The fact that it has been sitting so long is a problem that I am working to correct now.
For the time being I have removed that KB guide from public view on our site. It might be possible for us to restore this at a later time, but since the entire procedure of that guide is dependent upon being able to get those scripts, I don't see the benefit of keeping this KB up since it is only likely to cause more frustration that it doesn't work yet.
In my research of this problem I came across the request of https://jira.atlassian.com/browse/JRASERVER-63885 which is a request to publicly provide the scripts used to do performance testing on Jira. It isn't clear to me if this is using the Grinder application or some alternative method. However I would recommend watching this request for updates.
Regards,
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.