#3060 Delete old scm logic - NEEDS MONGO CMD

v1.0.0
closed
SCM
nobody
2015-08-20
2011-10-21
No

After [#3059], delete the "old" repo data structures from repository.py. Check carefully though, some stuff may still be used. The new models is in repo.py. Also identify the mongo collections that are unused so we can drop them.

The scm.new_refresh setting should become irrelevant after this. Everything should be the "new" logic.

Related

Tickets: #3059
Tickets: #5103

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-06-26
    • status: open --> invalid
    • milestone: forge-backlog --> forge-jun-29
     
  • Dave Brondsema

    Dave Brondsema - 2012-06-26

    Handled already

     
  • Dave Brondsema

    Dave Brondsema - 2012-07-10
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -After [#3059], delete the "old" repo refresh logic and data structures.  See `scm.new_refresh` if statement.
    +After [#3059], delete the "old" repo data structures from repository.py.  The new stuff is in repo.py  Also identify the mongo collections that are unused so we can drop them.
    
    • status: invalid --> open
    • milestone: forge-jun-29 --> forge-backlog
     
  • Dave Brondsema

    Dave Brondsema - 2012-07-10
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1 @@
    -After [#3059], delete the "old" repo data structures from repository.py.  The new stuff is in repo.py  Also identify the mongo collections that are unused so we can drop them.
    +After [#3059], delete the "old" repo data structures from repository.py.  Check carefully though, some stuff may still be used.  The new models is in repo.py.   Also identify the mongo collections that are unused so we can drop them.
    
     
  • Dave Brondsema

    Dave Brondsema - 2012-07-17
    • Description has changed:

    Diff:

    --- old
    +++ new
    @@ -1 +1,3 @@
     After [#3059], delete the "old" repo data structures from repository.py.  Check carefully though, some stuff may still be used.  The new models is in repo.py.   Also identify the mongo collections that are unused so we can drop them.
    +
    +The `scm.new_refresh` setting should become irrelevant after this.  Everything should be the "new" logic.
    
    • milestone: forge-backlog --> forge-aug-10
     
  • Dave Brondsema

    Dave Brondsema - 2012-07-27
    • size: --> 2
     
  • Dave Brondsema

    Dave Brondsema - 2013-05-08
    • Size: 2 --> 0
    • Milestone: forge-backlog --> forge-may-31
     
  • Dave Brondsema

    Dave Brondsema - 2013-05-20
    • Size: 0 --> 2
     
  • Dave Brondsema

    Dave Brondsema - 2013-05-31
    • Milestone: forge-may-31 --> forge-jun-14
     
  • Dave Brondsema

    Dave Brondsema - 2013-06-14
    • Milestone: forge-jun-14 --> forge-jun-28
     
  • Dave Brondsema

    Dave Brondsema - 2013-06-28
    • Milestone: forge-jun-28 --> forge-jul-12
     
  • Cory Johns

    Cory Johns - 2013-07-02
    • status: open --> in-progress
    • assigned_to: Cory Johns
     
  • Cory Johns

    Cory Johns - 2013-07-03
    • status: in-progress --> code-review
     
  • Cory Johns

    Cory Johns - 2013-07-03

    allura:cj/3060
    forgehg:cj/3060

    We can't remove LastCommitDoc_old, unfortunately, because we never ran the mass update script and it's still relying on old data.

     
  • Cory Johns

    Cory Johns - 2013-07-03

    Also, the collections to be removed are:

    • project-data.last_commit_for
    • pyforge.repo_object
     
  • Tim Van Steenburgh

    • status: code-review --> blocked
     
  • Tim Van Steenburgh

    Both branches merged. Once new ForgeHg package hits pythontree (https://trac.sdot.me/trac/siteops/ticket/54029), bump ForgeHg version to 0.1.15 in requirements-sf.txt.

     
  • Tim Van Steenburgh

    • summary: Delete old scm logic --> Delete old scm logic - NEEDS MONGO CMD
     
  • Tim Van Steenburgh

    • status: blocked --> closed
     
  • Cory Johns

    Cory Johns - 2013-07-10
    • status: closed --> code-review
     
  • Cory Johns

    Cory Johns - 2013-07-10
    • status: code-review --> closed