|
Atlassian can provide Subversion hosting for your JIRA or Confluence plugin.
Get a Subversion account
Mail developer-support@atlassian.com and request access. Please include the details about the plugin you would like us to host.
View or checkout from the Subversion repository.
Read-only access is available at http://svn.atlassian.com/svn/public/ or you can browse and query the repository using FishEye. However, if you have commit rights and intend on checking code into the repoistory, you must check out over HTTPS instead of HTTP.
Commit to the Subversion repository
There is an Atlassian-only directory at https://svn.atlassian.com/svn/public/atlassian and a open community directory at https://svn.atlassian.com/svn/public/contrib if you have an account (see above).
Every developer who has an account has full write access to the entire /contrib directory. So be careful about commiting on a project other than yours.
If you import a project, be sure that you put it in the appropriate /JIRA or /confluence directory.
SVN Notify Mailing List
If you would like email notification of all changes to the repository, send an email with the "subscribe" in the body to devnet-svn-request@atlassian.com.
|
Comments (5)
Jan 24, 2006
Jason Dillon says:
What are you guys using for SVN commit emails? I like the HTML version, but nic...What are you guys using for SVN commit emails? I like the HTML version, but nicer to look at. I'd like to see if Apache could use this too.
Jan 25, 2006
Jonathan Nolen says:
I think we're using this package, although I seem to remember someone saying som...I think we're using this package, although I seem to remember someone saying something about some patches from one of the Jive guys that made it prettier.
Jun 18, 2007
Gary S. Weaver says:
Something I didn't know until talking with Jonathan is that even though you can ...Something I didn't know until talking with Jonathan is that even though you can check out from their subversion using an HTTP URL, you should use the HTTPS URL or you'll be unable to commit as your user later. Specifying username may not be important here since it doesn't require a password on checkout:
svn co --username <username provided by Atlassian> https://svn.atlassian.com/<path to project>Then, as long as you checked out as HTTPS and not HTTP, you can specify --username in the commit like this:
Jul 13, 2007
Gary S. Weaver says:
fyi - We were having trouble getting access to commit to svn.repository.com afte...fyi - We were having trouble getting access to commit to svn.repository.com after their change to using Crowd on July 11, 2007. Jonathan replied to us with the following:
(quote)
Yeah, all the DevNet services are now running on a crowd backend. See some background here:
http://blogs.atlassian.com/developer/2007/07/developer_svn_and_jira_will_be.html
http://blogs.atlassian.com/developer/2007/07/developer_network_is_reopened.html
You should be able to visit developer.atlassian.com/jira and reset your password.
If that doesn't work, email jonathan@atlassian.com and jstepka@atlassian.com and one of us should be able to fix you up.
(end quote)
More info:
I personally had an issue logging back into developer.atlassian.com/jira, so I used the "forgot password" link to send me a temp password which I still couldn't use to log back into jira, but could use to auth in svn.atlassian.com so I could commit. Jonathan and Justen are looking into that.
Dec 11, 2007
Gary S. Weaver says:
Just a quick update - all of those problems I was mentioning were resolved month...Just a quick update - all of those problems I was mentioning were resolved months ago with the Atlassian Jira instance and svn.atlassian.com. Everything is great now! Also note that in addition to Atlassian hosted svn, they host Jira projects for contributed projects, and now even support Bamboo (continuous integration) projects for contributed projects.