[ci] Delete .circleci
Everything has been migrated to GH. It's time to say goodbye... ghstack-source-id: c7a9f49a729bd4b1d29a53a7b22dfa33f5a4eaf2 Pull Request resolved: https://github.com/facebook/react/pull/30496
Lauren Tan committed
Jul 29, 2024 at 11:26 UTC
a6b5ed01ae98a18507cb92d8e932a8ca321602e6
1 file changed
-132
.circleci/config.yml
deleted
-132
@@ -1,132 +0,0 @@
1
-version: 2.1
2
-
3
-aliases:
4
- - &docker
5
- - image: cimg/node:18.20.1-browsers
6
-
7
- - &environment
8
- TZ: /usr/share/zoneinfo/America/Los_Angeles
9
-
10
- - &TEST_PARALLELISM 20
11
-
12
- - &attach_workspace
13
- at: build
14
-
15
-commands:
16
- setup_node_modules:
17
- description: "Restore node_modules"
18
- steps:
19
- - restore_cache:
20
- name: Restore yarn cache
21
- keys:
22
- - v2-yarn_cache-{{ arch }}-{{ checksum "yarn.lock" }}
23
- - run:
24
- name: Install dependencies
25
- command: |
26
- yarn install --frozen-lockfile --cache-folder ~/.cache/yarn
27
- if [ $? -ne 0 ]; then
28
- yarn install --frozen-lockfile --cache-folder ~/.cache/yarn
29
- fi
30
- environment:
31
- # If we start needing the Electron binary, please ensure the binary is cached in CI following https://www.electronjs.org/docs/latest/tutorial/installation
32
- ELECTRON_SKIP_BINARY_DOWNLOAD: 1
33
- - save_cache:
34
- name: Save yarn cache
35
- key: v2-yarn_cache-{{ arch }}-{{ checksum "yarn.lock" }}
36
- paths:
37
- - ~/.cache/yarn
38
-
39
-# The CircleCI API doesn't yet support triggering a specific workflow, but it
40
-# does support triggering a pipeline. So as a workaround you can triggger the
41
-# entire pipeline and use parameters to disable everything except the workflow
42
-# you want. CircleCI recommends this workaround here:
43
-# https://support.circleci.com/hc/en-us/articles/360050351292-How-to-trigger-a-workflow-via-CircleCI-API-v2-
44
-parameters:
45
- # This is only set when triggering the CI pipeline via an API request.
46
- prerelease_commit_sha:
47
- type: string
48
- default: ''
49
-
50
-jobs:
51
- publish_prerelease:
52
- parameters:
53
- commit_sha:
54
- type: string
55
- release_channel:
56
- type: string
57
- dist_tag:
58
- type: string
59
- docker: *docker
60
- environment: *environment
61
- steps:
62
- - checkout
63
- - setup_node_modules
64
- - run:
65
- name: Run publish script
66
- command: |
67
- git fetch origin main
68
- cd ./scripts/release && yarn && cd ../../
69
- scripts/release/prepare-release-from-ci.js --skipTests -r << parameters.release_channel >> --commit=<< parameters.commit_sha >>
70
- cp ./scripts/release/ci-npmrc ~/.npmrc
71
- scripts/release/publish.js --ci --tags << parameters.dist_tag >>
72
-
73
-workflows:
74
- # Used to publish a prerelease manually via the command line
75
- publish_preleases:
76
- when: << pipeline.parameters.prerelease_commit_sha >>
77
- jobs:
78
- - publish_prerelease:
79
- name: Publish to Canary channel
80
- commit_sha: << pipeline.parameters.prerelease_commit_sha >>
81
- release_channel: stable
82
- # The tags to use when publishing canaries. The main one we should
83
- # always include is "canary" but we can use multiple (e.g. alpha,
84
- # beta, rc). To declare multiple, use a comma-separated string, like
85
- # this:
86
- # dist_tag: "canary,alpha,beta,rc"
87
- #
88
- # TODO: We currently tag canaries with "next" in addition to "canary"
89
- # because this used to be called the "next" channel and some
90
- # downstream consumers might still expect that tag. We can remove this
91
- # after some time has elapsed and the change has been communicated.
92
- dist_tag: "canary,next,rc"
93
- - publish_prerelease:
94
- name: Publish to Experimental channel
95
- requires:
96
- # NOTE: Intentionally running these jobs sequentially because npm
97
- # will sometimes fail if you try to concurrently publish two
98
- # different versions of the same package, even if they use different
99
- # dist tags.
100
- - Publish to Canary channel
101
- commit_sha: << pipeline.parameters.prerelease_commit_sha >>
102
- release_channel: experimental
103
- dist_tag: experimental
104
-
105
- # Publishes on a cron schedule
106
- publish_preleases_nightly:
107
- unless: << pipeline.parameters.prerelease_commit_sha >>
108
- triggers:
109
- - schedule:
110
- # At 10 minutes past 16:00 on Mon, Tue, Wed, Thu, and Fri
111
- cron: "10 16 * * 1,2,3,4,5"
112
- filters:
113
- branches:
114
- only:
115
- - main
116
- jobs:
117
- - publish_prerelease:
118
- name: Publish to Canary channel
119
- commit_sha: << pipeline.git.revision >>
120
- release_channel: stable
121
- dist_tag: "canary,next,rc"
122
- - publish_prerelease:
123
- name: Publish to Experimental channel
124
- requires:
125
- # NOTE: Intentionally running these jobs sequentially because npm
126
- # will sometimes fail if you try to concurrently publish two
127
- # different versions of the same package, even if they use different
128
- # dist tags.
129
- - Publish to Canary channel
130
- commit_sha: << pipeline.git.revision >>
131
- release_channel: experimental
132
- dist_tag: experimental