| Title | Can't stop replication of an issue |
| Status | suspended |
| Priority | essential |
| Assigned user | Nick Barnes |
| Organization | Ravenbrook |
| Description | Once an issue passes replicate_p, it is replicated indefinitely afterwards. A user has requested a mechanism for halting replication of a given issue. Their advanced-config jobspec is quite restrictive and will not support replication of some issues. If an issue is mistakenly put into a state which passes replicate_p, and then taken out again, the replicator fails on every subsequent poll. |
| Analysis | To halt replication of an issue, the link between the job and the issue must be broken. The P4DTI-issue-id field of the job should be set to 'None', and the matching link from the defect tracker should also be cleared (e.g. in Bugzilla the matching row should be deleted from the p4dti_bug table, and any matching rows should be deleted from the p4dti_fixes and p4dti_filespecs tables). This could be done by hand but it may be better to provide a script. Note that this may cause conflicts with P4DTI requirement 1 < http://www.ravenbrook.com/project/p4dti/req/#req-1> . It may therefore be best to also mark the job as no longer replicated. It seems unlikely that the right thing is to delete the job, but maybe the script could produce a message suggesting this. |
| How found | customer |
| Evidence | <http://info.ravenbrook.com/mail/2001/07/04/19-53-09/0.txt> |
| Observed in | 1.1.1 |
| Introduced in | 1.0.0 |
| Created by | Nick Barnes |
| Created on | 2001-07-05 11:21:10 |
| Last modified by | Nick Barnes |
| Last modified on | 2018-07-05 17:27:39 |
| History | 2001-07-05 NB Created. 2018-07-05 NB Suspended because the P4DTI is obsolete. |