#7866 Run can_merge in background, and cache results

v1.3.0
closed
General
2015-08-20
2015-03-31
No

We do need to run merge requests as a background task, and cache the results. Mature projects with big repos take too long to compute if they are mergable.

See https://forge-allura.apache.org/p/allura/tickets/7830/#f5b2 for discussion on running in background and caching.

Discussion

  • Dave Brondsema

    Dave Brondsema - 2015-04-07
    • labels: merge-requests --> merge-requests, sf-current
     
  • Igor Bondarenko - 2015-04-08
    • Owner: Anonymous --> Igor Bondarenko
    • Labels: merge-requests, sf-current --> merge-requests, 42cc, sf-current
    • Status: open --> in-progress
     
  • Igor Bondarenko - 2015-04-08
    • labels: merge-requests, 42cc, sf-current --> merge-requests, 42cc, sf-current, sf-2
     
  • Igor Bondarenko - 2015-04-20
    • status: in-progress --> review
     
  • Igor Bondarenko - 2015-04-20

    Closed #754. ib/7866

     
  • Dave Brondsema

    Dave Brondsema - 2015-04-20
    • status: review --> in-progress
    • Reviewer: Dave Brondsema
     
  • Dave Brondsema

    Dave Brondsema - 2015-04-20

    If merging is not allowed (merge_allowed method), e.g. disabled with scm.merge.git.disabled = true then none of this should run. When I had it disabled, and was logged in as a project admin and visited a MR it showed the "checking" message and ran the task and then was hidden after that.

     
  • Igor Bondarenko - 2015-04-21
    • status: in-progress --> review
     
  • Igor Bondarenko - 2015-04-21

    Closed #758. Force-pushed ib/7866 (rebase)

     
  • Dave Brondsema

    Dave Brondsema - 2015-04-21
    • status: review --> closed
     
  • Dave Brondsema

    Dave Brondsema - 2015-04-30
    • labels: merge-requests, 42cc, sf-current, sf-2 --> merge-requests, 42cc, sf-2
     
  • Igor Bondarenko - 2015-06-18
    • Milestone: unreleased --> asf_release_1.3.0
     

Log in to post a comment.