> Am 13.02.2017 um 20:39 schrieb Mark Waite <mark.earl.wa...@gmail.com>: > > I'd love to have students help create Jenkins jobs which illustrate specific > bugs in the git plugin, for example. Sample jobs which illustrate different > bugs as Jenkins jobs are available from the lts-with-plugins branch of my > docker repository. I've found it very powerful to have a Jenkins job per bug > report, either as a pipeline job (branch in a git repository like my > jenkins-bugs repository) or as a freestyle job which shows the bug and marks > itself unstable when the bug is detected. > > I hope to propose a blog posting describing the technique of using one or > more Jenkins job definitions for each bug. I've found it very helpful to > verify bugs remain fixed while detecting problems on multiple platforms.
That sounds interesting and would be a good basis. Do you think you can give some more pointers until the course starts (15. March)? A job per bug report is also a good working unit so we can start with a simple one and then move to more difficult setups. If there would be an example to start with it would be even better. What is not yet clear: these jobs you are referring to sound like a test setup for the ATH. So if you have such a setup it would be not much harder to add a verification step as an ATH test case. Then you will also have regression tests. Would that be also useful? In which order should we pick up issues? Priority in Jira? Or Newest first? > > Mark Waite > > On Mon, Feb 13, 2017 at 11:44 AM Victor Martinez > <victormartinezru...@gmail.com <mailto:victormartinezru...@gmail.com>> wrote: > Maybe it is a bit out of the scope and I don't know whether there is already > a ongoing testing framework for the pipeline. But, is it something feasible? > It might be a really good contribution to the community > Cheers > > -- > 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-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev%2bunsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/bf2dbfa0-c524-4673-bfb5-6e55c05de2d2%40googlegroups.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/bf2dbfa0-c524-4673-bfb5-6e55c05de2d2%40googlegroups.com>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. > > -- > 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-dev+unsubscr...@googlegroups.com > <mailto:jenkinsci-dev+unsubscr...@googlegroups.com>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFfBbcs16yghxjQHB58EF3%2B%3D3mUGOck1WK-EpQ_eaD17w%40mail.gmail.com > > <https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtFfBbcs16yghxjQHB58EF3%2B%3D3mUGOck1WK-EpQ_eaD17w%40mail.gmail.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/4F6F3DB6-1D43-4085-B54A-F4A6CCEE19E9%40gmail.com. For more options, visit https://groups.google.com/d/optout.
