Age | Commit message (Collapse) | Author | Files | Lines |
|
In order to support additonal features that have been added to
collectd since the 5.8 release, there needs to be a separate
stable and master container so we can support the new features
as well as the stable release.
This change will allow us to increment the version of collectd
as we add functest support, config guides and documentation,
while keeping the stable version container intact and available
for users to download.
JIRA: BAROMETER-102
Change-Id: I06ca84581a2e0f1a994cedf53aebc8f5cc3e7535
Signed-off-by: Emma Foley <emma.l.foley@intel.com>
|
|
|
|
Basically we are getting blocked on merging patches due to ODL breaking
and these patches have nothing to do with ODL. So we are changing the
default sceanrio to just be nosdn, and then if the change is relatd to
ODL we can include an ODL gate run.
Change-Id: I61ec224e62e6f3cb6ee40696326bf243788c27d6
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I2946684b8e5941201865c123793b7f5800b5421b
Signed-off-by: Michael Polenchuk <mpolenchuk@mirantis.com>
|
|
This is the patchset of projects that did not fill out their
releases fraser file.
I have done it for them.
some of the projects had no changes on the fraser branch
in this case I put the tag in the same place as the 6.0.0 tag
some project I am familliar with and I move the tag to the
head of fraser for them,
Ideally team leads will do this work in the future
We will update the tagging instructions accordingly.
Change-Id: I1b2c7a8b6e63bc857192757e25f2d103c2629319
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
|
|
master commit to use for 6.1.0:
b718a43380376d2b19222c4203c97a95ca849ae8
(note: opnfv-6.1.0 tag: 553ea71b7aa2eb7d9ff46316de367dff0844ce42)
(can/should a tag objet ID be used for a point release ?)
updated stable/fraser SHA1, to same SHA1 that was used for 6.0.0
(i.e. 3a957a75f99686767d13f45d74b5ca8463559b7b)
(I assume stable/fraser SHA1 should be the same as 6.0.0 SHA1 ?)
>The stable ref is the ref when the branch was created, it should not
>change
(cherry-picking for stable/fraser is not possible after 6.0.0 is
released)
>You can cherry pick as long as you want.
Change-Id: I887174801a56b374cae0197b31561673bc0435ea
Signed-off-by: Gerard Damm <gerard.damm@wipro.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit dc4b9d1ad316e9055ccb3767c4572ad22cbe43a5.
Change-Id: I3bec4ef84dcb7e56d80b4df78b487f7caa931f3e
|
|
This script is tested, and should now be allowed to create tags.
Change-Id: Ia87341c9cb6397700442a11c38d502fed8dd4743
Signed-off-by: Aric Gardner <agardner@linuxfoundation.org>
|
|
Change-Id: I7ec0b1d9b40d12500eaf0f82e2e8035c488d1437
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
|
|
Updates the releases verify and merge jobs to check release files for
the following:
- commits exist
- commits are on stable-branch
If both of these criteria are met and the patch is merged, the repos
will be tagged at the specified commits and pushed.
If a repo has already been tagged but not on stable-branch the job will
not exit, but will warn that the commit doesn't exist on the correct
branch. This is because tags should never be removed.
This adds an additional script 'repos.py' that provides an quick
interface for pulling out information from release files, along with the
script 'release-status.sh' for checking the status of tags.
NOTE: The branch creation script has been disabled until it can be reworked.
Change-Id: I498bc74f20aa50d2bd321771f20a77905b246399
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
JIRA:-
fix 3 neutron trunk testcases failure in functest
Change-Id: Ie3cd55c3aac1b6e1104054b3ab666056efa83b5b
Signed-off-by: chigang <chigang@huawei.com>
|
|
Change-Id: I885f40ca8ac1c076b8443f03ca99a975d4edc82e
Signed-off-by: Stephen Wong <stephen.kf.wong@gmail.com>
|
|
Change-Id: Ibdb9bba605fd7deccf184010085cb14cc2805b59
|
|
Change-Id: Ife8ee87db45381678c44ebd80adf08658bd697f5
Signed-off-by: Ross Brattain <ross.b.brattain@intel.com>
|
|
Change-Id: Ib59491210da3996fe59885635481b22fd84d1af2
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Changes-Include:
- Use 2 computes as required by ODL team
- Get rid of checking JOB_NAME var for csit, and simply check if
PROMOTE var is True
- Pass PROMOTE all the way from top-down into deploy job
- Use CSIT network settings file when deploying CSIT
Change-Id: I56d953516ce690749634b474e553baad3a762364
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I1282caa29b6c2a1fe67ec80f090a0acc1d4f24ce
Signed-off-by: Manuel Buil <mbuil@suse.com>
|
|
|
|
|
|
Change-Id: I274dba9398ef549d20fa106eda88abebfbf48c9e
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This job already does deploy and test, so just use that rather than
triggering seperate jobs.
Change-Id: Ie62088f434de93ebb7638ba4d4ef8791ac01aa1f
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I6312e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Deepak S <deepak.s@linux.intel.com>
|
|
Change-Id: Iea3269a25e88790d335456508ad0de904ed4706e
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
|
|
Change-Id: I5212e57c689519bdf65a562db85acfb343ac7b68
Signed-off-by: Bin Hu <bh526r@att.com>
|
|
Change-Id: Ie2d0a730801bc7f5bb784ee90e60e8e30562ef47
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Promotion name for master OS should just be nofeature.
Change-Id: I60086e94bbef87a1754f4f2cc00d096454668ded
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
We still need VERSION_EXTENSION var to figure out which RPM files to
remove on the slave.
Change-Id: I03cc9c3318edec9860c8f3ffc01db52517a644b4
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
This fixes the two error types being output by a Sphinx docs build:
- numbered - This is already included in the root toctree
(docs/index.rst) and doesn't need to be repeated
- List spacing - Only in infra/jenkins/connect-to-jenkins.rst, the
enumerated list of steps was missing spaces after each item
Change-Id: I55555821a35a3d248f3a347e8e4d9c851254cf08
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: If1f9d8c961d976e21c5fd6354a712027a6591e96
Signed-off-by: Cédric Ollivier <cedric.ollivier@orange.com>
|
|
Change-Id: Ib09b9b919ca046532931fed551d7a6f7aa1857c1
Signed-off-by: Tomi Juvonen <tomi.juvonen@nokia.com>
|
|
Remove unnecessary arm-daily testsuite
arm-daily does not require special builder or parameter
changes
Increase job-timeout to fit both architectures
JIRA: FUNCTEST-917
Change-Id: Id31709740906fa9ea3918c8694d04fd88191f03f
Signed-off-by: Delia Popescu <delia.popescu@enea.com>
|
|
Now that we only build apex python rpm in master, we can afford to build
RPM everytime and ensure it builds correctly.
Change-Id: Ica1efe1cc2c3db0dfe1c5677b5ab47df121c0966
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
Change-Id: I881634a57f1d28cfcc3346476dc095873c014a22
Signed-off-by: Tim Rozet <trozet@redhat.com>
|
|
|
|
When manually triggering a docker job (or even through timed builds),
GERRIT_EVENT_TYPE will not get set. This does gets set when the job is
triggered by a Gerrit event (ex: ref-updated, comment-added).
Specifying the variable lookup to default to nothing (ex: "${FOO:-}")
should allow non-Gerrit triggered jobs to complete successfully.
Change-Id: Ic1ba8ebef0967b0f20a2d6385ce0e0b4876901dc
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
This is a temporary update until a new release of Global-JJB comes out.
Updating Global-JJB to a commit on master past 0.19.2 which allows
jjb jobs to run on the same builder without tripping over each other.
The related Gerrit change for the current tip of master can be seen
here: https://gerrit.linuxfoundation.org/infra/#/c/10717/
Change-Id: I4205fc74d8af805ac29ac93d4c5b033c145a00b9
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I62095327781153eaff81999f5f3fdddc652dc550
Signed-off-by: Fatih Degirmenci <fdegir@gmail.com>
|