1. Z.Archive.Ovsdb-Dev
  2. Messages

Re: [integration-dev] running tempest tests

Flavio Fernandes <ffernand@...>
 





On Apr 1, 2015, at 9:22 AM, Colin Dixon <colin@...> wrote:

Thanks! That's exactly what I wanted. At the very least people can use it to track their progress in fixing bugs that are breaking tempest.

—Colin


To make it a bit easier to display the counts, consider using this handy script I added:


It will grab a json from jenkins to know what builds took place, and then extract the status from testr_results.html in the build artifact for the build.

— flavio



On Mar 28, 2015 11:33 AM, "Flavio Fernandes" <ffernand@...> wrote:

On Mar 24, 2015, at 11:27 PM, Luis Gomez <ecelgp@...> wrote:

Forgot to mention you have to replace ${DISTRIBUTION} with karaf so the script will look like:


As expected, it worked like a champ. Thanks Luis!

@Colin: @Kyle: @Sam: This is the gerrit [1] for a jenkins job that will run tempest against latest ODL. I do not expect to see it passing in the near
future, but it may provide us some history to track the progress on tempest harvesting. :)

Thanks,

— flavio





    # Extract the BUNDLEVERSION from the pom.xml
    BUNDLEVERSION=`xpath pom.xml '/project/version/text()' 2> /dev/null`
    echo "Bundle version is ${BUNDLEVERSION}”

    # Acquire the timestamp information from maven-metadata.xml
    wget ${NEXUSPATH}/${BUNDLEVERSION}/maven-metadata.xml
    TIMESTAMP=`xpath maven-metadata.xml "//snapshotVersion[extension='zip'][1]/value/text()" 2>/dev/null`
    echo "Nexus timestamp is ${TIMESTAMP}”

    BUNDLEFOLDER=“distribution-karaf-${BUNDLEVERSION}"
    BUNDLE=“distribution-karaf-${TIMESTAMP}.zip"
    BUNDLEURL="${NEXUSPATH}/${BUNDLEVERSION}/${BUNDLE}”

    echo "Distribution bundle URL is ${BUNDLEURL}”
    echo "Distribution bundle is ${BUNDLE}”
    echo "Distribution folder is ${BUNDLEFOLDER}"


On Mar 24, 2015, at 6:13 PM, Luis Gomez <ecelgp@...> wrote:

FYI I am already using a similar script to calculate latest Nexus artifact for a given integration branch (note if you do not want to download integration git, you can replace BUNDLEVERSION=0.3.0-SNAPSHOT in the script below):

    # Extract the BUNDLEVERSION from the pom.xml
    BUNDLEVERSION=`xpath pom.xml '/project/version/text()' 2> /dev/null`
    echo "Bundle version is $BUNDLEVERSION"
    # Acquire the timestamp information from maven-metadata.xml
    wget ${NEXUSPATH}/${BUNDLEVERSION}/maven-metadata.xml
    TIMESTAMP=`xpath maven-metadata.xml "//snapshotVersion[extension='zip'][1]/value/text()" 2>/dev/null`
    echo "Nexus timestamp is $TIMESTAMP"
    BUNDLEFOLDER="distribution-${DISTRIBUTION}-${BUNDLEVERSION}"
    BUNDLE="distribution-${DISTRIBUTION}-${TIMESTAMP}.zip"
    BUNDLEURL="${NEXUSPATH}/${BUNDLEVERSION}/${BUNDLE}"
    echo "Distribution bundle URL is ${BUNDLEURL}”
    echo "Distribution bundle is ${BUNDLE}”
    echo "Distribution folder is ${BUNDLEFOLDER}"

Then I do wget ${BUNDLEURL} to download the distribution, unzip ${BUNDLE}, cd ${BUNDLEFOLDER} to set some configuration and run karaf. All these scripts are available in releng/builder repo [1]


 BR/Luis



On Mar 24, 2015, at 3:14 PM, Andrew Grimberg <agrimberg@...> wrote:

On Tue, 2015-03-24 at 15:10 -0500, Colin Dixon wrote:
Right now we have tempest tests running against Helium-SR3 whenever there
are patches pushed in OpenStack as this job:
https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-openstack-gerrit/configure

Flavio has created a new version that does the same thing but to use the
latest Helium:
https://jenkins.opendaylight.org/releng/view/ovsdb/job/ovsdb-openstack-gerrit/configure

These four lines:

# Use Lithium build
DEVSTACK_LOCAL_CONFIG+="ODL_NAME=distribution-karaf-0.3.0-SNAPSHOT;"

DEVSTACK_LOCAL_CONFIG+="ODL_PKG=distribution-karaf-0.3.0-20150323.224826-778.zip;"
DEVSTACK_LOCAL_CONFIG+="ODL_URL=
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT
;"


I have two questions:
1.) Can somebody (Andrew or Thanh) help Flavio to get a version of this
that runs using the (locally-built) karaf distribution in the ovsdb project
on every ovsdb-verify job?

2.) Can we figure out a way to run these tests against integration without
having to know the weird numbers after "distribution-karaf-0.3.0-" and
before ".zip"?

In answer to point 2 you can first pull
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/maven-metadata.xml and then run the following to get the "weird numbers" needed:

xpath maven-metadata.xml
'/metadata/versioning/snapshotVersions/snapshotVersion[3]/value/text()'

so.. in script form:

--[cut]--
wget
https://nexus.opendaylight.org/content/repositories/opendaylight.snapshot/org/opendaylight/integration/distribution-karaf/0.3.0-SNAPSHOT/maven-metadata.xml
SNAPSHOTVER=`xpath maven-metadata.xml
'/metadata/versioning/snapshotVersions/snapshotVersion[3]/value/text()'
2> /dev/null`
--[/cut]--

Now you know the actual filename, it's
distribution-karaf-${SNAPSHOTVER}.zip

We used to do this sort of thingwith the old integration pipeline before
it was moved to releng. I'm not certain what they're doing now as I
haven't looked

-Andy-

-- 
Andrew J Grimberg
Systems Administrator
The Linux Foundation
_______________________________________________
integration-dev mailing list
integration-dev@...
https://lists.opendaylight.org/mailman/listinfo/integration-dev




Join {z.archive.ovsdb-dev@lists.opendaylight.org to automatically receive all group messages.