On Fri, Aug 5, 2016 at 2:04 PM Jesse Glick <[email protected]> wrote:

> On Fri, Aug 5, 2016 at 7:57 AM, Mark Waite <[email protected]>
> wrote:
> > The git client plugin (1.19.7 and
> > it predecessors) matches the situation you describe (old Jenkins
> baseline,
> > not recent release, does not compile without changes against current
> core).
>
> Why exactly does it not compile against current core? If SECURITY-144,
> just update to 1.580.1, which is quite old by now.
>
>
The changes required to compile against current core include:

- change jenkins.MasterToSlaveFileCallable<GitClient> to
FileCallable<GitClient>
- add checkRoles(RoleChecker) to HudsonTestCase

My recollection (when I did that investigation many months ago) is that
those changes came in one or more of the 1.6xx versions.  I was not ready
to move the git client plugin dependency forward to 1.6xx at that time
without a major version number change.

If I were making a major version change, I wanted other benefits (like
dropping support for Java 6, switching to JGit 4, using try with resources,
etc.).  That's what is being prepared in the git client plugin 2.0.0-beta
branch, and what I hope to release in time for Jenkins World in September.

Mark Waite


> --
> 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/CANfRfr1JY-9OaYoUUhmNWiUMvOO5v_xkq_NW6Bkkd2KoT7REgg%40mail.gmail.com
> .
> For more options, visit 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/CAO49JtHrh%2BNEPi2KBQ%3Dv0ELJCyOc9XZ%2BEXc-pp%3Dr6xrMdfVihQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to