You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: jekyll/_cci2/about-circleci.md
+7-8Lines changed: 7 additions & 8 deletions
Original file line number
Diff line number
Diff line change
@@ -11,11 +11,10 @@ This document provides a summary of continuous integration and how CircleCI enab
11
11
12
12
## CircleCI Overview
13
13
14
-
**CircleCI** - Our mission is to empower technology-driven organizations to do their best work.
15
-
We want to make engineering teams more productive through intelligent automation.
14
+
**CircleCI** - Our mission is to empower technology-driven organizations to do their best work. We want to make engineering teams more productive through intelligent automation.
16
15
17
-
CircleCI provides enterprise-class support and services, with the flexibility of a startup.
18
-
We work where you work: Linux, macOS, Android, and Windows - SaaS or behind your firewall.
16
+
CircleCI provides enterprise-class support and services, with the flexibility of a startup.
17
+
We work where you work: Linux, macOS, Android, and Windows - SaaS or behind your firewall.
19
18
20
19

21
20
@@ -31,7 +30,7 @@ As an operator or administrator of CircleCI installed on your own servers, Circl
31
30
32
31
After a software repository on GitHub or Bitbucket is authorized and added as a project to [circleci.com](https://circleci.com), every code change triggers automated tests in a clean container or VM. CircleCI runs each [job]({{site.baseurl}}/2.0/glossary/#job) in a separate [container]({{site.baseurl}}/2.0/glossary/#container) or VM. That is, each time your job runs CircleCI spins up a container or VM to run the job in.
33
32
34
-
CircleCI then sends an email notification of success or failure after the tests complete. CircleCI also includes integrated Slack and IRC notifications. Code test coverage results are available from the details page for any project for which a reporting library is added.
33
+
CircleCI then sends an email notification of success or failure after the tests complete. CircleCI also includes integrated [Slack and IRC notifications]( {{ site.baseurl }}/2.0/notifications). Code test coverage results are available from the details page for any project for which a reporting library is added.
35
34
36
35
CircleCI may be configured to deploy code to various environments, including AWS CodeDeploy, AWS EC2 Container Service (ECS), AWS S3, Google Kubernetes Engine (GKE), Microsoft Azure, and Heroku. Other cloud service deployments are easily scripted using SSH or by installing the API client of the service with your job configuration.
37
36
@@ -47,9 +46,9 @@ Every commit triggers an automated build and test.
47
46
If build and test fails, it’s repaired quickly - within minutes.
Copy file name to clipboardExpand all lines: jekyll/_cci2/notifications.md
+4Lines changed: 4 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,10 @@ workflows:
103
103
- build
104
104
```
105
105
106
+
To get started with enabling notifications in Slack *for a specific project*, head to the *Settings* page for your project. Click on *Slack Integration* in the sidebar and follow the steps to setup Slack.
It is also possible to use the Slack Orb to provide other types of notifications, including notifying a slack channel of a pending approval or sending a status alert at the end of a job based on success or failure. To view such usage examples, consult the [CircleCI Slack Orb page](https://circleci.com/orbs/registry/orb/circleci/slack).
0 commit comments