From: Chris Packham <noreply@github.com>
To: crossgcc@sourceware.org
Subject: [crosstool-ng/crosstool-ng] 0b096f: CI: Create continuous-integration-workflow.yml
Date: Wed, 26 Aug 2020 00:31:26 -0700 [thread overview]
Message-ID: <crosstool-ng/crosstool-ng/push/refs/heads/master/60473e-f547a1@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/crosstool-ng/crosstool-ng
Commit: 0b096f4164fdac9e7b7d186e3ca72f52906dff72
https://github.com/crosstool-ng/crosstool-ng/commit/0b096f4164fdac9e7b7d186e3ca72f52906dff72
Author: Chris Packham <judge.packham@gmail.com>
Date: 2020-08-24 (Mon, 24 Aug 2020)
Changed paths:
A .github/workflows/continuous-integration-workflow.yml
Log Message:
-----------
CI: Create continuous-integration-workflow.yml
Create a continuous integration workflow that builds a few sample
configurations.
Future improvements would be to have a single job that builds ct-ng and
shares the artifacts with the matrix jobs for building the individual
toolchains. It would also be a good idea to fetch and cache the various
source tarballs.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: 0a4bed1a92ebc52ff31b29672b39aca4ad223f62
https://github.com/crosstool-ng/crosstool-ng/commit/0a4bed1a92ebc52ff31b29672b39aca4ad223f62
Author: Chris Packham <judge.packham@gmail.com>
Date: 2020-08-24 (Mon, 24 Aug 2020)
Changed paths:
M .github/workflows/continuous-integration-workflow.yml
Log Message:
-----------
CI: Only install packages not already present
The GitHub runners have most of the required packages installed already.
Only install the 3 extra that we need for ct-ng.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: d52c897a719badfb503ef1d9c157728d9bc4593a
https://github.com/crosstool-ng/crosstool-ng/commit/d52c897a719badfb503ef1d9c157728d9bc4593a
Author: Chris Packham <judge.packham@gmail.com>
Date: 2020-08-24 (Mon, 24 Aug 2020)
Changed paths:
M .github/workflows/continuous-integration-workflow.yml
Log Message:
-----------
CI: upload build logs as artifacts
Upload the config.log from building ct-ng as well as build.log and
.config from the toolchain builds.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: d9791f4fcb74a6d8fd44684f666d727fd46ab3fb
https://github.com/crosstool-ng/crosstool-ng/commit/d9791f4fcb74a6d8fd44684f666d727fd46ab3fb
Author: Chris Packham <judge.packham@gmail.com>
Date: 2020-08-24 (Mon, 24 Aug 2020)
Changed paths:
M .github/workflows/continuous-integration-workflow.yml
Log Message:
-----------
CI: Build ct-ng once
Build ct-ng once and use the result to build the toolchains.
Signed-off-by: Chris Packham <judge.packham@gmail.com>
Commit: f547a1cffdb360843b75b6b00553b2cdae7e9633
https://github.com/crosstool-ng/crosstool-ng/commit/f547a1cffdb360843b75b6b00553b2cdae7e9633
Author: Chris Packham <judge.packham@gmail.com>
Date: 2020-08-26 (Wed, 26 Aug 2020)
Changed paths:
A .github/workflows/continuous-integration-workflow.yml
Log Message:
-----------
Merge pull request #1377 from cpackham/master
CI: Use github actions for continous integration
Compare: https://github.com/crosstool-ng/crosstool-ng/compare/60473e727452...f547a1cffdb3
reply other threads:[~2020-08-26 7:31 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=crosstool-ng/crosstool-ng/push/refs/heads/master/60473e-f547a1@github.com \
--to=noreply@github.com \
--cc=crossgcc@sourceware.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.
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).