Installation reference
On This Page
マニフェストの例:
以下は、CircleCI Server helm のスピンアップに必要な基本的なパラメーターを含むマニフェストの例です。
AWS
以下は、AWS 環境への CircleCI Server のインストールに必要なパラメーターを含むマニフェスト例です。 このインストールではサービスアカウント (IRSA) の IAM ロールを使用しており、それを推奨しています。 base64 エンコードを含むフィールドはそのようにマークされています。
global:
domainName: "<full-domain-name-of-your-install>"
license: '<license>'
apiToken: "<circleci-api-token>"
sessionCookieKey: "<session-cookie-key>"
keyset:
signing: '<generated-signing-key>'
encryption: '<generated-encryption-key>'
nomad:
server:
gossip:
encryption:
key: "<nomad-gossip-encryption-key>"
rpc:
mTLS:
enabled: true
CACertificate: "<nomad-mtls-base64-ca>"
certificate: "<nomad-mtls-base64-cert>"
privateKey: "<nomad-mtls-base64-key>"
object_storage:
bucketName: '<s3-bucket-name>'
s3:
enabled: true
endpoint: "<aws-region-url>" # ex: https://s3.us-east-1.amazonaws.com
region: "<aws-region>"
irsaRole: "<arn-of-irsa-role>"
github:
clientId: "<generated-github-client-id>"
clientSecret: "<generated-github-client-secret>"
vm_service:
providers:
ec2:
enabled: true
region: "<aws-region>"
subnets:
- "<subnet-id>"
securityGroupId: "<security-group-id>"
irsaRole: "<arn-of-irsa-role>"
mongodb:
auth:
rootPassword: "<mongodb-root-password>"
password: "<mongodb-password>"
postgresql:
auth:
postgresPassword: "<postgres-password>"
pusher:
secret: "<pusher-secret>"
rabbitmq:
auth:
password: "<rabbitmq-password>"
erlangCookie: "<rabbitmq-erlang-cookie>"
GCP
以下は、GCP 環境への CircleCI Server のインストールに必要なパラメーターを含むマニフェスト例です。 このインストールでは Workload Identity を使用しており、それを推奨しています。 base64 エンコードを含むフィールドはそのようにマークされています。
global:
domainName: "<full-domain-name-of-your-install>"
license: '<license-for-circleci-server>'
apiToken: "<circleci-api-token>"
sessionCookieKey: "<session-cookie-key>"
keyset:
signing: '<generated-signing-key>'
encryption: '<generated-encryption-key>'
github:
clientId: "<generated-github-client-id>"
clientSecret: "<generated-github-client-secret>"
object_storage:
bucketName: "<gcs-bucket-name>"
gcs:
enabled: true
workloadIdentity: "<service-account-email-with-gcs-access>"
mongodb:
auth:
rootPassword: "<mongodb-root-password>"
password: "<mongodb-password>"
vm_service:
providers:
gcp:
enabled: true
project_id: <gcp-project-id>
network_tags:
- <network-tag>
zone: <gcp-zone>
network: "<gcp-network>"
subnetwork: "" # leave blank for auto-subnetting
workloadIdentity: "<service-account-email-with-compute-access>"
pusher:
secret: "<pusher-secret>"
postgresql:
auth:
postgresPassword: "<postgres-password>"
rabbitmq:
auth:
password: "<rabbitmq-password>"
erlangCookie: "<rabbitmq-erlang-cookie>"
nomad:
server:
gossip:
encryption:
key: "<nomad-gossip-encryption-key>"
rpc:
mTLS:
enabled: true
CACertificate: "<nomad-mtls-base64-ca>"
certificate: "<nomad-mtls-base64-cert>"
privateKey: "<nomad-mtls-base64-key>"
All Helm values.yaml
options
キー | タイプ | デフォルト値 | 説明 |
---|---|---|---|
apiToken | 文字列型 |
| API token (2 Options). Option 1: Set the value here and CircleCI will create the secret automatically. Option 2: Leave this blank, and create the secret yourself. CircleCI will assume it exists. |
api_service.replicas | 整数 |
| Number of replicas to deploy for the api-service deployment. |
audit_log_service.replicas | 整数 |
| Number of replicas to deploy for the audit-log-service deployment. |
branch_service.replicas | 整数 |
| Number of replicas to deploy for the branch-service deployment. |
builds_service.replicas | 整数 |
| Number of replicas to deploy for the builds-service deployment. |
contexts_service.replicas | 整数 |
| Number of replicas to deploy for the contexts-service deployment. |
cron_service.replicas | 整数 |
| Number of replicas to deploy for the cron-service deployment. |
dispatcher.replicas | 整数 |
| Number of replicas to deploy for the dispatcher deployment. |
distributor_cleaner.replicas | 整数 |
| Number of replicas to deploy for the distributor-dispatcher deployment. |
distributor_dispatcher.replicas | 整数 |
| Number of replicas to deploy for the distributor-dispatcher deployment. |
distributor_external.replicas | 整数 |
| Number of replicas to deploy for the distributor-external deployment. |
distributor_internal.replicas | 整数 |
| Number of replicas to deploy for the distributor-internal deployment. |
domain_service.replicas | 整数 |
| Number of replicas to deploy for the domain-service deployment. |
frontend.replicas | 整数 |
| Number of replicas to deploy for the frontend deployment. |
github | object | | VCS Configuration details (currently limited to GitHub Enterprise and GitHub) |
github.clientId | string |
| Client ID for OAuth Login via Github (2 Options). Option 1: Set the value here and CircleCI will create the secret automatically. Option 2: Leave this blank, and create the secret yourself. CircleCI will assume it exists. Create one by Navigating to Settings > Developer Settings > OAuth Apps. Your homepage should be set to |
github.clientSecret | string |
| Client Secret for OAuth Login via Github (2 Options). Option 1: Set the value here and CircleCI will create the secret automatically. Option 2: Leave this blank, and create the secret yourself. CircleCI will assume it exists. Retrieved from the same location as specified in github.clientID. |
github.enterprise | bool |
| Set to true for Github Enterprise and false for Github.com |
github.fingerprint | string |
| Required when it is not possible to directly ssh-keyscan a GitHub Enterprise instance. It is not possible to proxy |
github.hostname | string |
| Github hostname. Ignored on Github.com. This is the hostname of your Github Enterprise installation. |
github.scheme | string |
| One of 'http' or 'https'. Ignored on Github.com. Set to 'http' if your Github Enterprise installation is not using TLS. |
github.selfSignedCert | bool |
| set to 'true' If Github is using a self-signed certificate |
github.unsafeDisableWebhookSSLVerification | bool |
| Disable SSL Verification in webhooks. This is not safe and shouldn’t be done in a production scenario. This is required if your Github installation does not trust the certificate authority that signed your Circle server certificates (e.g they were self signed). |
global.container.org | string |
| The registry organization to pull all images from, defaults to circleci. |
global.container.registry | string |
| The registry to pull all images from, defaults to dockerhub. |
global.domainName | string |
| Domain name of your CircleCI install |
global.imagePullSecrets[0].name | string |
| |
global.license | string |
| License for your CircleCI install |
global.scheme | string |
| Scheme for your CircleCI install |
global.tracing.collector_host | string |
| |
global.tracing.enabled | bool |
| |
global.tracing.sample_rate | float |
| |
insights_service.dailyCronHour | 整数 |
| Defaults to 3AM local server time. |
insights_service.hourlyCronMinute | 整数 |
| Defaults to 35 minutes past the hour. |
insights_service.isEnabled | bool |
| Whether or not to enable the insights-service deployment. |
insights_service.replicas | 整数 |
| Number of replicas to deploy for the insights-service deployment. |
internal_zone | string |
| |
keyset | object |
| Keysets (2 Options) used to encrypt and sign artifacts generated by CircleCI. CircleCI Server の設定にはこれらの値が必要です。 Option 1: Set the values keyset.signing and keyset.encryption here and CircleCI will create the secret automatically. Option 2: Leave this blank, and create the secret yourself. CircleCI will assume it exists. The secret must be named 'signing-keys' and have the keys; signing-key, encryption-key. |
keyset.encryption | string |
| Encryption Key To generate an artifact ENCRYPTION key run: |
keyset.signing | string |
| Signing Key To generate an artifact SIGNING key run: |
kong.acme.email | 文字列型 |
| |
kong.acme.enabled | bool |
| This setting will fetch and renew Let’s Encrypt certs for you. It defaults to false as this only works when there’s a valid DNS entry for your domain (and the app. sub domain) - so you will need to deploy with this turned off and set the DNS records first. You can then set this to true and run helm upgrade with the updated setting if you want. |
kong.debug_level | 文字列型 |
| Debug level for Kong. Available levels: debug, info, warn, error, crit. Default is "notice". |
kong.replicas | 整数 |
| |
kong.resources.limits.cpu | 文字列型 |
| |
kong.resources.limits.memory | 文字列型 |
| |
kong.resources.requests.cpu | 文字列型 |
| |
kong.resources.requests.memory | 文字列型 |
| |
legacy_notifier.replicas | 整数 |
| Number of replicas to deploy for the legacy-notifier deployment. |
mongodb.architecture | 文字列型 |
| |
mongodb.auth.database | 文字列型 |
| |
mongodb.auth.existingSecret | 文字列型 |
| |
mongodb.auth.mechanism | 文字列型 |
| |
mongodb.auth.password | 文字列型 |
| |
mongodb.auth.rootPassword | 文字列型 |
| |
mongodb.auth.username | 文字列型 |
| |
mongodb.fullnameOverride | 文字列型 |
| |
mongodb.hosts | 文字列型 |
| MongoDB host. This can be a comma-separated list of multiple hosts for sharded instances. |
mongodb.image.tag | 文字列型 |
| |
mongodb.internal | bool |
| Set to false if you want to use an externalized MongoDB instance. |
mongodb.labels.app | 文字列型 |
| |
mongodb.labels.layer | 文字列型 |
| |
mongodb.options | 文字列型 |
| |
mongodb.persistence.size | 文字列型 |
| |
mongodb.podAnnotations."backup.velero.io/backup-volumes" | 文字列型 |
| |
mongodb.podLabels.app | 文字列型 |
| |
mongodb.podLabels.layer | 文字列型 |
| |
mongodb.ssl | bool |
| |
mongodb.tlsInsecure | bool |
| If using an SSL connection with custom CA or self-signed certs, set this to true |
mongodb.useStatefulSet | bool |
| |
nginx.annotations."service.beta.kubernetes.io/aws-load-balancer-cross-zone-load-balancing-enabled" | 文字列型 |
| |
nginx.annotations."service.beta.kubernetes.io/aws-load-balancer-type" | 文字列型 |
| Use "nlb" for Network Load Balancer and "clb" for Classic Load Balancer see https://aws.amazon.com/elasticloadbalancing/features/ for feature comparison |
nginx.aws_acm.enabled | bool |
| ⚠️ WARNING: Enabling this will recreate frontend’s service which will recreate the load balancer. If you are updating your deployed settings, then you will need to route your frontend domain to the new loadbalancer. You will also need to add |
nginx.loadBalancerIp | 文字列型 |
| Load Balancer IP To use a static IP for the provisioned load balancer with GCP, set to a reserved static ipv4 address |
nginx.private_load_balancers | bool |
| |
nginx.replicas | 整数 |
| |
nginx.resources.limits.cpu | 文字列型 |
| |
nginx.resources.limits.memory | 文字列型 |
| |
nginx.resources.requests.cpu | 文字列型 |
| |
nginx.resources.requests.memory | 文字列型 |
| |
nomad.auto_scaler.aws.accessKey | 文字列型 |
| AWS Authentication Config (3 Options). Option 1: Set accessKey and secretKey here, and CircleCI will create the secret for you. Option 2: Leave accessKey and secretKey blank, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave accessKey and secretKey blank, and set the irsaRole field (IAM roles for service accounts). |
nomad.auto_scaler.aws.autoScalingGroup | 文字列型 |
| |
nomad.auto_scaler.aws.enabled | bool |
| |
nomad.auto_scaler.aws.irsaRole | 文字列型 |
| |
nomad.auto_scaler.aws.region | 文字列型 |
| |
nomad.auto_scaler.aws.secretKey | 文字列型 |
| |
nomad.auto_scaler.enabled | bool |
| |
nomad.auto_scaler.gcp.enabled | bool |
| |
nomad.auto_scaler.gcp.mig_name | 文字列型 |
| |
nomad.auto_scaler.gcp.project_id | 文字列型 |
| |
nomad.auto_scaler.gcp.region | 文字列型 |
| |
nomad.auto_scaler.gcp.service_account | object |
| GCP Authentication Config (3 Options). Option 1: Set service_account with the service account JSON (raw JSON, not a string), and CircleCI will create the secret for you. Option 2: Leave the service_account field as its default, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave the service_account field as its default, and set the workloadIdentity field with a service account email to use workload identities. |
nomad.auto_scaler.gcp.workloadIdentity | 文字列型 |
| |
nomad.auto_scaler.gcp.zone | 文字列型 |
| |
nomad.auto_scaler.scaling.max | 整数 |
| |
nomad.auto_scaler.scaling.min | 整数 |
| |
nomad.auto_scaler.scaling.node_drain_deadline | 文字列型 |
| |
nomad.buildAgentImage | 文字列型 |
| |
nomad.clients | object |
| |
nomad.server.gossip.encryption.enabled | bool |
| |
nomad.server.gossip.encryption.key | 文字列型 |
| |
nomad.server.replicas | 整数 |
| |
nomad.server.rpc.mTLS | object |
| mTLS is strongly suggested for RPC communication. It encrypts traffic but also authenticates clients to ensure no unauthenticated clients can join the cluster as workers. Base64 encoded PEM encoded certificates are expected here. |
nomad.server.rpc.mTLS.CACertificate | 文字列型 |
| base64 encoded nomad mTLS certificate authority |
nomad.server.rpc.mTLS.certificate | 文字列型 |
| base64 encoded nomad mTLS certificate |
nomad.server.rpc.mTLS.privateKey | 文字列型 |
| base64 encoded nomad mTLS private key |
nomad.server.service.unsafe_expose_api | bool |
| |
object_storage | object | | Object storage for build artifacts, audit logs, test results and more. One of object_storage.s3.enabled or object_storage.gcs.enabled must be true for the chart to function. |
object_storage.expireAfter | 整数 |
| number of days after which artifacts will expire |
object_storage.gcs.service_account | object |
| GCP Storage (GCS) Authentication Config (3 Options). Option 1: Set service_account with the service account JSON (raw JSON, not a string), and CircleCI will create the secret for you. Option 2: Leave the service_account field as its default, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave the service_account field as its default, and set the workloadIdentity field with a service account email to use workload identities. |
object_storage.s3 | object |
| S3 Configuration for Object Storage. Authentication methods: AWS Access/Secret Key, and IRSA Role |
object_storage.s3.accessKey | 文字列型 |
| AWS Authentication Config (3 Options). Option 1: Set accessKey and secretKey here, and CircleCI will create the secret for you. Option 2: Leave accessKey and secretKey blank, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave accessKey and secretKey blank, and set the irsaRole field (IAM roles for service accounts), also set region: "your-aws-region". |
object_storage.s3.endpoint | 文字列型 |
| API endpoint for S3. If in AWS us-west-2, for example, this would be the regional endpoint http://s3.us-west-2.amazonaws.com. If using S3 compatible storage, specify the API endpoint of your object storage server |
orb_service.replicas | 整数 |
| Number of replicas to deploy for the orb-service deployment. |
output_processor.replicas | 整数 |
| Number of replicas to deploy for the output-processor deployment. |
permissions_service.replicas | 整数 |
| Number of replicas to deploy for the permissions-service deployment. |
postgresql.auth.existingSecret | 文字列型 |
| |
postgresql.auth.password | 文字列型 |
| |
postgresql.auth.postgresPassword | 文字列型 |
| Password for the "postgres" admin user. Ignored if |
postgresql.auth.username | 文字列型 |
| |
postgresql.fullnameOverride | 文字列型 |
| |
postgresql.image.tag | 文字列型 |
| |
postgresql.internal | bool |
| |
postgresql.persistence.existingClaim | 文字列型 |
| |
postgresql.persistence.size | 文字列型 |
| |
postgresql.postgresqlHost | 文字列型 |
| |
postgresql.postgresqlPort | 整数 |
| |
postgresql.primary.extendedConfiguration | 文字列型 |
| |
postgresql.primary.podAnnotations."backup.velero.io/backup-volumes" | 文字列型 |
| |
prometheus.alertmanager.enabled | bool |
| |
prometheus.enabled | bool |
| |
prometheus.extraScrapeConfigs | 文字列型 |
| |
prometheus.fullnameOverride | 文字列型 |
| |
prometheus.nodeExporter.fullnameOverride | 文字列型 |
| |
prometheus.pushgateway.enabled | bool |
| |
prometheus.server.emptyDir.sizeLimit | 文字列型 |
| |
prometheus.server.fullnameOverride | 文字列型 |
| |
prometheus.server.persistentVolume.enabled | bool |
| |
proxy.enabled | bool |
| If false, all proxy settings are ignored |
proxy.http | object |
| Proxy for HTTP requests |
proxy.https | object |
| Proxy for HTTPS requests |
proxy.no_proxy | リスト |
| List of hostnames, IP CIDR blocks exempt from proxying. Loopback and intra-service traffic is never proxied. |
pusher.key | 文字列型 |
| |
pusher.secret | 文字列型 |
| |
rabbitmq.auth.erlangCookie | 文字列型 |
| |
rabbitmq.auth.existingErlangSecret | 文字列型 |
| |
rabbitmq.auth.existingPasswordSecret | 文字列型 |
| |
rabbitmq.auth.password | 文字列型 |
| |
rabbitmq.auth.username | 文字列型 |
| |
rabbitmq.fullnameOverride | 文字列型 |
| |
rabbitmq.image.tag | 文字列型 |
| |
rabbitmq.podAnnotations."backup.velero.io/backup-volumes" | 文字列型 |
| |
rabbitmq.podLabels.app | 文字列型 |
| |
rabbitmq.podLabels.layer | 文字列型 |
| |
rabbitmq.replicaCount | 整数 |
| |
rabbitmq.statefulsetLabels.app | 文字列型 |
| |
rabbitmq.statefulsetLabels.layer | 文字列型 |
| |
redis.cluster.enabled | bool |
| |
redis.cluster.slaveCount | 整数 |
| |
redis.fullnameOverride | 文字列型 |
| |
redis.image.tag | 文字列型 |
| |
redis.master.podAnnotations."backup.velero.io/backup-volumes" | 文字列型 |
| |
redis.podLabels.app | 文字列型 |
| |
redis.podLabels.layer | 文字列型 |
| |
redis.replica.podAnnotations."backup.velero.io/backup-volumes" | 文字列型 |
| |
redis.statefulset.labels.app | 文字列型 |
| |
redis.statefulset.labels.layer | 文字列型 |
| |
redis.usePassword | bool |
| |
schedulerer.replicas | 整数 |
| Number of replicas to deploy for the schedulerer deployment. |
serveUnsafeArtifacts | bool |
| Warning! Changing this to true will serve HTML artifacts instead of downloading them. This can allow specially-crafted artifacts to gain control of users' CircleCI accounts. |
sessionCookieKey | 文字列型 |
| Session Cookie Key (2 Options). NOTE: Must be exactly 16 bytes. Option 1: Set the value here and CircleCI will create the secret automatically. Option 2: Leave this blank, and create the secret yourself. CircleCI will assume it exists. |
smtp | object |
| Email notification settings |
smtp.port | 整数 |
| ポート 25 のアウトバウンド接続は、ほとんどのクラウド プロバイダーでブロックされます。 Should you select this default port, be aware that your notifications may fail to send. |
smtp.tls | bool |
| StartTLS is used to encrypt mail by default. Only disable this if you can otherwise guarantee the confidentiality of traffic. |
soketi.replicas | 整数 |
| Number of replicas to deploy for the soketi deployment. |
telegraf.args[0] | 文字列型 |
| |
telegraf.args[1] | 文字列型 |
| |
telegraf.config.agent.interval | 文字列型 |
| |
telegraf.config.agent.omit_hostname | bool |
| |
telegraf.config.agent.round_interval | bool |
| |
telegraf.config.custom_config_file | 文字列型 |
| |
telegraf.config.inputs[0].statsd.service_address | 文字列型 |
| |
telegraf.config.outputs[0].prometheus_client.listen | 文字列型 |
| |
telegraf.fullnameOverride | 文字列型 |
| |
telegraf.image.tag | 文字列型 |
| |
telegraf.mountPoints[0].mountPath | 文字列型 |
| |
telegraf.mountPoints[0].name | 文字列型 |
| |
telegraf.mountPoints[0].readOnly | bool |
| |
telegraf.rbac.create | bool |
| |
telegraf.serviceAccount.create | bool |
| |
telegraf.volumes[0].configMap.name | 文字列型 |
| |
telegraf.volumes[0].name | 文字列型 |
| |
test_results_service.replicas | 整数 |
| Number of replicas to deploy for the test-results-service deployment. |
tls.certificate | 文字列型 |
| base64 encoded certificate, leave empty to use self-signed certificates |
tls.privateKey | 文字列型 |
| base64 encoded private key, leave empty to use self-signed certificates |
vault | object |
| External Services configuration |
vault.internal | bool |
| Disables this charts Internal Vault instance |
vault.token | 文字列型 |
| This token is required when |
vault.transitPath | 文字列型 |
| When |
vm_gc.replicas | 整数 |
| Number of replicas to deploy for the vm-gc deployment. |
vm_scaler.prescaled | リスト |
| Configuration options for, and numbers of, prescaled instances. |
vm_scaler.replicas | 整数 |
| Number of replicas to deploy for the vm-scaler deployment. |
vm_service.dlc_lifespan_days | 整数 |
| Number of days to keep DLC volumes before pruning them. |
vm_service.enabled | bool |
| |
vm_service.providers | object |
| Provider configuration for the VM service. |
vm_service.providers.ec2.accessKey | 文字列型 |
| EC2 Authentication Config (3 Options). Option 1: Set accessKey and secretKey here, and CircleCI will create the secret for you. Option 2: Leave accessKey and secretKey blank, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave accessKey and secretKey blank, and set the irsaRole field (IAM roles for service accounts). |
vm_service.providers.ec2.enabled | bool |
| Set to enable EC2 as a virtual machine provider |
vm_service.providers.ec2.subnets | リスト |
| Subnets must be in the same availability zone |
vm_service.providers.gcp.enabled | bool |
| Set to enable GCP Compute as a VM provider |
vm_service.providers.gcp.service_account | object |
| GCP Compute Authentication Config (3 Options). Option 1: Set service_account with the service account JSON (raw JSON, not a string), and CircleCI will create the secret for you. Option 2: Leave the service_account field as its default, and create the secret yourself. CircleCI will assume it exists. Option 3: Leave the service_account field as its default, and set the workloadIdentityField with a service account email to use workload identities. |
vm_service.replicas | 整数 |
| Number of replicas to deploy for the vm-service deployment. |
web_ui.replicas | 整数 |
| Number of replicas to deploy for the web-ui deployment. |
web_ui_404.replicas | 整数 |
| Number of replicas to deploy for the web-ui-404 deployment. |
web_ui_insights.replicas | 整数 |
| Number of replicas to deploy for the web-ui-insights deployment. |
web_ui_onboarding.replicas | 整数 |
| Number of replicas to deploy for the web-ui-onboarding deployment. |
web_ui_org_settings.replicas | 整数 |
| Number of replicas to deploy for the web-ui-org-settings deployment. |
web_ui_project_settings.replicas | 整数 |
| Number of replicas to deploy for the web-ui-project-settings deployment. |
web_ui_server_admin.replicas | 整数 |
| Number of replicas to deploy for the web-ui-server-admin deployment. |
web_ui_user_settings.replicas | 整数 |
| Number of replicas to deploy for the web-ui-user-settings deployment. |
webhook_service.isEnabled | bool |
| |
webhook_service.replicas | 整数 |
| Number of replicas to deploy for the webhook-service deployment. |
workflows_conductor_event_consumer.replicas | 整数 |
| Number of replicas to deploy for the workflows-conductor-event-consumer deployment. |
workflows_conductor_grpc.replicas | 整数 |
| Number of replicas to deploy for the workflows-conductor-grpc deployment. |
ドキュメントの改善にご協力ください
このガイドは、CircleCI の他のドキュメントと同様にオープンソースであり、 GitHub でご利用いただけます。 ご協力いただき、ありがとうございます。
- このページの編集をご提案ください (最初に「コントリビューションガイド」をご覧ください)。
- ドキュメントの問題点を報告する、またはフィードバックやコメントを送信するには、GitHub で issue を作成してください。
- CircleCI は、ユーザーの皆様の弊社プラットフォームにおけるエクスペリエンスを向上させる方法を常に模索しています。 フィードバックをお寄せいただける場合は、リサーチコミュニティにご参加ください。
サポートが必要ですか
CircleCI のサポートエンジニアによる、サービスに関する問題、請求およびアカウントについての質問への対応、設定の構築に関する問題解決のサポートを行っています。 サポートチケットを送信して、CircleCI のサポートエンジニアにお問い合わせください。日本語でお問い合わせいただけます。
または、 サポートサイト から、サポート記事やコミュニティフォーラム、トレーニングリソースをご覧いただけます。
CircleCI Documentation by CircleCI is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.