From: "Kevin Hilman" <khilman@baylibre.com>
To: Aditya Srivastava <adityasrivastava301199@gmail.com>,
kernelci@groups.io,
Aditya Srivastava <adityasrivastava301199@gmail.com>
Subject: Re: Contribute to KernelCI in Kubernetes or Cloud
Date: Wed, 22 Jul 2020 13:55:05 -0700 [thread overview]
Message-ID: <7hmu3r6ziu.fsf@baylibre.com> (raw)
In-Reply-To: <CAJMT-dGA6ELQbnJt5qDsDhu3aKa6ixQC0Pv1QCNW_-WpGwTNRw@mail.gmail.com>
Aditya Srivastava <adityasrivastava301199@gmail.com> writes:
[...]
> I had one concern though, in the jinja2 file[1] the way args are inputted,
> Can't there be a way to create a config file or something to use instead of
> writing that huge args part (which can be error prone)
Yes, as Guillaume said, we need a way to use config files for the tools.
However, if we go this route, how do you pass the config file to the k8s
job? So far, I only know how to start containers with
arguments/parameters passed in env variables.
Kevin
next prev parent reply other threads:[~2020-07-22 20:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 20:22 Contribute to KernelCI in Kubernetes or Cloud Aditya Srivastava
2020-07-06 18:10 ` Kevin Hilman
2020-07-15 8:39 ` adityasrivastava301199
2020-07-21 17:14 ` Kevin Hilman
[not found] ` <1621E054EEFB3FDC.11249@groups.io>
2020-07-17 9:40 ` Aditya Srivastava
2020-07-20 8:07 ` Guillaume Tucker
2020-07-22 20:55 ` Kevin Hilman [this message]
2020-07-23 12:46 ` Aditya Srivastava
2020-07-24 18:48 ` Kevin Hilman
[not found] ` <CAJMT-dGsKh9vObdBxbdTQNoC7_mVx7qgxyX6AN0pXzePepjbFQ@mail.gmail.com>
[not found] ` <7hzh7j2qha.fsf@baylibre.com>
[not found] ` <CAJMT-dEoEerBUcTeZT97ZfWbqDy3f0UhB8xordgG=Ae8wzOEtQ@mail.gmail.com>
[not found] ` <7hlfj03opw.fsf@baylibre.com>
2020-07-31 8:38 ` Aditya Srivastava
2020-07-31 16:48 ` Kevin Hilman
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=7hmu3r6ziu.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=adityasrivastava301199@gmail.com \
--cc=kernelci@groups.io \
/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