public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: robert.marshall@codethink.co.uk (Robert Marshall)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] script for health check (or any script which involves uploading kernel to BBB)
Date: Wed, 10 May 2017 14:20:14 +0100	[thread overview]
Message-ID: <87bmr0u9v5.fsf@ctlt579.codethink.co.uk> (raw)

The kernelci-build uploads the kernel (for a BBB build) to

http://localhost:8010/cip-bbb1/cip_v4.4.27/v4.4.27/arm/omap2plus_defconfig/

So that's

http://localhost:8010/$TREE_NAME/$BRANCH/$TAG/$ARCH/omap2plus_defconfig/

I think the ARCH can be embedded in the script (otherwise we'd need to
embed omap2plus_defconfig too..) so we just need a script using the
other 3 values which can then sed a base yaml file creating the
correct urls outputting it to a new file and then running lava-tool on
that will upload and test that kernel build to the BBB

TREE_NAME can be taken from the environment variable (if it's not set -
if for example the kernel wasn't build on this login) request the user
to set it before running the script

BRANCH and TAG can be retrieved via git commands much as build.py does

So my intention is to create a script in /vagrant/scripts which is run

/vagrant/scripts/create_test.sh input.yaml output.yaml which takes a
yaml file - which could be in the release or a new one created by a B at D
user and outputs a file (the second parameter) which can then be used in
a lava-tool command


Thoughts? Counter suggestions?


Robert

             reply	other threads:[~2017-05-10 13:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 13:20 Robert Marshall [this message]
2017-05-10 13:34 ` [cip-dev] script for health check (or any script which involves uploading kernel to BBB) Agustin Benito Bethencourt

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=87bmr0u9v5.fsf@ctlt579.codethink.co.uk \
    --to=robert.marshall@codethink.co.uk \
    --cc=cip-dev@lists.cip-project.org \
    /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