From: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
To: git@vger.kernel.org
Cc: "Đoàn Trần Công Danh" <congdanhqx@gmail.com>
Subject: [PATCH 4/4] ci: add arm64 CI environment via CircleCI
Date: Fri, 3 Mar 2023 20:46:06 +0700 [thread overview]
Message-ID: <db5c58fb3ee114b56f110dcd20f938e77d8b476f.1677850518.git.congdanhqx@gmail.com> (raw)
In-Reply-To: <cover.1677850517.git.congdanhqx@gmail.com>
Signed-off-by: Đoàn Trần Công Danh <congdanhqx@gmail.com>
---
.circleci/config.yml | 17 +++++++++++++++++
ci/lib.sh | 19 +++++++++++++++++++
2 files changed, 36 insertions(+)
create mode 100644 .circleci/config.yml
diff --git a/.circleci/config.yml b/.circleci/config.yml
new file mode 100644
index 0000000000..2f5e0966b7
--- /dev/null
+++ b/.circleci/config.yml
@@ -0,0 +1,17 @@
+# .circleci/config.yml
+jobs:
+ build:
+ machine:
+ image: ubuntu-2004:2022.04.1
+ resource_class: arm.medium
+ environment:
+ jobname: linux-gcc
+ runs_on_pool: ubuntu-arm64
+ steps:
+ - checkout
+ - run: ci/install-dependencies.sh
+ - run:
+ name: Build and Tests
+ command: ci/run-build-and-tests.sh
+ - store_test_results:
+ path: t/out
diff --git a/ci/lib.sh b/ci/lib.sh
index 3c19267a56..8b0c727950 100755
--- a/ci/lib.sh
+++ b/ci/lib.sh
@@ -201,6 +201,25 @@ then
MAKEFLAGS="$MAKEFLAGS --jobs=10"
test windows != "$CI_OS_NAME" ||
GIT_TEST_OPTS="--no-chain-lint --no-bin-wrappers $GIT_TEST_OPTS"
+elif test "$CIRCLECI" = true
+then
+ CI_TYPE=circleci
+ CI_BRANCH="$CIRCLE_BRANCH"
+ CI_COMMIT="$CIRCLE_SHA1"
+ CI_JOB_ID="$CIRCLE_WORKFLOW_JOB_ID"
+ CI_JOB_NUMBER="$CIRCLE_BUILD_NUM"
+ CI_OS_NAME="$(echo "$AGENT_OS" | tr A-Z a-z)"
+ test darwin != "$CI_OS_NAME" || CI_OS_NAME=osx
+ CI_REPO_SLUG="$(expr "$CIRCLE_REPOSITORY_URL" : '.*:\([^/]*/[^/]*\)\.git$')"
+ CC="${CC:-gcc}"
+
+ # use a subdirectory of the cache dir (because the file share is shared
+ # among *all* phases)
+ cache_dir="$HOME/none"
+
+ export GIT_PROVE_OPTS="--timer --jobs 10"
+ export GIT_TEST_OPTS="--verbose-log -x --write-junit-xml"
+ MAKEFLAGS="$MAKEFLAGS --jobs=10"
else
echo "Could not identify CI type" >&2
env >&2
--
2.40.0.rc1.2.gd15644fe02
next prev parent reply other threads:[~2023-03-03 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-03 13:46 [PATCH 0/4] Add a CI for unsigned char system Đoàn Trần Công Danh
2023-03-03 13:46 ` [PATCH 1/4] ci/lib.sh: remove an useless break Đoàn Trần Công Danh
2023-03-03 13:46 ` [PATCH 2/4] ci/install-dependencies: libify p4 and git-lfs installation Đoàn Trần Công Danh
2023-03-03 13:46 ` [PATCH 3/4] ci/install-dependencies: install git-lfs for arm64 build Đoàn Trần Công Danh
2023-03-03 13:46 ` Đoàn Trần Công Danh [this message]
2023-03-03 13:54 ` [PATCH 4/4] ci: add arm64 CI environment via CircleCI Đoàn Trần Công Danh
2023-03-09 9:53 ` [PATCH 0/4] Add a CI for unsigned char system Jeff King
2023-03-09 10:26 ` Chris Torek
2023-03-09 10:57 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=db5c58fb3ee114b56f110dcd20f938e77d8b476f.1677850518.git.congdanhqx@gmail.com \
--to=congdanhqx@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).