View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0023647 | Open CASCADE | Website:Tracker | public | 2012-12-17 09:56 | 2014-08-05 14:13 |
| Reporter | Assigned To | bugmaster | |||
| Priority | normal | Severity | feature | ||
| Status | closed | Resolution | fixed | ||
| Summary | 0023647: Provide automatic log of Git integrations in Mantis | ||||
| Description | It would be instrumental to have automatic log of integrations made in Git in connection with some issue, as notes added to this issue. This would facilitate work of developers (not requiring them to record pushed branches in Mantis manually), and ensure consistency of Mantis information with actual repository state. This should be triggered by Git push action on the official OCCT repository. The relevant Mantis issue should be identified by the name of the branch being updated (CRxxx, where xxx is ID of the issue). Four situations need to be distinguished: - pushing a new branch: "Branch CRxxx added" - updating existing branch: "Branch CRxxx updated" - forced update of existing branch: "New version of branch CRxxx pushed" - deletion of the branch: "Branch CRxxx deleted" The note should include also identification of the user who made a push (preferably set as author of the note), and commit hash of the branch after push (or before deletion). No references to GitWeb are needed. | ||||
| Additional information and documentation updates | This functionality can be combined with automation of update of Mantis issues when master is pushed (which is now performed manually through Mantis interface). | ||||
| Tags | No tags attached. | ||||
| Test case number | |||||
| related to | 0025041 | new | Open CASCADE | Automation of update of Mantis issues when master is pushed |
|
|
Resolved, please review. Four situations are distinguished for branches: - created - updating - updated forcibly - deleted Short information about the changes is also published in bugnotes (except "forced update" as it can lead to getting huge lists of "new" commits, actually had only new hashes) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2012-12-17 09:56 |
|
New Issue | |
| 2012-12-17 09:56 |
|
Assigned To | => aiv |
| 2012-12-29 12:41 |
|
Status | new => assigned |
| 2014-07-01 09:00 |
|
Relationship added | related to 0025041 |
| 2014-08-01 20:04 |
|
Note Added: 0030542 | |
| 2014-08-01 20:04 |
|
Assigned To | aiv => bugmaster |
| 2014-08-01 20:04 |
|
Status | assigned => resolved |
| 2014-08-05 14:13 | bugmaster | Status | resolved => closed |
| 2014-08-05 14:13 | bugmaster | Resolution | open => fixed |
