slack

在大家纷纷谈起 DevOps 和 ChatOps 的时候，Martin Giles 也对 ChatOps 的前景有自己的看法。他曾是《经济学人》的记者，现在是 Wing Venture Capital （@Wing_VC）合伙人。本文系国内 ITOM 管理平台 OneAPM 翻译自 Martin Giles 于 2015 年 12 月撰写的文章 Atlassian, Slack, and the promise of ChatOps 。 企业 IT 的消费化正在迈入激动人心的新阶段。员工们厌倦了老掉牙的办公技术，智能手机和平板电脑因而得以引入，而智能手机和平板电脑的传播又加速了将消费者导向的技术引入工作场所的进程。我们也见证了 Salesforce 的 Chatter 及 Microsoft 的 Yammer 等应用的兴起，它们是模仿 Facebook 等社交媒体平台的佳作。这一大趋势的最新进展是企业传讯应用的兴起，而这些应用均受到 WhatsApp、Facebook Messenger 等非常成功的消费产品的启发。 Slack 和 HipChat 等业务在企业界的迅速传播，是此类服务提供商能够吸引投资者高估值的原因所在。日前， Atlassian （HipChat 的创造者） 正在准备上市 ，并在本周将其IPO的股价区间设定为每股 16.50 美元至 18.50 美元

Is a Slack channel / group / im / mpim id unique across different teams? In other words, can two teams have channels with the same id? I read the docs, searched on Google and here on SO, but could not get confirmation if channel IDs are unique or not. Slack plans to clarify this in documentation soon. While in the present day you'd probably get by just fine assuming IDs are unique across different teams, we strongly recommend scoping all of your storage and retrieval by team ID. Essentially, we recommend considering IDs as only unique within teams, regardless of if experientially they are

How can I configure Airflow so that any failure in the DAG will (immediately) result in a slack message? At this moment I manage it by creating a slack_failed_task: slack_failed_task = SlackAPIPostOperator( task_id='slack_failed', channel="#datalabs", trigger_rule='one_failed', token="...", text = ':red_circle: DAG Failed', icon_url = 'http://airbnb.io/img/projects/airflow3.png', dag=dag) And set this task (one_failed) upstream from each other task in the DAG: slack_failed_task << download_task_a slack_failed_task << download_task_b slack_failed_task << process_task_c slack_failed_task <<

I have a pipeline groovy script in Jenkins v2.19. Also I have a "Slack Notification Plugin" v2.0.1 and "Groovy Postbuild Plugin". I have successfully send a message "build started" and "build finished" (if it had). When some build step failed – how I can send a message "Build failed" to the Slack channel? You could do something like this and use a try catch block. Here is some example Code: node { try { notifyBuild('STARTED') stage('Prepare code') { echo 'do checkout stuff' } stage('Testing') { echo 'Testing' echo 'Testing - publish coverage results' } stage('Staging') { echo 'Deploy Stage' }

I've just created an app (slash command) and install it in one of my workspaces. But now I want to add the same app to another one. Is it possible without distribution to App Directory? If you want to add you Slack app to another workspace, you can do so without going through the process of placing it on the App directory. All you need to do is add the ability to install your app to an workspace using OAuth 2.0. enable public distribution So instead of clicking "Install app to this workspace", which works great for private Slack app, which live in one workspace only, you need a script than can

I want to develop a feature such a way that user can select multiple options from message menu. Is it possible to select multiple options from the interactive menu at the same time ?? You can currently only select one option. Slack does not support choosing more than one option in a message. But there are 2 alternatives: Dialogs Dialogs are modal and allow you to use up to 10 elements each including select menus. And they have a "submit" and "cancel" button. This allows you to implement exactly what you are asking, but your selects would be shown in a separate Dialog window and not directly as

I need to post multiple bot replies (responses determined dynamically) to the same channel. The obvious way seems to be to do an HTTP POST for each message in succession using this API method: https://api.slack.com/methods/chat.postMessage Is there a way to send messages to Slack in bulk to post to the same channel? The order in which the messages get rendered need not be important for me. No, there is no bulk variant. So you basically need to build your own bulk message sender. Keep in mind that there is a request limit of 1 message per second or your API requests will fail. There also is a 3