On 2016-06-30 16:26, Mark Waite wrote:
That sounds good to me.  Simplifying that page will be a good thing.

I've constructed a series of Docker images which contain bug
verification jobs that are interesting to the git plugin.  Currently it
includes 72 jobs that verify specific bugs have not been reintroduced,
with an additional 20+ jobs verifying various forms of authentication to
interesting git service providers like GitHub, BitBucket, Gitlab, and
Assembla.

Are you interested in links to the verification Docker definitions (for
those images that I'm willing to share publicly)?

I've found it quite helpful to use a Jenkins job to confirm that a
specific git plugin bug is resolved.  It then allows me to run that same
condition on multiple platforms, with parallel execution (depending on
the number of slaves I have running), and has been helpful discovering
unexpected surprises in my configurations and in those tests.

Mark Waite

It is good to hear you still look at the LTS RCs, for sure. I would love if your work ware living and running somewhere publicly so people can contribute and see the results. Though it seems you approach is fundamentally different than the one used by ATH and project infra is not ready to run docker containers (unless that has changes recently).

As a minimum, please consolidate the path of the wiki page that refers to git plugin to something that makes sense w.r.t. what you tests. Also, I really miss your green +1 in there so feel free to have just one item on the page but please, let us know the tests are passing at your end.

Thanks
--
oliver

--
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].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/2d6b022a-6b11-05ee-1fec-b48a482d1503%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to