#4820 Create event when new commits are processed

v1.0.0
closed
nobody
migration (63) 42cc (432)
General
Cory Johns
2015-08-20
2012-08-29
Dave Brondsema
No

Fire an event whenever a new set of commits is processed by our repo refresh code. Use the existing post_event/event_handler functionality.

Is there a way to pass data in events? We should include the # of commits, perhaps not all the details though since that could be huge on an import. Eventually we need a flag to denote whether the commits are new or were reprocessed.

Use-case for this is to have separate code (not in Allura) define an event handler for commits, and update an external database timestamp whenever a project's repo has been updated.

Related

Tickets: #4820

Discussion

  • Dave Brondsema

    Dave Brondsema - 2012-09-21
    • milestone: forge-backlog --> forge-oct-05
     

  • Dave Brondsema

    Dave Brondsema - 2012-09-26
    • labels: migration --> migration, 42cc
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,3 +1,5 @@
-Fire an event whenever a new set of commits is processed by our repo refresh code.
+Fire an event whenever a new set of commits is processed by our repo refresh code.  Use the existing `post_event`/`event_handler` functionality.

 Is there a way to pass data in events?  We should include the # of commits, perhaps not all the details though since that could be huge on an import.  Eventually we need a flag to denote whether the commits are new or were reprocessed.
+
+Use-case for this is to have separate code (not in Allura) define an event handler for commits, and update an external database timestamp whenever a project's repo has been updated.
    • milestone: forge-oct-19 --> forge-backlog
     

  • Igor Bondarenko - 2012-09-27

    Created #180: [#4820] Create event when new commits are processed (2cp)

     

    Related

    Tickets: #4820

  • Igor Bondarenko - 2012-09-27
    • status: open --> in-progress
     

  • Igor Bondarenko - 2012-10-02

    Closed #180. Branch 42cc_4820.

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

  • Dave Brondsema

    Dave Brondsema - 2012-10-05
    • qa: Cory Johns
     

  • Cory Johns - 2012-10-10
    • status: code-review --> closed
    • milestone: forge-backlog --> forge-oct-19
     

  • Dave Brondsema

    Dave Brondsema - 2012-10-19
    • size: 2 --> 0
     

Log in to post a comment.