33
edits
Taskcluster/Round Tuit Box: Difference between revisions
Jump to navigation
Jump to search
Proposed mock pulse listener/publisher
No edit summary |
(Proposed mock pulse listener/publisher) Tag: Mobile edit |
||
| Line 55: | Line 55: | ||
We should provide some support for building a similar system for other projects. That should be some basic building blocks on which those projects can build, since their needs will be different from Gecko. For example, perhaps a Github repo with some basic decision-task code, and a docker image that can run it. Then projects can fork that repo and get some tasks running quickly, then modify it to suit their needs. | We should provide some support for building a similar system for other projects. That should be some basic building blocks on which those projects can build, since their needs will be different from Gecko. For example, perhaps a Github repo with some basic decision-task code, and a docker image that can run it. Then projects can fork that repo and get some tasks running quickly, then modify it to suit their needs. | ||
== Mock Pulse Listener/Publisher == | |||
In taskcluster services we publish a lot of events to a RabbitMQ server called pulse. We do this so that anyone can hook into the event stream and feed of CI events. This is a powerful and important feature, hence, we test that messages are sent during our integration tests. However, this means that in order to run tests you must have pulse credentials. This isn't a huge issue as these can be made for anyone. But it limits our ability to test PRs from untrusted repositories and makes running tests harder. Hence, it would be cool to make a mock-mode for our PulseListener and publisher. Then we can run tests without pulse credentials for PRs and with credentials for pushes, as an integration step after merging. This is also an opportunity to clean up some of older parts of the code base to improve overall stability. | |||
= Guidelines = | = Guidelines = | ||