On 08/22/2014 04:34 AM, Milosz Wasilewski wrote:
Carlos,
The problem with that patch is that you can't parametrize the
git-repos part.
But isn't the branch/tag defined either way in the json?
what's the advantage of setting it in the params section vs the install
section?
I think we had a feature request for that but it never
got implemented. For example pm-qa development team uses HEAD instead
of tagged release for their testing.
I understand the problem, but I don't see a good solution at this point :(
Best Regards,
milosz
On 21 August 2014 20:51, Carlos Hernandez <c...@ti.com> wrote:
Some embedded filesystems might not have GIT installed, so
instead of running 'git checkout' in the device under test, add
the tag to the git repo definition so the right branch is checked
out by the dispatcher.
Signed-off-by: Carlos Hernandez <c...@ti.com>
---
openembedded/pwrmgmt.yaml | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/openembedded/pwrmgmt.yaml b/openembedded/pwrmgmt.yaml
index 42a17bb..660e1ec 100644
--- a/openembedded/pwrmgmt.yaml
+++ b/openembedded/pwrmgmt.yaml
@@ -16,15 +16,13 @@ metadata:
install:
git-repos:
- - git://git.linaro.org/power/pm-qa.git
+ - git://git.linaro.org/power/pm-qa.git -b pm-qa-v0.4.13 pm-qa
steps:
- "cd pm-qa"
- - "git checkout $RELEASE"
- "make -C utils"
params:
PWR_TESTARG: cpufreq cpuidle cpuhotplug thermal cputopology
- RELEASE: 'tags/pm-qa-v0.4.13'
run:
steps:
--
1.7.9.5
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
_______________________________________________
linaro-validation mailing list
linaro-validation@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-validation
