part of story #22675 replicate program increment changes to mirrored program increments How to test: make sure your redis worker is running - Edit an existing Program Increment artifact. You can change anything. - a new row will be created in the `plugin_program_management_pending_program_increment_update` database table. It will have the program increment's artifact id, your user id and the changeset id. No functional change expected when creating mirror iterations: - Run `tuleap config-set feature_flag_program_management_display_iteration 1` to enable iterations. - Edit a Program Increment artifact and add one or more artifact links with _is_child type to Iteration artifacts. For each iteration, Tuleap will write a new row in the `plugin_program_management_pending_iterations` database table. - a log message will be added to "program_management_syslog" for each iteration. - Only links to Iterations that have never been linked in previous changesets of the Program Increment are considered. If you edit the PI again, the iterations are not processed again. Notes: We need a single message because the update of program increment mirrors and the creation of iteration mirrors will both modify the source program increment (its artifact links). If we let them happen in parallel (with multiple redis messages), we will lose information due to the way Tracker changeset are designed. Change-Id: I92e84fc8821fa06918e7aff682692c888dcc73a5

+553 −447

Author

Joris MASSON (jmasson) 2021-08-27 17:30

Committer

Joris MASSON (jmasson) 2021-08-31 11:49

Hash f91520d01a87c458e860b20f80bc1f48692cb4ee

Parent 99870f30a47ef95600167499482defbc630a5809

Reference git #tuleap/stable/f91520d01a87c458e860b20f80bc1f48692cb4ee