#3059 Update controllers & templates to use new SCM data

v1.0.0
closed
sf-8 (45)
General
2015-08-20
2011-10-21
No

[#2020] set up the new data structures, we should start using them. A total repo refresh is in progress to backfill the data needed.

Related

Tickets: #2020
Tickets: #2138
Tickets: #3060
Tickets: #3759

Discussion

<< < 1 2 (Page 2 of 2)
  • Dave Brondsema

    Dave Brondsema - 2012-05-01

    Commit runs aren't displayed correctly in the commit browser

    • I pushed allura's master@b63bbcab59a4670a41f03dbe7d880d0411458104
    • Then pushed dev@f4e6e2170404cb55d9c802773f5f689bff085470, which includes all of master and then 4 more commits
    • The commit browser should be a straight line, since we keep both dev & master rebased.
    • But it looks like http://screencast.com/t/wnKP6GJk
    • The 4 new commits on dev are the 4 red dots closest to the top, before the green fork. The green "branch" are the commits on master. The #4057 commit should be connected to the #4108 commit instead of the #4125 commit.
    • The parent & child detail links on individual commits look correct to me

    It's not clear to me what branch and/or starting point the commit browser uses (dev? master? last commit?). Perhaps that could be clarified. It's possible that that it's a problem in the browser and the commit runs are correct.

     
  • To ssh://engr.geek.net/forge
    + c1219ac...0017534 tv/3759 -> tv/3759 (forced update)

    Commit run data was fine. There was a bug in the topological sort of commits that was causing the commit graph to render incorrectly. Fixed that and added a test. Also did a visual comparison of the graph to:

    git log --graph --pretty=oneline --abbrev-commit dev
    

    and found that they matched. There are some minor differences in the rendering, but the branches are consistent.

     
    • status: in-progress --> code-review
     
  • Dave Brondsema

    Dave Brondsema - 2012-05-08
    • status: code-review --> closed
     
  • Dave Brondsema

    Dave Brondsema - 2012-05-08

    Not merging - [#4142] will be responsible for that.

     

    Related

    Tickets: #4142

<< < 1 2 (Page 2 of 2)

Log in to post a comment.