The original thought - to use the build to separately upload
config.json for our CORS draft build - didn't work because
of lack of path munging control. Instead we've declared a
separate build target called 'build:draft' that compiles an
appropriate client, which can then be uploaded in one go.
Change-Id: I16ad8fd8b90aca93929e68ef3033715e0666795b
Code is being ported to python so setup the python build jobs
We are currently working on the necessary files for the build so there is no
need to wait for them to show before making this change
Change-Id: I879715f5d9e08f28f97a01b0f16b8d3faf4ce9a7
The ironic sideways grenade tests are no functional and passing.
This moves it out of experimental and promotes it to a non-voting
check job on the relevant projects.
Change-Id: Ia44831955e6e921424278c5f342b961efa9d772a
Currently, when running functional tests for OSC, we try to run
a tox job. It automatically fails because the user running tox does
not have sufficient permission to run the tests.
Suggest just running a single script file that OSC maintains, rather
than having to change infra resources every time something changes.
Change to add functional tests for OSC is here:
https://review.openstack.org/#/c/122605/
Change-Id: I8543db1c2ecbb6f78eb831ebc9ea1a03625e3542
Remove the jobs that run the unit tests for projects that consume
oslotest. We don't need to gate every change on these tests.
Change-Id: I78ebee3017ce0c36645eceb5a40dc6b9bef54ce8
With CORS support in the API, and custom configuration loading in the
webclient, we can now let our js-draft build connect to a live API and
function like a regular client. This change makes the assumption that
any javascript project will include static docs-draft assets in the
$PROJECT_ROOT/test/draft directory, which will be uploaded as-is to the
same destination as the draft build.
Depends on: https://review.openstack.org/#/c/124201
Change-Id: Ia68f1f5e13098faac9e94c9655cf4bd8aaceb02b
Since puppet 3.x, Puppet Labs Forge accept only the metadata.json file
for module description (Modulefile is now deprecated). Our puppet-lint
jobs use the Modulefile to determine module name; this patch keep the «
retro-compat. » with Modulefile, but fetch the module name in
metadata.json file if available.
Change-Id: I1738ee14706d136837b2c8fe4ffa741907291bb8
The TESTR_FULL option was added back when tempest was running by
default with nosestests serially to test using testr in parallel.
However, this migration happened >1yr ago and the testr-full job is
just a duplicate of the regular full now. This commit removes all uses
of it from job definitions.
Change-Id: I8af1b4bc0623e89786b34359c6e75aacb21b91ab
Builder's parameters should not be on the same level as builder.
Otherwise bash script will be generated with errors.
Change-Id: I5816f41f54d5506f0cbe72ffbd1271d2834d0864
Test packages are required for successful install of MySQL-python.
This change should fix the job check-heat-dsvm-functional
Change-Id: Ib9f8c98e34c62f15dec182671390d21750110e38
There were some jenkins jobs that test project-config that needed
their names updated. This patch renames jobs that started with
config or gate-config to project-config or gate-project-config.
Change-Id: I107b7830a9b5c7d0bb526742a5f35bf662faccd2
Due to the fact that we had to freeze config in order to filter
branch it as the seed repo for the creation of the project-config
repo, the patch that created project-config in config landed
after the filter branch. So the information about project-config
itself is not currently in project-config. This patch addresses
the situation.
Backport of: https://review.openstack.org/#/c/121650/15
Change-Id: I669fb70f2dabb57300e0e7cdddc49e16b7e67d47
This repo was created from filter branching the openstack-infra/
config repo. This process brought a lot of cruft with it in the
form of directories that we no longer need. This patch removes
that cruft so we begin with a tidier repo.
Change-Id: Ibffad1b11c0c5f84eedfb0365369f60c4961a0f3