This commit adds a new job filter to the gearman client to filter
based on the build queue. This is used for the subunit jobs which
we don't want to run on check jobs.
Change-Id: If81fe98d8d67bb718c53a963695a7d06f5f6625d
The policy for the subunit workers expected a subunit yaml file named:
jenkins-subunit-worker.yaml however the filename had a typo which
prevented things from working. This patch fixes the filename.
Change-Id: I0638f1dcb18561580351959cb29ef2546850450f
the following css attribute selector will make -1s in the english
ui version of gerrit new screen be the color red. This is as good
as we can do today given that gerrit doesn't provide real classes
on things any more.
Reference on attr selectors: http://css-tricks.com/attribute-selectors/
(should work on all browsers > ie6)
A follow up will be to see if we can get proper semantic tags back
into gerrit for things like this.
Change-Id: I8236cf83b648bfe352daea1f3ae59c151068ab44
Use the same trick used in zuul status page to store a cookie
with the last state so when we load another review, we use the last
setting to show or hide the CI comments.
Change-Id: If912b88c3ad68c1dcaa086ad76abb54ecf5b576b
This adds a new gearman worker to process the subunit files from
the gate job runs. It will use subunit2sql to connect to a sql
server and process the data from the subunit file. The
log-gearman-client is modified to allow for pushing subunit jobs
to gearman, and the worker model for processsing logs is borrowed
to process the subunit files.
Change-Id: I83103eb6afc22d91f916583c36c0e956c23a64b3
The previous hideci enhancements and refactor was not tested on the
new change screen, which sadly removes all the semantic markup around
the displayed changes (boo gerrit).
Do the base parsing based on the looping over the p tags as was done
in the initial version instead of matching divs by semantic tags. A
few of the parsing functions needs to be adapted to know if they are
on old vs. new change screen (like finding the date).
Spot tested locally with new and old change screen, seems to be
working.
Change-Id: Ieadfb78fa4d152d12cb64fc69d808fa510d28abd
The OpenStack infrastructure's PyPI mirror (pypi.openstack.org) shouldn't
be used for 3rd parties so setting the default to pypi.dfw.openstack.org
instead.
Change-Id: I7720ad7d3b23816c63e971112a3a733bde52b7f4
Change hideci to only show the most recent results of a pipeline. For
entries where the pipeline is not parsable we default to assuming the
results were in the 'check' pipeline.
3rd Party CI systems are assumed to be 'check' pipeline for the
purposes of this patch.
Order the display of these results for parsed pipeline entries first,
then non parsed entries after. That has the impact of making all the
Jenkins results be the top of the page and 3rd Party come later.
Also provide a (### rechecks) comment if we find more than 1 result at
the current patch set number. This helps reviewers understand that
this patch might be unstable as it's been rechecked to get to the
current state.
Change-Id: I153f73000f9392af6c8bbe850716645b3ba836a0
Move the install location of the git checkout of the config repo
to /opt/system-config to make things more consistent for operators.
Actually moving this on the puppetmaster will be a manual step.
Change-Id: Id9297088ae6c76c02e35414433aae2733f9f639c
We are renaming the openstack-infra/config repo to
openstack-infra/system-config. This patch changes the paths in
the tempest help files.
Change-Id: I5edb3e444b554a979d9274b7354ddd8c1b4b9128
We are renaming the openstack-infra/config repo to
openstack-infra/system-config. This patch edits the paths in the pypi.yaml
files to reflect the name change.
Change-Id: I40e417d31803d8e47e1558b7783e7216119e898d
However the help message didn't update, so it's harder to find
the source files. This fixes the help urls presented to the user.
Change-Id: I641cee0fe8494ad7ee712b4884e6767cc6ed15e2
This is a refactors the hideci code into much smaller functions,
making the whole thing a bit more readable for fixing this going
forward. This was done in order to add a couple of new features. The
smaller functions should also make this code much easier to review.
After the refactor we now do a top down parsing of all comments in a
review, classifying them as 'is_ci' and 'is_trusted_ci' so that we can
more easily compute the results we want going forward.
In the process a few additional features were added.
1) CI results are only shown for the latest patch set, even if no CI
system has reported on it. This is accomplished via
ci_latest_patchset.
2) If CI system is in merge conflict, that's displayed in the results
box.
3) Test results records are lifted in total to the test results
display panel, and each set of test results includes the date that we
got it from. This means that for patches that get 'rechecked' a lot,
you'll see the whole history of test results on current patch. You
will also be able to quickly realize that the current test results are
older than the last recheck comment.
The UX for part 3 is different, and may need tweaking going forward,
however the merge of results from different runs was creating a lot of
confusion to reviewers, so this errors on the side of more clarity.
Because of the largely inconvenient workflow for development (the fact
that you basically need to copy / paste function definitions into
chrome dev console) this isn't broken up as smaller patches. This
should, hopefully, make future patches much easier on this code
though.
Change-Id: I3f128a449756fd6988f3810863cd1d49c476b0dd
Fix all of the bashate failures. Also, bashate will install its negative
tests in its virtualenv, so we need to generate a list of files to pass to
bashate that excludes .tox/
Change-Id: I55559bf6137f705aec9a7f277928ad8d4cadc2ca
The file zuul/layout-dev.yaml was moved to the project-config repo.
This copy of the file in config should have been deleted with the
others in commit 1e7874e1eb0c15adc06d0bd10da5a90a26901309 and it
wasn't. There have been no updates to this file since August 5,
2014. This patch deletes zuul/layout-dev.yaml.
Change-Id: I4d6729d289b00b3ce05aa98f27d275b5093b9f00
Content from the config repo was split into a new repo,
project-config. This patch deletes the moved content from the
config repo.
Change-Id: Ifa1ae2cb7c23ae48f388b7d57a4c0d0799ef1dc2
Story: 167
This patch creates a new repo, openstack-infra/project-config.
This is the first step in the work items to impliment the
spec config-repo-split.
Change-Id: Ibd17035f69501104038d2ec8de0c6e857844cc0e
Story: 167
The group annotation was initially created with the assumption that a
project would be assigned to a single group. Storyboard now supports
multiple project group membership, so the config file needs to be
updated accordingly.
Do not merge before https://review.openstack.org/#/c/111814/
Change-Id: I1b11b6eee7b071592b052d9bbc5b874e49e2ef77
Flame is an automatic Heat template generator, for a dedicated tenant.
The project is currently available on github:
https://github.com/cloudwatt/flame
Change-Id: I188640ff322c996253c48c91849e3952b4f11c77
