Đoàn Trần Công Danh <congdanhqx@xxxxxxxxx> writes:
> This is a nearly rewrite of this series, because there're GitHub Action
> allow running directly inside container.
>
> => I rewrite this series to prepare as much as possible for the GitHub
> Action series.
> ...
> .travis.yml | 10 ++++-
> azure-pipelines.yml | 39 ++++++++++++++++++-
> ci/install-docker-dependencies.sh | 18 +++++++++
> ci/lib.sh | 8 ++++
> ...n-linux32-build.sh => run-docker-build.sh} | 39 +++++++++++++------
> ci/{run-linux32-docker.sh => run-docker.sh} | 28 ++++++++++---
> 6 files changed, 121 insertions(+), 21 deletions(-)
> create mode 100755 ci/install-docker-dependencies.sh
> rename ci/{run-linux32-build.sh => run-docker-build.sh} (63%)
> rename ci/{run-linux32-docker.sh => run-docker.sh} (43%)
Thanks. The above diffstat makes me wonder if it makes more sense
to do the topic from Dscho first to migrate existing CI targets to
GitHub Actions and then add musl job to the ci suite on top? That
way, we won't have to worry about azure-pipelines.yml at all here.
