part of story #21368 create mirrored iteration How to test: Run `tuleap config-set feature_flag_program_management_display_iteration 1` to enable iterations Make sure your redis worker is running 1. Assuming you have already run tests for this story, you should have rows in the plugin_program_management_pending_iterations table. If not, see section 2 below. Trigger manually a redis message with the following steps: - Enter a bash shell on the redis container: $ docker exec -it tuleap_redis_1 bash - Enter the redis cli in interactive mode: # redis-cli - Push a message to the events list > LPUSH 'app_user_events' '{"event_name":"tuleap.program_management.iteration.creation","payload":{"artifact_id":6260,"user_id":110},"_enqueue_ts":1628157233.0802,"_queued_total":0}' Here, "artifact_id" must be the id of an Iteration with a matching row in the database table. "user_id" must be the id of your user and match the same row in the database table. "_enqueue_ts" represents the timestamp at which the message is pushed. You can get one here [0], make sure to select "$get_as_float" = true. - You should see a log message in /var/log/tuleap/program_management_syslog : [debug] Processing iteration creation with iteration #6260 for user #110 2. If you have no pre-existing rows in the database table, follow these steps: - 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 database table and push a message to redis (like above). 3. If you change the Iteration tracker in Program Management Administration and then trigger a message from redis, the corresponding database row will be deleted. Change-Id: Icbb95463123021e65eefcb63d5e44d391c70d875

+365 −38

Author

Joris MASSON (jmasson) 2021-08-10 09:37

Committer

Joris MASSON (jmasson) 2021-08-10 16:22

Hash 38e8815e6bbe8f2fcbbf8fd6a1c195b46ffe49b4

Parent af8ab906f528d297c0c1c1fa664eff4c4eff2c22

Reference git #tuleap/stable/38e8815e6bbe8f2fcbbf8fd6a1c195b46ffe49b4