part of story #22675 replicate program increment changes to mirrored program increments How to test: Make sure your redis worker is running 1. - 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. - You should see a log message in /var/log/tuleap/program_management_syslog : [debug] Processing program increment update with program increment #6107 for user #110 2. If you delete a Program Increment and then trigger a message from redis, then the corresponding database row will be deleted and nothing will be logged (it will not be processed). How to trigger manually a message from redis: - Enter the redis-cli in the redis container: $ docker exec -it tuleap_redis_1 sh -c redis-cli - Push a message to the events list > LPUSH 'app_user_events' '{"event_name":"tuleap.program_management.program_increment.update","payload":{"artifact_id":6107,"user_id":110},"_enqueue_ts":1630314422.2812,"_queued_total":0}' Here, "artifact_id" must be the id of a Program Increment 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. [0] https://microtime.onlinephpfunctions.com/ Change-Id: Ib2ad536c9afda06b6710ee0d48e20d49369b783a

+812 −55

Author

Joris MASSON (jmasson) 2021-08-30 14:38

Committer

Joris MASSON (jmasson) 2021-09-02 11:49

Hash e9c54138427305faea95d11f403219caeba3588e

Parent e96038867dc83ca198025fe0360d2c897c2902ba

Reference git #tuleap/stable/e9c54138427305faea95d11f403219caeba3588e