summaryrefslogtreecommitdiff
path: root/.github/workflows/ubuntu.yml
AgeCommit message (Collapse)Author
2020-12-31merge revision(s) 45fd4436ee146f95487b1575c5a2df5cf77f4717:nagachika
Use $GITHUB_ENV instead of set-env https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/
2020-01-30Allow failures with rss tests on test-bundled-gemsHiroshi SHIBATA
2020-01-30Add branch option to checkout on pushKazuhiro NISHIYAMA
2020-01-30Slightly change the job wording [ci skip]Takashi Kokubun
mame-san said it's weird
2020-01-30Support running Actions on a forkTakashi Kokubun
Since 8c9450e7b875db846b19cc631af0d7fee66db5c6, we increased the chance to run GitHub Actions on a fork, as we usually use a topic branch instead of master when filing a pull request. This patch makes it possible to reuse the same GitHub Actions config on a fork repository.
2020-01-30Directly refer to GitHub eventsTakashi Kokubun
instead of unnecessarily defining env vars
2020-01-30Remove code to prevent double build on trunkTakashi Kokubun
trunk branch was deleted.
2020-01-30More consistent failure notificationsTakashi Kokubun
The format is the same as Travis / AppVeyor now.
2020-01-30Revert "Remove TEST_BUNDLED_GEMS_ALLOW_FAILURES"Takashi Kokubun
This reverts commit 75e8dd58f69c190c9698d0133942032903fb2f07. We seem to randomly hit another issue these days: https://github.com/ruby/ruby/runs/368756135 https://github.com/ruby/ruby/runs/368756191
2019-12-13Ignore error of `apt-get update` on GitHub ActionsKazuhiro NISHIYAMA
2019-12-11Try to use `set-output`Kazuhiro NISHIYAMA
because commit info are not necessary in env.
2019-12-11Create dummy files when check onlyKazuhiro NISHIYAMA
because foo.rb in build directory breaks test-bundler https://github.com/ruby/ruby/runs/343168046#step:20:125
2019-12-11Create more dummy files in build directoryKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2736
2019-12-11Do not load files in build directoryKazuhiro NISHIYAMA
related https://bugs.ruby-lang.org/issues/16177 Notes: Merged: https://github.com/ruby/ruby/pull/2736
2019-11-30Make extract-gems only if test_task is checkKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2678
2019-11-30Add update-gems before extract-gemsKazuhiro NISHIYAMA
(windows.yml used `nmake up`) Notes: Merged: https://github.com/ruby/ruby/pull/2678
2019-11-30Add extract-gems to GitHub Actions CIKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2678
2019-11-19Remove TEST_BUNDLED_GEMS_ALLOW_FAILURESKazuhiro NISHIYAMA
https://github.com/seattlerb/minitest/pull/798 is closed
2019-11-13Make GitHub Actions notification more like TravisTakashi Kokubun
Build's sequential number is a link in Travis, and also YYYY-MM-DD-XX is a little hard to parse.
2019-11-13Use shallow-since instead of depthKazuhiro NISHIYAMA
commit number of today requires log since 0:00 UTC. So commits of 24 hours are enough. https://www.git-scm.com/docs/git-clone#Documentation/git-clone.txt---depthltdepthgt > Implies --single-branch unless --no-single-branch is given to fetch the histories near the tips of all branches. So I add `--single-branch` too. Notes: Merged: https://github.com/ruby/ruby/pull/2680
2019-11-12Migrate Wercker MJIT tests to Actions (#2676)Takashi Kokubun
* Migrate Wercker MJIT tests to Actions * Support pull request for testing * Capitalize other jobs too * Make it a command name for consistency [ci skip] * Remove wercker.yml * Add --jit-verbose=2 for debugging * Install MJIT headers * Separate install for sudo * Trigger build Notes: Merged-By: k0kubun <takashikkbn@gmail.com>
2019-11-13Add commit number of today to notification of GitHub ActionsKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2675
2019-11-12Stop debugging the same thing twiceTakashi Kokubun
See L25-28
2019-11-12Remove MSPECOPT formerly for debuggingTakashi Kokubun
At least the comment looks obsoleted. Aren't we using $JOBS already?
2019-11-12Improve Actions job name shown on toolipTakashi Kokubun
Hoping to make it like `make (check, ...)`, `make (test-bundler, ...)` instead of `latest (...)` because some of the jobs are already not running on a latest platform.
2019-11-12Run test-bundler / test-bundled-gems for UbuntuTakashi Kokubun
only once. Doing it on multiple Ubuntu versions may not worth it.
2019-11-13Use style of set-envKazuhiro NISHIYAMA
https://help.github.com/en/actions/automating-your-workflow-with-github-actions/development-tools-for-github-actions#set-an-environment-variable-set-env
2019-11-05Set $JOBS to Tests for parallel testsNobuyoshi Nakada
2019-11-05Simplify test tasksNobuyoshi Nakada
Removed `if` conditions separating `test-bundled-gems`, and pass `TESTOPTS` and `TEST_BUNDLED_GEMS_ALLOW_FAILURES` via `env`. Notes: Merged: https://github.com/ruby/ruby/pull/2643
2019-10-28Try out-of-place buildNobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/2622
2019-10-28Add more matrix info to slack payloadKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2621
2019-10-27Add ubuntu-16.04 to matrix of GitHub ActionsKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2617
2019-10-10Remove unreachable step level `[ci skip]`Kazuhiro NISHIYAMA
2019-10-09Check '[ci skip]' at job levelKazuhiro NISHIYAMA
2019-09-30Run test-unit tests in CIBenoit Daloze
Notes: Merged: https://github.com/ruby/ruby/pull/2506
2019-09-29Exclude the test-unit bundled gem tests since they also fail since the ↵Benoit Daloze
Time#inspect change * See https://github.com/test-unit/test-unit/issues/165 Notes: Merged: https://github.com/ruby/ruby/pull/2503
2019-09-29Remove continue-on-error for test-bundled-gemsBenoit Daloze
* Otherwise, it takes a very long time to notice those tests broke. Notes: Merged: https://github.com/ruby/ruby/pull/2503
2019-09-13Dump some informationKazuhiro NISHIYAMA
Notes: Merged: https://github.com/ruby/ruby/pull/2457
2019-09-04Add TEST_BUNDLED_GEMS_ALLOW_FAILURES=minitestKazuhiro NISHIYAMA
2019-09-04`$JOBS` does not set in `env:`Kazuhiro NISHIYAMA
2019-09-04Use RUBY_TESTOPTS instead of TESTOPTSKazuhiro NISHIYAMA
https://github.com/ruby/ruby/pull/2417#issuecomment-526884646 > `TESTOPTS` is defaulted to `$(RUBY_TESTOPTS)` in `common.mk` file. > Use the latter name to pass options via an environment variable.
2019-08-28Use JOBS again like macos.ymlKazuhiro NISHIYAMA
2019-08-28Change name to `Tests (test-bundled-gems)`Kazuhiro NISHIYAMA
2019-08-28Remove GITHUB_SHA from jobs.<job_id>.steps.envKazuhiro NISHIYAMA
because default value overrides it. https://help.github.com/en/articles/virtual-environments-for-github-actions#environment-variables
2019-08-27Revert "Explain which test task"Nobuyoshi Nakada
This reverts commit 9bc1667a188392b94971b9b96507af76cbd5f413. `name` lines are not expanded.
2019-08-27Explain which test taskNobuyoshi Nakada
2019-08-26Expand JOBS instead of meaningless export (#2402)Kazuhiro NISHIYAMA
* Expand JOBS instead of meaningless export * Remove -j option in TESTOPTS of test-bundled-gems https://github.com/ruby/ruby/runs/203129516#step:10:167 > invalid option: -j3 Notes: Merged-By: znz
2019-08-22Make GitHub Actions Slack notification consistentTakashi Kokubun
with Travis, rather than AppVeyor. Formerly it was made similar to AppVeyor to provide some normal set of CI failure notification. But for some reason people preferred a shorter variant and introduced a1d606c079f6c3d1779d885e0bf2e3991251609e and d8d8015b93c6daa8d8433895464db3493a2056e2. Instead of AppVeyor format, this commit chose Travis-like format to achieve consistency and to include usual CI-failure information, while keeping it one-liner for people who prefer short notifications. Note that this shrinks the 40-char sha to 10-char, using the new feature of k0kubun/action-slack@v2.0.0: https://github.com/k0kubun/action-slack/commit/1c88a05dac664cbafa1c99a37f292ed23ac1c289
2019-08-22Remove footer from message to Slackaycabta
2019-08-22Show short message to Slackaycabta
generated by cgit v1.2.3 (git 2.25.1) at 2026-05-29 19:22:17 +0000