Skip to content

Created a "TAP Test History" page which shows the status of multiple tests over previous builds.#11

Open
evandy0 wants to merge 11 commits into
jenkinsci:masterfrom
evandy0:TAP_Analysis
Open

Created a "TAP Test History" page which shows the status of multiple tests over previous builds.#11
evandy0 wants to merge 11 commits into
jenkinsci:masterfrom
evandy0:TAP_Analysis

Conversation

@evandy0

@evandy0 evandy0 commented May 15, 2016

Copy link
Copy Markdown

Tested with matrix plugin and tap configs with some built/unbuilt.

@evandy0

evandy0 commented May 15, 2016

Copy link
Copy Markdown
Author

Partially addresses JENKINS-34820.

@evandy0

evandy0 commented May 15, 2016

Copy link
Copy Markdown
Author

screen shot 2016-05-15 at 12 30 36 pm

@evandy0

evandy0 commented May 15, 2016

Copy link
Copy Markdown
Author

Still looking into showing latest test failures on the project page, but this is (at least) better.

@kinow

kinow commented May 18, 2016

Copy link
Copy Markdown
Member

Was going to review this pr today too, but indeed this will take a bit more of time. Sorry, will try to review it this weekend.

@evandy0

evandy0 commented May 19, 2016

Copy link
Copy Markdown
Author

I'd say I was surprised... but I'm not. Take your time; let me know what you find. Definitely interested in learning.

@evandy0

evandy0 commented Aug 30, 2016

Copy link
Copy Markdown
Author

Bruno, and update on getting this merged into your new 2.0 plugin architecture? We were looking to update, but it appears that this feature has not been delivered yet.

Thanks.

@kinow

kinow commented Aug 30, 2016

Copy link
Copy Markdown
Member

Not yet @evandy0, tried to fix the low hanging issues, and am now debugging memory problems before jumping into new features.

The only issue I think I'll fix while profiling the plugin, is https://issues.jenkins-ci.org/browse/JENKINS-19262, regarding graphs, as this was another easy to fix.

Once the profiling is done, I expect to have changed a few internal classes, but will try to merge pending pull requests myself, thus not having to bother you to update all your work :-) though I may have to ask for help if there are too many changes.

@kinow

kinow commented Aug 30, 2016

Copy link
Copy Markdown
Member

A 2.1 version should be released in the next days, with the performance enhancements, hopefully. Then will start working on 2.1.1, where we could include your code 👍

@evandy0

evandy0 commented Aug 30, 2016

Copy link
Copy Markdown
Author

Thanks for the update; I appreciate it. I’ll keep my eyes pealed!

—Evan

On Aug 30, 2016, at 5:00 PM, Bruno P. Kinoshita notifications@github.com wrote:

A 2.1 version should be released in the next days, with the performance enhancements, hopefully. Then will start working on 2.1.1, where we could include your code 👍


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #11 (comment), or mute the thread https://github.com/notifications/unsubscribe-auth/AMMk18TYramDbkYyaaee65UIxwVZ5Kjoks5qlKfygaJpZM4Ie4MY.

@drmmr763

Copy link
Copy Markdown

Just want to +1 this PR and encourage those of you who've worked on it, it would be super useful to have!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants