{"action":"closed","issue":{"url":"https://api.github.com/repos/deis/jenkins-jobs/issues/192","repository_url":"https://api.github.com/repos/deis/jenkins-jobs","labels_url":"https://api.github.com/repos/deis/jenkins-jobs/issues/192/labels{/name}","comments_url":"https://api.github.com/repos/deis/jenkins-jobs/issues/192/comments","events_url":"https://api.github.com/repos/deis/jenkins-jobs/issues/192/events","html_url":"https://github.com/deis/jenkins-jobs/issues/192","id":169458491,"number":192,"title":"switch over to slack emails","user":{"login":"vdice","id":9322017,"avatar_url":"https://avatars.githubusercontent.com/u/9322017?v=3","gravatar_id":"","url":"https://api.github.com/users/vdice","html_url":"https://github.com/vdice","followers_url":"https://api.github.com/users/vdice/followers","following_url":"https://api.github.com/users/vdice/following{/other_user}","gists_url":"https://api.github.com/users/vdice/gists{/gist_id}","starred_url":"https://api.github.com/users/vdice/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vdice/subscriptions","organizations_url":"https://api.github.com/users/vdice/orgs","repos_url":"https://api.github.com/users/vdice/repos","events_url":"https://api.github.com/users/vdice/events{/privacy}","received_events_url":"https://api.github.com/users/vdice/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/deis/jenkins-jobs/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/deis/jenkins-jobs/labels/proposal","name":"proposal","color":"0052cc"}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-08-04T19:49:46Z","updated_at":"2016-08-19T18:21:13Z","closed_at":"2016-08-19T18:21:13Z","body":"We still don't have the ability to send slack notifications to appropriate channels for each Workflow component (or other) -- rather, they all have to go to the global default of `#testing` b/c that's where the credentials live.  (When changing the channel in job DSL, it requires supplying the credential token again, which cannot be done via a credentials binding and so would otherwise be leaking the secret to source control.  The proposed plugin enhancement to this end https://github.com/jenkinsci/slack-plugin/pull/208 seems to have lost momentum.)\r\n\r\nAlso, we are encountering https://github.com/deis/jenkins-jobs/issues/153.\r\n\r\nTherefore, I propose we switch over to sending slack emails using the [extendedEmail]( https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.helpers.publisher.PublisherContext.extendedEmail) DSL.  This would allow us to send emails to the component-appropriate slack channel, assuming the slack email address for each channel exists in the form of Credentials Bindings.\r\n\r\nThis will greatly relieve the amount of noise currently in the `#testing` channel and get component-appropriate build statuses to the parties directly affected/interested."}}
{"actor":{"display_login":"vdice"}}