Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tasty-1.2 support #2

Open
nomeata opened this issue Feb 2, 2021 · 4 comments
Open

Tasty-1.2 support #2

nomeata opened this issue Feb 2, 2021 · 4 comments

Comments

@nomeata
Copy link

nomeata commented Feb 2, 2021

I’d like to use your reporter, but I get

[__2] rejecting: tasty-1.2.3 (conflict: tasty-jenkins-xml => tasty>=0.11.2 &&
<0.12)

Do you still plan to maintian this library?

@nomeata
Copy link
Author

nomeata commented Feb 2, 2021

Maybe tasty-ant-xml is enough for me, though…

@liskin
Copy link
Owner

liskin commented Feb 2, 2021

If you don't need --exit-success which exits with exitSuccess when the xml test report was produced correctly, so that Jenkins can then distinguish between failed (something went horribly wrong) and unstable (just some tests are failing), then tasty-ant-xml should be enough.

I haven't used this myself for a couple years (different job, language, CI, everything), but if anyone still needs it, I can definitely make it work with current version of tasty. Please do let me know if you want the additional functionality or whether tasty-ant-xml covers all your usecases.

@nomeata
Copy link
Author

nomeata commented Feb 2, 2021

Thanks, seems to cover my needs indeed :-)

@liskin
Copy link
Owner

liskin commented Feb 2, 2021

Okay, I'll leave this open so that if anyone else has this problem, they'll see that I'm alive and willing/able to fix this.

But I have a feeling most people just don't care about this level of detail. It's probably only useful at a certain scale where tracking of individual test breakages and/or execution failures starts to make sense, and at that scale there is usually a CI team who's able to hack something like this together in a couple hours anyway.

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

No branches or pull requests

2 participants