Avineet, This question could strike up a good deal of debate on what skills are necessary to design, deploy, and support Jenkins - but I'll risk putting in my 2 cents. Development experience is a plus, but not required (although your software engineers will definitely be stake-holders for the lifecycle of this system). A moderate level of systems administration experience is necessary. Depending on what you're using the tool for, the skill sets necessary branch out from there. You'll want someone that understands the existing build system well enough to adapt it to use Jenkins. Java development experience isn't a must, but for debugging complex issues it's definitely a plus.
This is woefully generic and under-specified, but it should provide you an idea of who can support a Jenkins deployment. -Kenny On Tuesday, April 30, 2013 2:44:47 AM UTC-7, avineet wrote: > > Thanks Kenny, > What would be the skill set required/effort required to work on the tool. > Example: > Any Java developer or tester or any pre requisite. > > > > > On Sat, Apr 27, 2013 at 4:35 AM, Kenny Ayers > <[email protected]<javascript:> > > wrote: > >> Hey avineet, >> >> The procurement cost of Jenkins is free. The real cost will be in >> implementation and development man hours by your build person (or team). >> As far as your use-cases go, it's up to your build person or team to >> implement the functionality using the Jenkins toolset. >> >> If you don't have anyone in-house that can answer those questions on >> feasibility, it's probably time for a new hire. >> >> Good luck, >> >> Kenny >> >> >> On Friday, April 26, 2013 3:05:18 AM UTC-7, avineet wrote: >>> >>> Hi, >>> We wanted to implement Jenkin in our project which require some kind of >>> automation tool which support testing around Abnitio. >>> I have heard that Jenkin works with Abnitio,Could you please confirm me >>> the same. >>> *What would be the Procurement cost of the product. >>> * >>> Also,I drafted few high level cases which we want the tool should >>> support.Could anyone please have a look and let me know if these cases >>> works with Jenkin. >>> >>> Compare input and output record counts >>> Compare input values and output values >>> Validates transformations >>> Compares checksums created against the input and output (e.g. The >>> sum of input column 1 = sum of output column 1) >>> Compare input with a filter record count with output record count >>> Supports files and tables as either the input or output (File to >>> Table, Table to Table, Table to File) >>> Supports the validation of a test against a static value, e.g. Sum >>> of column 1 = value x >>> Supports embedded SQL to use for the validation routine, e.g. Output >>> of SQL 1 is equal to the output of SQL 2 or Output of SQL 1 is equal to >>> this >> >> -- >> 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 [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Thanks and Regards.. > Avineet > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
