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: _data/snippets.yml
+37-19
Original file line number
Diff line number
Diff line change
@@ -18,38 +18,38 @@ before_and_after: |
18
18
```
19
19
ghlimit: |
20
20
> If your API or cron triggered builds run on the *same commit
21
-
> or branch* over and over again, you will notice GitHub have a limit of
21
+
> or branch* over and over again, you will notice GitHub has a limit of
22
22
> [1000 status updates](https://developer.github.com/v3/repos/statuses/#create-a-status)
23
-
> *per commit*, which causes the Travis CI build status displayed on GitHub
24
-
> to be incorrect.
23
+
> *per commit*, which causes the Travis CI build status to display incorrectly
24
+
> on GitHub.
25
25
> Avoid this problem by specifying a regularly updated branch for your automated builds.
26
26
all_note: |
27
-
> Language versions and other build-environment specific
28
-
> information are in our reference pages:
27
+
> For Language versions and other build-environment specific
28
+
> information visit our reference pages:
29
29
> * [Precise](/user/reference/precise/)
30
30
> * [Trusty](/user/reference/trusty/)
31
31
> * [Xenial](/user/reference/xenial/)
32
32
> * [Bionic](/user/reference/bionic/)
33
33
> * [macOS](/user/reference/osx/)
34
34
> * [Windows](/user/reference/windows/)
35
35
unix_note: |
36
-
> Language versions and other build-environment specific
37
-
> information are in our reference pages:
36
+
> For Language versions and other build-environment specific
37
+
> information visit our reference pages:
38
38
> * [Precise](/user/reference/precise/)
39
39
> * [Trusty](/user/reference/trusty/)
40
40
> * [Xenial](/user/reference/xenial/)
41
41
> * [Bionic](/user/reference/bionic/)
42
42
> * [macOS](/user/reference/osx/)
43
43
linux_note: |
44
-
> Language versions and other build-environment specific
45
-
> information are in our reference pages:
44
+
> For Language versions and other build-environment specific
45
+
> information visit our reference pages:
46
46
> * [Precise](/user/reference/precise/)
47
47
> * [Trusty](/user/reference/trusty/)
48
48
> * [Xenial](/user/reference/xenial/)
49
49
> * [Bionic](/user/reference/bionic/)
50
50
linux_windows_note: |
51
-
> Language versions and other build-environment specific
52
-
> information are in our reference pages:
51
+
> For Language versions and other build-environment specific
52
+
> information visit our reference pages:
53
53
> * [Precise](/user/reference/precise/)
54
54
> * [Trusty](/user/reference/trusty/)
55
55
> * [Xenial](/user/reference/xenial/)
@@ -79,20 +79,38 @@ contact_enterprise_support: |
79
79
80
80
- Description of the problem - what are you observing?
81
81
- Which steps did you try already?
82
-
- A support bundle (You can get it from `https://<your-travis-ci-enterprise-domain>:8800/support`)
82
+
- A support bundle (see table below on how to obtain it)
83
83
- Log files from all workers (They can be found at `/var/log/upstart/travis-worker.log` - please include as many as you can retrieve).
84
84
- If a build failed or errored, a text file of the build log
85
-
85
+
86
+
| TCI Enterprise version | Support bundle |
87
+
| :--- | :--- |
88
+
| **3.x** | Run `kubectl kots admin-console -n [namespace]` to access admin console on `http://localhost:8800`<br />Support bundle generation instruction is available in ‘troubleshoot’ menu or directly at: `http://localhost:8800/app/tci-enterprise-kots/troubleshoot`<br /><br />A command for generating support bundle will appear after selecting: <br />`If you'd prefer, [click here]() to get a command to manually generate a support bundle.` |
89
+
| **2.x+** | You can get it from `https://<your-travis-ci-enterprise-domain>:8800/support` |
90
+
86
91
Have you made any customizations to your setup? While we may be able to see some
87
92
information (such as hostname, IaaS provider, and license expiration), there
88
-
are many other things we can't see which could lead to something not working.
89
-
Therefore, we'd like to ask you to also answer the questions below in your
93
+
are many other things we cannot see which could lead to something not working.
94
+
Therefore, we would like to ask you to also answer the questions below in your
90
95
support request (if applicable):
91
96
92
-
- How many machines are you using?
97
+
- How many machines are you using / what is your Kubernetes cluster setup?
93
98
- Do you use configuration management tools (Chef, Puppet)?
94
99
- Which other services do interface with Travis CI Enterprise?
95
-
- Do you use Travis CI Enterprise together with github.com or GitHub Enterprise?
96
-
- If you're using GitHub Enterprise, which version of it?
100
+
- Which Version Control system (VCS) do you use together with Travis CI Enterprise (e.g. github.com, GitHub Enterprise, or BitBucket Cloud)?
101
+
- If you are using GitHub Enterprise, which version of it?
97
102
98
-
We're looking forward to helping!
103
+
We are looking forward to helping!
104
+
enterprise_2_encryption_key_backup: |
105
+
To make a backup of encryption keys in TCIE 2.x, please follow these steps:
106
+
107
+
1. Open an SSH connection to the platform machine.
108
+
2. Open a bash session with `root` privileges on the Travis CI container by running `travis bash`.
109
+
3. Run the following command to obtain the key: `grep -A1 encryption: /usr/local/travis/etc/travis/config/travis.yml`.
110
+
4. Create a backup of the value returned by the previous command by either writing it down on a piece of paper or storing it on a different computer.
111
+
enterprise_3_encryption_key_backup: |
112
+
To make a backup of encryption keys in TCIE 3.x, please follow these steps:
113
+
114
+
1. Make sure you have appropriate access to the kubernetes cluster: you need credentials for `kubectl` and connection to [travis-api-pod]
115
+
2. Run `kubectl exec -it [travis-api-pod] cat /app/config/travis.yml |grep -A 2 encryption` (using Travis API pod is recommended).
116
+
3. Create a backup of the value returned by that command by either writing it down on a piece of paper or storing it on a different computer.
0 commit comments