Bugzilla

I tried testing out the community pulse ingestion earlier today on prototype with SimonSapin however, we weren't able to get it working. I had pushed his branch with the servo tc_root_url changes upstream as `servo-root-url` branch (I've confirmed the changes to the root url were applied to the repository table). 

I didn't see any errors per say - looking in paper trail* - it just wasn't showing up in the Treeherder-prototype UI. I kept the taskcluster.net credentials, but added another object to each of PULSE_PUSH_SOURCES and PULSE_TASK_SOURCES for community-tc. However, I've just realized I made one mistake with the push source updates, where I put `hgmo:true` - that's been changed to false per Dustin's example above. 

*There was a lot of noise from worker_store_pulse_data for prototype: 'Could not determine Treeherder route. Either there is no route, or more than one matching route exists.Task ID: <id>' but those were in the logs before I had made these changes to prototype. I also didn't find anything of use with the pulse_listener worker.

Armen and Cam probably have more knowledge and insight into pulse ingestion than I do, so if either one of you would like to jump in and try this again with Simon in the morning please feel free. Otherwise I'll continue working on it with Simon.

Note: I have a WIP branch called `taskcluster-rooturl-changes` that includes changes to repositories.json and a few other changes where taskcluster.net is used. There might still need to be additional backend code changes but for any other changes that are needed to get this working, we'll want to add to that branch so feel free to add commits if you need to.

Dustin, is there a way to see whether a task was processed by the pulse queue/exchange? This is one Simon created for testing: https://community-tc.services.mozilla.com/tasks/NSkZtsUQR-iS9Kui_4Mt1A

I tried testing out the community pulse ingestion earlier today on prototype with SimonSapin however, we weren't able to get it working. I had pushed his branch with the servo tc_root_url changes upstream as `servo-root-url` branch (I've confirmed the changes to the root url were applied to the repository table). 

I didn't see any errors per say - looking in paper trail* - it just wasn't showing up in the Treeherder-prototype UI. I kept the taskcluster.net credentials, but added another object to each of PULSE_PUSH_SOURCES and PULSE_TASK_SOURCES for community-tc. However, I've just realized I made one mistake with the push source updates, where I put `hgmo:true` , not sure if that would've made a difference. 

*There was a lot of noise from worker_store_pulse_data for prototype: 'Could not determine Treeherder route. Either there is no route, or more than one matching route exists.Task ID: <id>' but those were in the logs before I had made these changes to prototype. I also didn't find anything of use with the pulse_listener worker.

Armen and Cam probably have more knowledge and insight into pulse ingestion than I do, so if either one of you would like to jump in and try this again with Simon in the morning please feel free. Otherwise I'll continue working on it with Simon.

Note: I have a WIP branch called `taskcluster-rooturl-changes` that includes changes to repositories.json and a few other changes where taskcluster.net is used. There might still need to be additional backend code changes but for any other changes that are needed to get this working, we'll want to add to that branch so feel free to add commits if you need to.

Dustin, is there a way to see whether a task was processed by the pulse queue/exchange? This is one Simon created for testing: https://community-tc.services.mozilla.com/tasks/NSkZtsUQR-iS9Kui_4Mt1A

Edit: I've removed those credentials from the Heroku configs and reset the branch back to master.

I tried testing out the community pulse ingestion earlier today on prototype with SimonSapin however, we weren't able to get it working. I had pushed his branch with the servo tc_root_url changes upstream as `servo-root-url` branch (I've confirmed the changes to the root url were applied to the repository table). 

I didn't see any errors per say - looking in paper trail* - it just wasn't showing up in the Treeherder-prototype UI. I kept the taskcluster.net credentials, but added another object to each of PULSE_PUSH_SOURCES and PULSE_TASK_SOURCES for community-tc. However, I've just realized I made one mistake with the push source updates, where I put `hgmo:true` , not sure if that would've made a difference. 

*There was a lot of noise from worker_store_pulse_data for prototype: 'Could not determine Treeherder route. Either there is no route, or more than one matching route exists.Task ID: <id>' but those were in the logs before I had made these changes to prototype. I also didn't find anything of use with the pulse_listener worker.

Armen and Cam probably have more knowledge and insight into pulse ingestion than I do, so if either one of you would like to jump in and try this again with Simon in the morning please feel free. Otherwise I'll continue working on it with Simon.

Note: I have a WIP branch called `taskcluster-rooturl-changes` that includes changes to repositories.json and a few other changes where taskcluster.net is used. There might still need to be additional backend code changes but for any other changes that are needed to get this working, we'll want to add to that branch so feel free to add commits if you need to.

Dustin, is there a way to see whether a task was processed by the pulse queue/exchange? This is one Simon created for testing: https://community-tc.services.mozilla.com/tasks/NSkZtsUQR-iS9Kui_4Mt1A

Edit: I've removed those credentials from the Heroku configs and reset the branch to master. Armen has said he'll take a stab at this in the morning.