switch from watching slackbots and creating multiple channels that then also watch activities
Opened this issue · 4 comments
Right now we list and watch slackbot resources and create a new channel for everyone, then start a new watch of pipeline activities for each. I wonder if instead we change this to use a shared index informer that watches pipeline activities and then have multiple workers, one for each slackbot that is configured? Architecturally this seems like a better fit, will likely be more performant and less overhead I would think.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten