Re: Looking for specific functionalities in existing plugins
8 views
Skip to first unread message
Daniel Beck
Aug 17, 2015, 9:35:56 AM8/17/15
to jenkin...@googlegroups.com
You're on the wrong mailing list.
On 17.08.2015, at 15:17, Janez Novak <matic....@gmail.com> wrote:
> Hi,
>
> I'm working on a project to extend Jenkins' functionalities to serve certain goals, but before I start writing plugins from scratch I will of course look for these functionalities in existing plugins.
>
> Seeing as Jenkins seems to have more than a thousand available plugins, even narrowing my search to the fields I'm interested in leaves me (at first glance) with well over a hundred of them.
>
> Checking them all out will probably take a few days and I'm sure I'll miss one or two things while going through them.
>
> In order to make this process faster and ensure I don't miss anything, I'd like to ask you to read the functionalities I'd like to see Jenkins users have at their disposal, and if you know a plugin which provides at least one of these functionalities at least partially, please tell me the name of the plugin.
>
> The functionalities I'm looking for are as follows:
>
>
>
> - CI_TOOLS MUST record the results of each test, mapping them to the version number.
>
> - QTESTING_TOOLS MUST test the application for efficiency and reliability.
>
> - QTESTING_TOOLS MUST provide the test outcome: success or failure, and the result
> MUST be independent of any other test runs.
> - When running Continuous Integration, the tests need to indicate if they encountered an error, an invalid application state or violation of the set quality constraints. The
> QTESTING_TOOLS will perform many tests of varying parameters, and each result has to be independent
>
> - DEPLOYMENT_TOOLS MUST be able to run automatically and autonomically.
> - Manual interventions into the deployment process are not trackable, and reduce control and repeatability of the deployment process. A recommended pattern is to use automatic
> and autonomic tools.
>
> - DEPLOYMENT_TOOLS MUST be able to deploy and install any application and the related monitoring tools from a valid topology of the supported DICE building blocks.
> - DICE will support an essential set of building blocks able to support the selected use cases. The deployment tools will make this support effective
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5cc55c1a-9928-4462-a507-4886baccab03%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
On 17.08.2015, at 15:17, Janez Novak <matic....@gmail.com> wrote:
> Hi,
>
> I'm working on a project to extend Jenkins' functionalities to serve certain goals, but before I start writing plugins from scratch I will of course look for these functionalities in existing plugins.
>
> Seeing as Jenkins seems to have more than a thousand available plugins, even narrowing my search to the fields I'm interested in leaves me (at first glance) with well over a hundred of them.
>
> Checking them all out will probably take a few days and I'm sure I'll miss one or two things while going through them.
>
> In order to make this process faster and ensure I don't miss anything, I'd like to ask you to read the functionalities I'd like to see Jenkins users have at their disposal, and if you know a plugin which provides at least one of these functionalities at least partially, please tell me the name of the plugin.
>
> The functionalities I'm looking for are as follows:
>
>
>
> - CI_TOOLS MUST record the results of each test, mapping them to the version number.
>
> - QTESTING_TOOLS MUST test the application for efficiency and reliability.
>
> - QTESTING_TOOLS MUST provide the test outcome: success or failure, and the result
> MUST be independent of any other test runs.
> - When running Continuous Integration, the tests need to indicate if they encountered an error, an invalid application state or violation of the set quality constraints. The
> QTESTING_TOOLS will perform many tests of varying parameters, and each result has to be independent
>
> - DEPLOYMENT_TOOLS MUST be able to run automatically and autonomically.
> - Manual interventions into the deployment process are not trackable, and reduce control and repeatability of the deployment process. A recommended pattern is to use automatic
> and autonomic tools.
>
> - DEPLOYMENT_TOOLS MUST be able to deploy and install any application and the related monitoring tools from a valid topology of the supported DICE building blocks.
> - DICE will support an essential set of building blocks able to support the selected use cases. The deployment tools will make this support effective
>
> --
> You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5cc55c1a-9928-4462-a507-4886baccab03%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages