Jenn,
We do not test with a CI strategy. We have a limited number things that we
do with some parallelization.
1. clone or merge
2. in parallel
a. build product for (window (32, 64), linux (32, 64))
b. run many different types of tests
c. generate report on tests
3. generate consolidated reports
Currently I have a different pipeline for many of the preferred
configurations we want our developers to use.
I want to be able to allow my developers to select from all of the
available options.
I could put all of these options in 1 pipeline and have if conditions at
every decision point.
This maybe challenging to get perfect with the diff parallels it would have.
I thought it would be powerful to pass a generated script based on
available choices to a generic pipeline job.
I could then handle all of the complex logic outside of the groovy script.
This logic could be unit tested and in revision control.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/73f6c726-82aa-4d25-8e8b-c0cbd768385a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
