bregman-arie / rhoci Goto Github PK

Don't specify them with the configuration file

run the dashboard process as a systemd service for easier maintenance + systemd caring about it during crashes

• Color based on status
• Class name and test name
• Add average duration

Support not only bugzilla and launchpad but basically every URL provided by the user.

Users asked to add EOL information for each release in the main page

Display how many many tests and builds passed in a given range of dates.
For example:

• Number of builds failed this week
• Number of tests passed this month

• Number of failed builds
• Number of passed builds

It's much nicer to know what version of a specific plugin is installed

This was pointed out mainly by new users - it would be nice to know what is each phase from the dashboard by having a balloon tip right to the phase name

Hi,
It will be great to have a different color for disabled jobs.
And also maybe add a legend with the meaning of the colors.

Thanks

For some reason, people are copying jobs between Jenkins instances which causing other Jenkins instances to send notifications to the dashboard.
To solve this, I will match between request remote address source and the Jenkins provided by the user with RHOCI configuration.

There are too many 500 internal server errors right. Shame!

Currently the filtering is applied on the client without storing information about selected sorting and filters in the URLS.

As a result of this, when I copy-paste my url and send it to somebody else, they will see a very different page than mine.

Example /dfg/Storage, now click on reds for rhos 11. You will see some but the URL remains the same. If you refresh the page, you loose the filter.

Any applied filter should be save using anchor part of the url, that's the correct HTML way of storing information for the client.

One possible example is /dfg/Storage#status=failed&version=11, but in the end you can pick any approach for storing the filter in the anchor (part after the hash sign).

By doing this you can assure that copy/pasting the URL will provide same view.

Note: work with Michal on that

To quickly reach the full information on Jenkins.

This request came from many who would like to see what changes were made each new version.

Should be simply a page with a list of changes.

Should be useful for removing "junk" jobs :)

Some columns in the bugs datatable should be hyperlink to the bug itself in the original system

Opening this on behalf of Assaf:

Clicking in each row on 'bugs' button to see the bugs and who handles them is not optimal.
If possible, let's include bug assignee and status directly in current datatables.

RHOS versions should be listed in DESC order, not ASC because most important ones are the newer ones, not the older ones.

Also the default width of the piechart does wrap allow only for 6 our of the 7 version on one raw, even if browser is full screen (1280 width). There is a lot of wasted panning space which could be eliminated on order to assure that we fit 7 columns by default.

These two issues create a less than ideal user experience because RHOS 11 and RHOS 12 do endup on different rows. Maybe changing the default order should be enough for the moment, because RHOS 6 would end-up on different raw, which is not a big deal.

In DB tables and in the datatable

This requested by managers and developers.

Useful for those who use dashboard as monitoring tool in the background

Hi,
It can be nice to have a view of my favorite jobs.

Thanks

I think that the default pagination of 15 records is far too small for out usage and a value of 30 is likely to be much better.

Jira also happens to have a default pagination of 30. To be hones any value starting with 30 should be ok. Even if you make it 50 or 100, I would be happy.

Having a small pagination did confused me because I got the impression that there were no other records, especially because the quick filter applies to the current page.

Sorting column by result is not good enough since you'll see either regression or failed but not both. Add quick filtering buttons.

Despite the fact that "Timeout waiting for the server" is present in rhoci/common/failures.py +119,
the failure is not reflected in "Last build status" column (showing "Unknown" ATM).

Got this request from at least three different teams so I guess it should be a high priority? :D

if you use nova-unit-compute it will find novaclient

Cards are not effective. It's much better when you can actually filter and sort the data.

In every build row, introduce a button for quick builds comparison.
So if build #3 failed, have a button to compare it with another build quickly.

This way, users don't need to enter job name and two builds to compare. Just the build to compare with the chosen build in the table.

Can be used for component statistics.

Components for example: neutron, nova, ...

Move any snippet that interacts with Jenkins to Pykins since it will handle it much better than how I do it with RHOCI at the moment

Inspect component CI configuration in octairo by specifying component name and release