Message ID | cover.1585832270.git.congdanhqx@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | Travis + Azure jobs for linux with musl libc | expand |
Đoàn Trần Công Danh <congdanhqx@gmail.com> 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.
On 2020-04-02 10:53:35-0700, Junio C Hamano <gitster@pobox.com> wrote: > Đoàn Trần Công Danh <congdanhqx@gmail.com> 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. You can ignore the change to azure-pipelines.yml in 6/6 to reduce noise about Azure (it'll be deleted by next series anyway). And declare that this series is working for Travis only (as same intention of v1). New diffstat: ---------------8<------------------ .travis.yml | 10 +++++- azure-pipelines.yml | 4 +-- ci/install-docker-dependencies.sh | 18 +++++++++++ ci/lib.sh | 8 +++++ ci/{run-linux32-build.sh => run-docker-build.sh} | 39 ++++++++++++++++-------- ci/{run-linux32-docker.sh => run-docker.sh} | 28 +++++++++++++---- 6 files changed, 86 insertions(+), 21 deletions(-) ---------------->8---------------- In _my_ opinion, I still prefer have this series first. But, if we prefer to have GitHub Action first: - We'll need 5/6 moved to that series - In the rebased of this series, we'll change about 10 lines in GitHub Action yml. If people think it's better that way, please tell me, I could re-order it.