54e79eafa0
The console page is currently based on the ListView from PF3. The
most direct conversion to PF4 is a DataList, which is similar but
different.
This is intended to be a like-for-like replacement of the console page
using the DataList model.
The things I have explicitly thought about:
* The trusted flag on the playbook remains with tooltip
* The task line output is the same order, with
task <+>- (STATUS) [hosts] <time>
The magnifying glass and status share a cell to keep them close
* You can click on either the magnifying glass or the status to bring
up the modal with the full task status. Both have a tooltip.
* The status and hosts are modified to use PF4 label and chip models
for a standard look.
* Plays start rolled up, but tasks start in the expanded state as
before.
* If there is a failed task, the playbook and play are unrolled to
show it automatically as before.
* "run" playbooks are expanded by default
* Tasks highlight on hover, but now using a light boxshadow rather
than background color which is more consistent with other parts of
the ui (like the build table, for example).
* No colours in the background of the playbook rows; the DataList now
has a blue line that runs down the side showing you the groupings
when a playbook row is opened. I think this is more consistent
with "less is more" type approach.
* deep-link permalinks on the modal display of the task results open
up the same task display when pasted into a new window.
While I think there is plenty of room for improvement in the way this
information is displayed, I've deliberately tried to keep everything
the same in this changeset to a) ease review and b) so we have a
PF4-based grounding to work from. There wasn't really a way to do
this more incrementally; although almost everything moves around there
is no tricky code to call out -- some fiddling of things that needed
to state properties and some toggle javascript-code bits are the main
additions.
Change-Id: Ie480deb046502879542e41844e919a362203e25d
Zuul
Zuul is a project gating system.
The latest documentation for Zuul v3 is published at: https://zuul-ci.org/docs/zuul/
If you are looking for the Edge routing service named Zuul that is related to Netflix, it can be found here: https://github.com/Netflix/zuul
If you are looking for the Javascript testing tool named Zuul, it can be found here: https://github.com/defunctzombie/zuul
Getting Help
There are two Zuul-related mailing lists:
- zuul-announce
-
A low-traffic announcement-only list to which every Zuul operator or power-user should subscribe.
- zuul-discuss
-
General discussion about Zuul, including questions about how to use it, and future development.
You will also find Zuul developers in the #zuul channel on Freenode IRC.
Contributing
To browse the latest code, see: https://opendev.org/zuul/zuul To clone the latest code, use git clone https://opendev.org/zuul/zuul
Bugs are handled at: https://storyboard.openstack.org/#!/project/zuul/zuul
Suspected security vulnerabilities are most appreciated if first reported privately following any of the supported mechanisms described at https://zuul-ci.org/docs/zuul/user/vulnerabilities.html
Code reviews are handled by gerrit at https://review.opendev.org
After creating a Gerrit account, use git review to submit patches. Example:
# Do your commits
$ git review
# Enter your username if promptedJoin #zuul on Freenode to discuss development or usage.
License
Zuul is free software. Most of Zuul is licensed under the Apache License, version 2.0. Some parts of Zuul are licensed under the General Public License, version 3.0. Please see the license headers at the tops of individual source files.
Python Version Support
Zuul requires Python 3. It does not support Python 2.
Since Zuul uses Ansible to drive CI jobs, Zuul can run tests anywhere Ansible can, including Python 2 environments.