From: David Marchand <david.marchand@redhat.com>
To: Thomas Monjalon <thomas@monjalon.net>, Aaron Conole <aconole@redhat.com>
Cc: dev <dev@dpdk.org>, Michael Santana <maicolgabriel@hotmail.com>
Subject: Re: [dpdk-dev] [PATCH 2/4] ci: fix Travis config warnings
Date: Thu, 20 Feb 2020 17:46:03 +0100 [thread overview]
Message-ID: <CAJFAV8wT7QCvW4xOV_09_2yn8_pmyy-vdrZ8AftW7U4UFLfsBQ@mail.gmail.com> (raw)
In-Reply-To: <6771332.6fTUFtlzNn@xps>
On Thu, Feb 20, 2020 at 12:03 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 19/02/2020 20:41, David Marchand:
> > Reading https://config.travis-ci.com/ and using
> > https://config.travis-ci.com/explore to check changes, we can cleanup
> > some warnings reported by the config validation options in Travis.
>
> For documentation purpose, would be good to describe issues in the commit log.
Since I only have this commitlog to update, I intend to push the
series with the following addition:
Example on a job in master:
https://travis-ci.com/DPDK/dpdk/builds/149537002/config
Build config validation:
root: deprecated key doc_packages (anchor on a non-private key)
root: deprecated key build_32b_packages (anchor on a non-private key)
root: deprecated key libabigail_build_packages (anchor on a non-private key)
root: deprecated key extra_packages (anchor on a non-private key)
root: deprecated key aarch64_packages (anchor on a non-private key)
root: key matrix is an alias for jobs, using jobs
For the "(anchor on a non-private key)" warnings, the Travis
documentation [1] recommends prefixing private keys with _ (Travis
schema is available at [2]).
The use of the "matrix" key is allowed, but it is just an alias to the
"jobs" key.
1: https://docs.travis-ci.com/user/build-config-yaml#private-keys-as-yaml-anchors-and-aliases-and-external-tooling
2: https://github.com/travis-ci/travis-yml/blob/730a77f4028b91293a55c8c1c52fc72e64379dde/schema.json
--
David Marchand
next prev parent reply other threads:[~2020-02-20 16:46 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-19 19:41 [dpdk-dev] [PATCH 0/4] Reorganise Travis jobs David Marchand
2020-02-19 19:41 ` [dpdk-dev] [PATCH 1/4] ci: remove unnecessary dependency on Linux headers David Marchand
2020-02-20 10:44 ` Thomas Monjalon
2020-02-20 14:37 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 2/4] ci: fix Travis config warnings David Marchand
2020-02-20 11:03 ` Thomas Monjalon
2020-02-20 12:09 ` David Marchand
2020-02-20 16:46 ` David Marchand [this message]
2020-02-20 21:01 ` Aaron Conole
2020-02-21 10:17 ` Thomas Monjalon
2020-02-20 14:36 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 3/4] ci: use an explicit list of Travis jobs David Marchand
2020-02-20 11:05 ` Thomas Monjalon
2020-02-20 14:35 ` Aaron Conole
2020-02-19 19:41 ` [dpdk-dev] [PATCH 4/4] ci: reorganise " David Marchand
2020-02-19 21:39 ` Aaron Conole
2020-02-20 10:42 ` Thomas Monjalon
2020-02-20 12:22 ` David Marchand
2020-02-20 14:35 ` Aaron Conole
2020-02-20 16:01 ` David Marchand
2020-02-20 19:38 ` [dpdk-dev] [dpdk-ci] " Jeremy Plsek
2020-02-20 0:18 ` [dpdk-dev] " dwilder
2020-02-20 11:07 ` Thomas Monjalon
2020-02-20 21:05 ` [dpdk-dev] [PATCH 0/4] Reorganise " David Marchand
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=CAJFAV8wT7QCvW4xOV_09_2yn8_pmyy-vdrZ8AftW7U4UFLfsBQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=aconole@redhat.com \
--cc=dev@dpdk.org \
--cc=maicolgabriel@hotmail.com \
--cc=thomas@monjalon.net \
/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 NNTP newsgroup(s).