forked from taskcluster/taskcluster
-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yml
156 lines (128 loc) · 6.01 KB
/
config.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
defaults:
app:
exchangePrefix: v1/
# Number of seconds before the claim to a run expires, defaulting to 1200
claimTimeout: !env:number:optional TASK_CLAIM_TIMEOUT
# S3 buckets where artifacts are stored
publicArtifactBucket: !env PUBLIC_ARTIFACT_BUCKET
privateArtifactBucket: !env PRIVATE_ARTIFACT_BUCKET
signPublicArtifactUrls: !env:bool:optional SIGN_PUBLIC_ARTIFACT_URLS
# Time delay before expiring artifacts, in readable format, see:
# taskcluster.fromNow, notice this should be negative!
artifactExpirationDelay: '- 30 minutes'
# Time delay before expiring tasks, in readable format, see:
# taskcluster.fromNow, notice this should be negative!
taskExpirationDelay: '- 30 minutes'
# Time delay before expiring worker info; notice this should be negative!
workerInfoExpirationDelay: '- 30 minutes'
# update `expires`, `last_date_active` values in postgres at this frequency;
# larger values give less accurate expires times, but reduce database traffic.
# In readable format, see: taskcluster.fromNow. Defaulting to 30 minutes
workerInfoUpdateFrequency: !env:optional WORKER_INFO_UPDATE_FREQUENCY
# Time extension of the expires property for task-group definitions.
# This is entities holding the schedulerId for a task-group, hence, we
# expire them later to avoid people creating tasks with a different
# schedulerId inside a task-group where all tasks are about to expire.
taskGroupExpiresExtension: 6220800 # 3 days as seconds
# Prefix for azure queues (at most 6 characters)
queuePrefix: queue
# Name of azure queue for tracking claim expiration
claimQueue: claim-queue
# Name of azure queue for tracking deadlines
deadlineQueue: deadline-queue
# Name of azure queue for tracking resolved tasks (dependency tracker)
resolvedQueue: resolved-queue
# Number of ms before deadline expiration message arrives, past deadline
deadlineDelay: 60000
# Configuration for deadline-resolver
deadlineResolver:
# Number of ms to sleep after polling from an empty queue
pollingDelay: 5000
# Number of event loops to run in parallel, each taking up to 32 message
# in parallel. Hence, 4 implies 4 * 32 = 128 messages in parallel
parallelism: 1
# Configuration for claim-resolver
claimResolver:
# Number of ms to sleep after polling from an empty queue
pollingDelay: 5000
# Number of event loops to run in parallel, each taking up to 32 message
# in parallel. Hence, 4 implies 4 * 32 = 128 messages in parallel
parallelism: 1
# Configuration for dependency-resolver
dependencyResolver:
# Number of ms to sleep after polling from an empty queue
pollingDelay: 5000
# CDN for public artifact bucket
publicArtifactBucketCDN: !env:optional PUBLIC_ARTIFACT_BUCKET_CDN
taskCacheMaxSize: !env:number:optional TASK_CACHE_MAX_SIZE
# How many artifacts to remove at once when bulk deletion is disabled
expireArtifactsBatchSize: !env:number:optional EXPIRE_ARTIFACTS_BATCH_SIZE
taskcluster:
rootUrl: !env TASKCLUSTER_ROOT_URL
credentials:
clientId: !env TASKCLUSTER_CLIENT_ID
accessToken: !env TASKCLUSTER_ACCESS_TOKEN
monitoring:
level: !env:optional LEVEL
errorConfig: !env:json:optional ERROR_CONFIG
server:
port: !env:number PORT
env: !env NODE_ENV
forceSSL: !env:bool FORCE_SSL
trustProxy: true
# Azure credentials (for blob and queue storage)
postgres:
readDbUrl: !env READ_DB_URL
writeDbUrl: !env WRITE_DB_URL
pulse:
username: !env PULSE_USERNAME
password: !env PULSE_PASSWORD
hostname: !env PULSE_HOSTNAME
vhost: !env PULSE_VHOST
amqps: !env:bool:optional PULSE_AMQPS
aws:
# Credentials with access to artifact buckets and
# references/schemas.taskcluster.net if you wish to publish meta-data
accessKeyId: !env AWS_ACCESS_KEY_ID
secretAccessKey: !env AWS_SECRET_ACCESS_KEY
region: !env ARTIFACT_REGION
endpoint: !env:optional AWS_ENDPOINT
s3ForcePathStyle: !env:bool:optional AWS_FORCE_PATH_STYLE
apiVersion: 2014-01-01
skipCorsConfiguration: !env:bool:optional AWS_SKIP_CORS_CONFIGURATION
useBulkDelete: !env:bool:optional AWS_USE_BULK_DELETE
# new relic config (processed in services/prelude.js)
newRelic: !env:json:optional NEW_RELIC
# Configuration of tests
test:
taskcluster:
rootUrl: "https://tc.example.com"
app:
# For testing purposes we let claims expire very fast
claimTimeout: 1
queuePrefix: 'hacks3'
queuePrefix2: 'hacks4' # For testing deletion of queues
claimQueue: 'test-claim-queue'
deadlineQueue: 'test-deadline-queue'
deadlineDelay: 1000
# Positive, means we expire artifacts 4 days ahead of time, useful for
# testing. In production this should be "- x hours" or so...
artifactExpirationDelay: '4 days'
# Positive, means that expire tasks 4 days ahead of time, useful for
# testing. In production this should be "- x hours" or so...
taskExpirationDelay: '4 days'
taskGroupExpiresExtension: 0 # should always be positive in production
deadlineResolver:
pollingDelay: 250
parallelism: 1
claimResolver:
pollingDelay: 250
parallelism: 1
dependencyResolver:
pollingDelay: 250
taskCacheMaxSize: 10
server:
port: 60401
env: development
forceSSL: false
trustProxy: false