Most of them are offered as a service. Kraken CI is an on-premise solution. Beside of that it is focused on testing. When you have thousands of test cases and there is never 100% pass ratio then it is hard to spot regressions or unstable tests (eg. Jenkins does not have good support for such things). All of that and more is present in Kraken CI out of the box. There is much more, hard to list all. Please, check Kraken CI web page and its docs or contact me directly (mike@kraken.ci) or chat here :)
Thanks for reply. Thousands of test cases? It should be very specific development imho. And even in this case I am not sure what certain problem you are trying to solve here? I guess most of test frameworks provides a user with some sort of reports? Or I miss the point here ...
Medium and big projects can have 10k, 100k or even more test cases. But even for 1k if there is hard to achieve 100% then it is hard to track changes of results over time. E.g. can you say which tests are the least stable in the last month so that you could fix or disable them? Or could you say which tests started failing during the last week? Or if you have some performance tests, lots of them, then which of them degraded? I think that it is very hard to get answers for such questions in Jenkins. I was writing some scripts to do such analysis and generate some reports using Jenkins API but this is a dead end. In the past I wrote similar testing system to Kraken but it was proprietary and it was used only internally. Kraken is an open source version of the concepts that emerged in the original system.
Ok. I get you, thanks for clarification. You might be then interested in tool, I've created - Tomty and see how it deals with tests subgroups - dev.to/melezhik/write-devopsish-te... , see tags section.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi. Nice posts on Kraken, thanks. However what is a pros over already existing (billions) ci/cd solutions ?
Most of them are offered as a service. Kraken CI is an on-premise solution. Beside of that it is focused on testing. When you have thousands of test cases and there is never 100% pass ratio then it is hard to spot regressions or unstable tests (eg. Jenkins does not have good support for such things). All of that and more is present in Kraken CI out of the box. There is much more, hard to list all. Please, check Kraken CI web page and its docs or contact me directly (mike@kraken.ci) or chat here :)
Thanks for reply. Thousands of test cases? It should be very specific development imho. And even in this case I am not sure what certain problem you are trying to solve here? I guess most of test frameworks provides a user with some sort of reports? Or I miss the point here ...
Medium and big projects can have 10k, 100k or even more test cases. But even for 1k if there is hard to achieve 100% then it is hard to track changes of results over time. E.g. can you say which tests are the least stable in the last month so that you could fix or disable them? Or could you say which tests started failing during the last week? Or if you have some performance tests, lots of them, then which of them degraded? I think that it is very hard to get answers for such questions in Jenkins. I was writing some scripts to do such analysis and generate some reports using Jenkins API but this is a dead end. In the past I wrote similar testing system to Kraken but it was proprietary and it was used only internally. Kraken is an open source version of the concepts that emerged in the original system.
Ok. I get you, thanks for clarification. You might be then interested in tool, I've created - Tomty and see how it deals with tests subgroups - dev.to/melezhik/write-devopsish-te... , see tags section.