aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/.github/workflows/ci_travis.yml (unfollow)
Commit message (Collapse)Author
2023-07-03project.ci.cmake -> project.ci.buildEgor Tensin
Accordingly, rename ci-cmake to ci-build.
2023-03-02workflows: trigger for pathsEgor Tensin
This should speed things up. Hopefully I didn't mess it up.
2023-01-02workflows: use a newer Boost versionEgor Tensin
windows-latest no longer support building older Boost releases.
2022-12-11workflows: upgrade actionsEgor Tensin
2021-06-19workflows: use -latest images where appropriateEgor Tensin
2021-05-08workflows: lint, tweak job names, etc.Egor Tensin
2021-05-04workflows: add run_foo.ps1, compact YAMLEgor Tensin
2021-04-24workflows: use actions/cache@v2Egor Tensin
The v2 tag was finally bumped to v2.1.5 (I needed v2.1.4).
2021-04-24workflows: fix cache pathEgor Tensin
Forgot to switch to $RUNNER_WORKSPACE/build in the workflows also. Also, the usual crap with the cache action made me change the cache keys, or it would be restore in the wrong location for some reason.
2021-04-13project.ci: add --hint parameterEgor Tensin
This is a stupid workaround for testing other CI systems on GitHub Actions.
2021-04-13remove excessive logging & obsolete project.ci.* packagesEgor Tensin
Logging command line arguments before parsing them is a bit excessive.
2021-03-24project.ci: use same variable names for all CIsEgor Tensin
Using different ones was quite weird to begin with.
2021-03-24project.ci: change build directoryEgor Tensin
It's now <source directory>/../build for consistency.
2021-03-14workflows: _really_ fix Boost caching?..Egor Tensin
actions/cache@v2 doesn't work on windows-2016 images, since those contain the GNU tar, which cannot work with \ as path separator. This was fixed in package @actions/cache v1.0.5, which is used by action actions/cache@v2.1.4 [1][2]. In addition, it simply couldn't find tar.exe on those images thanks to my action cleanup-path, which removed the corresponding directory (I think it was Git's bin/) from PATH. It worked for windows-2019 images thanks to them containing tar.exe in System32. Solved by turning cleanup-path into a JavaScript action with a "post" step, which restores the original PATH value. [1]: https://github.com/actions/virtual-environments/issues/480 [2]: https://github.com/actions/toolkit/issues/632
2021-03-13project.ci: cache Boost downloadsEgor Tensin
2021-01-19bye-bye, Travis & AppVeyor!no_more_travisEgor Tensin
2021-01-18project.ci: add GitHub ActionsEgor Tensin
2021-01-18project.ci: --install picks the directory automaticallyEgor Tensin
2021-01-18workflows: add Travis/AppVeyor simulationsEgor Tensin
2021-01-18workflows: add "Basic usage"Egor Tensin