feature request: specify git branch and directory in YAML install steps

Bug #1201382 reported by Andrew McDermott
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LAVA Project
Triaged
Wishlist
Antonio Terceiro

Bug Description

It would be useful to be able to specify a branch to checkout when specifying a git repo in the install commands and the name of the directory where the clone should reside.

Right now I have two repo's with almost the same content for handling some minor differences between x86 and aarch64. I could do the git commands in the run steps but it seems natural to be able to have more control of the git clone command within the install steps.

For example:

install:
  git-repos:
    - git://git.linaro.org/people/andrew.mcdermott/mauve.git -b kvm-x86-64

OR:

install:
  git-repos:
    - git://git.linaro.org/people/andrew.mcdermott/mauve.git -b aarch64

If the git-repos line was to be executed as a complete git command then you could also specify a directory for the newly checked out repo. And this would then naturally extend to other git clone options.

For example.

install:
  git-repos:
    - git://git.linaro.org/people/andrew.mcdermott/mauve.git -b kvm-x86-64 mauve-kvm-86_64
    - git://git.linaro.org/people/andrew.mcdermott/mauve.git -b aarch64 mauve-aarch64

Revision history for this message
Antonio Terceiro (terceiro) wrote : Re: [Bug 1201382] [NEW] feature request: specify git branch and directory in YAML install steps

the problem with using those lines as git command lines is that we would
have to parse the command line somehow to avoid the risk of shell
command injection. IMO it's better to pass in the needed info already in
a structured way.

I already saw a syntax for this somewhere, but I can't recall exactly
where. Maybe we can use a something like this:

REPOURL#branch#directory

where everything but the REPOURL is optional.

Revision history for this message
Antonio Terceiro (terceiro) wrote :

A cleaner solution is to extend the schema to add new parameters to the repository specification so that we don't have to fiddle with parsing the repo URL in search of these other parameters.

Revision history for this message
Antonio Terceiro (terceiro) wrote :

argh - actually not, because these repos are referenced in the lava-test-shell test definition ... well, we need to think of a solution

Changed in lava-project:
importance: Undecided → Low
status: New → Triaged
assignee: nobody → Antonio Terceiro (terceiro)
Dave Pigott (dpigott)
Changed in lava-project:
importance: Low → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.