Tuleap Community Edition development and releases are no longer public. You have until September 30th to download packages and sources in Tuleap project. You can contact the team if you need further assistance.

  •  
     
    story #10211 include SVN plugin disk stats in site stats
Summary
site administrator
include SVN plugin disk stats in site stats
Empty
  • Each nights collect the SVN plugin stats project per project
  • To lower I/O pressure, keep a track, repository per repository, of the last write date (post-commit) to avoid re-commute disk size for projects where no changes were made
  • Take the opportunity for a slight svn service page update
    • Display the last push date (as for git)
    • Order repositories by name (instead of creation order)
    • Add a link to "Settings" repo per repo for svn administrators
Nouha Terzi (terzino), Denis PILAT (denis_pilat), Thomas Gerbet (tgerbet)
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#10211
Manuel Vacelet (vaceletm)
2017-06-20 15:57
2017-05-12 11:53
4534

References
Referencing story #10211

Follow-ups

User avatar

So it’s still weird in Tuleap with a format different from the Subversion part of this file, and not ordered in term of date.

I don't understand what's weird there

Plus, I don't understand how it's related to this story.

User avatar
Thanks

I was wondering about the format.
So it’s still weird in Tuleap with a format different from the Subversion part of this file, and not ordered in term of date.

Cheers,
Denis
User avatar
Did you have a look into Site admin/Statistics/Data export/"SCM statistics" ? and generate the csv file with SVN multiple repo stat ?
If yes can you provide what you get ?
User avatar
Thomas Gerbet (tgerbet)2017-06-05 15:14
  • Status changed from Ready (stalled) to On going
  • CC list Thomas Gerbet (tgerbet) added
User avatar

In REST philosophy, the idea is to chain the calls:

GET /project/:id

-> get the list of resources like /project/:id/svn

GET /project/:id/svn

[
  { "uri": "/svn/123" },
  { "uri": "/svn/124" }
]

-> get the list of repositories with their uris

then you can issue a new REST call based on those uris

If people need/want to deal with names, we can propose REST route like

GET /project/:id/svn?name=foo

to retreive repository named "foo" in project ":id"

 

 

User avatar
I was thinking of people who will use the new (future) REST end-point that requires repo IDs.
It’s not obvious to get repo ID


Cheers,
Denis
User avatar

We can add the ordering to the story but we will need to re-estimate as it's more tricky to do vs. just adding a new column.

Id can be added without much hassle (and re-estimate)

User avatar
Good idea for the layout. I would even add a ordering option on the displayed column (repo name, last push) so that people can choose the order.
The repo ID would also be a good thing to sorte repo by creation date, and will allow user to know the id in case he need it. I suggest for the admin link, you just put an URL behind each Id with naming the column "admin ID". Admin and users will then know that it's a sort link to administration activities

  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Permissions set to