Re: Is there a way i can use OpenJDK11 with Centos7 image?

[Martijn Verburg]

You may find one of the AdoptOpenJDK images a useful base point.

Cheers,
Martijn


On Fri, 10 Jul 2020 at 17:58, Slide  wrote:

> There is not a JDK11 CentOS image (PR's are welcome!). You could look at
> the current CentOS docker image Dockerfiles (see
> https://github.com/jenkinsci/docker) and build one based on that as a
> basis. If you get something working, a PR would be great so other people
> can use it as well.
>
> Regards,
>
> Alex
>
> On Fri, Jul 10, 2020 at 9:31 AM Ankush Sharma 
> wrote:
>
>> Hi,
>>
>> I tried hosting Jenkins with lts-jdk11 image. It worked fine at first.
>> But then there was need to install specific softwares which isn't
>> compatible with Debian 9 stretch on which lts-jdk11 image is based. Then i
>> tried lts-centos7 image and needed softwares are working fine but then all
>> my projects are java 11+ compatible, so all builds are failing now.
>>
>> Is there a centos7 with JDK11 image available, or is there any way i can
>> create my own image with centos7 jenkins installed on JDK11?
>>
>> Please help!!!
>>
>> --
>> 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 jenkinsci-users+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/8172926d-3d40-4e4e-94bf-a1054cd0c5dfo%40googlegroups.com
>> 
>> .
>>
>
>
> --
> Website: http://earl-of-code.com
>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVeqtUHqvOG8tKM11W2EBw%3DGZ%3D-HuLpWBx%2BAsRPdHCRR8Q%40mail.gmail.com
> 
> .
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAP7YuATmQHix9mTDBjXXy%2BD3pgKTy8tMNNoXi-60E_NFipweCw%40mail.gmail.com.

Re: Jenkins Upgrade

[Martijn Verburg]

Please note that AdoptOpenJDK produces both OpenJDK builds (i.e. HotSpot
JVM) and OpenJ9 + OpenJDK class library builds.

Cheers,
Martijn


On Thu, 12 Mar 2020 at 17:05, M.Madhusudana Reddy 
wrote:

> Thanks for the update Mark.
>
> I believe we tried with AdoptOpenJDK and ran into same issue but I will
> confirm that and let you know.
>
> Thanks
> M.Madhu
>
>
> On Thu, Mar 12, 2020 at 9:15 AM Mark Waite 
> wrote:
>
>> FYI IBM openJ9 is not supported by the Jenkins project.  Initial testing
>> has found no showstoppers, but IBM OpenJ9 introduces a very significant
>> difference between what you're running and what is used and tested by
>> people in the Jenkins project.
>>
>> The Jenkins Platform SIG  has started
>> the process of evaluating OpenJ9 with the help of Jim Crowley of IBM.
>> There are at least 4 open issues
>> 
>> related to OpenJ9 and another 15 issues
>> 
>> related to J9.  Probably best to confirm that the same problem occurs with
>> AdoptOpenJDK or with OpenJDK.
>>
>> Mark Waite
>>
>> On Wednesday, March 11, 2020 at 3:03:40 PM UTC-6, Madhu Muchukota wrote:
>>>
>>> Hi Devin, please find the thread dump attached.
>>>
>>> jfyi, we are using IBM J9.
>>>
>>> Thanks
>>> M.Madhu
>>>
>>>
>>> On Wed, Mar 11, 2020 at 2:05 PM Devin Nusbaum wrote:
>>>
 Do you have the full thread dump from a tool like jstack? If so, please
 attach it to this thread, or paste it somewhere like gist.github.com or
 pastebin.com and then paste a link to it here.

 On Mar 11, 2020, at 14:11, M.Madhusudana Reddy wrote:

 Hi Team,

 We upgraded our jenkins instance from 2.107.3 to 2.204.3 and sometimes
 we notice that jenkins master is taking lot of time to come up and jenkins
 UI/application is unresponsive.

 I took a thread dump while we ran into this issue and noticed that
 application is suffering from deadlock.

 Thread jenkins.util.Timer [#1] is in deadlock with thread 
 CpsStepContext.isReady
 [#6]

 jenkins.util.Timer [#1]priority:0x5 - threadId:0x7F9C4C16EBE0 -
 nativeId:0x5AF5 - nativeId (decimal):23285 - state:BLOCKED
 stackTrace:
 at jenkins/model/lazy/AbstractLazyLoadRunMap.getByNumber(
 AbstractLazyLoadRunMap.java:370)
 at jenkins/model/lazy/LazyBuildMixIn.getBuildByNumber(
 LazyBuildMixIn.java:228)
 at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
 WorkflowJob.java:232)
 at org/jenkinsci/plugins/workflow/job/WorkflowJob.getBuildByNumber(
 WorkflowJob.java:103)
 at hudson/model/Run.fromExternalizableId(Run.java:2446)
 at
 org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.runForDisplay(
 ExecutorStepExecution.java:445)
 at
 org/jenkinsci/plugins/workflow/support/steps/ExecutorStepExecution$PlaceholderTask.getDisplayName(
 ExecutorStepExecution.java:461)
 at org/jenkinsci/plugins/jqsmonitoring/buildqueue/QueueJob.(
 QueueJob.java:50)
 at
 org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.retrieveQueueJobs(
 BuildQueue.java:87)
 at org/jenkinsci/plugins/jqsmonitoring/buildqueue/BuildQueue.(
 BuildQueue.java:36)
 at org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring.(
 JQSMonitoring.java:43)
 at
 org/jenkinsci/plugins/jqsmonitoring/jqscore/JQSMonitoring$$FastClassByGuice$$a25d5b0d.newInstance(
 )
 at
 com/google/inject/internal/cglib/reflect/$FastConstructor.newInstance(
 FastConstructor.java:40)
 at
 com/google/inject/internal/DefaultConstructionProxyFactory$1.newInstance(
 DefaultConstructionProxyFactory.java:61)
 at com/google/inject/internal/ConstructorInjector.provision(
 ConstructorInjector.java:105)
 at com/google/inject/internal/ConstructorInjector.access$000(
 ConstructorInjector.java:32)
 at com/google/inject/internal/ConstructorInjector$1.call(
 ConstructorInjector.java:89)
 at
 com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
 ProvisionListenerStackCallback.java:115)
 at 
 hudson/ExtensionFinder$GuiceFinder$SezpozModule.onProvision(ExtensionFinder.java:567(Compiled
 Code))
 at
 com/google/inject/internal/ProvisionListenerStackCallback$Provision.provision(
 ProvisionListenerStackCallback.java:126)
 at com/google/inject/internal/ProvisionListenerStackCallback.provision(
 Provision

 ###


 CpsStepContext.isReady [#6]priority:0x5 - threadId:0x7F9C6802DE40
 - nativeId:0x5B72 - nativeId (decimal):23410 - state:BLOCKED
 stackTrace:
 at org/jenkinsci/plugins/workflow/cps/CpsGroovyShell.doParse(
 CpsGroovyShell.java:133)
 at org/jenkinsci/plugins/

Re: Install JDK Oracle 8 update 211

[Martijn Verburg]

There is also the AdoprOpenJDK binaries - www.adoptopenjdk.net and
api.adoptopenjdk.net
Cheers,
Martijn


On Wed, 17 Apr 2019 at 16:29,  wrote:

> Hi,
>
> Thank you Mark.
> I use the *Extract *.zip/*.tar.gz installer.*
> *I downloaded the jdk-8u212-windows-x64.exe file, i converted to a .zip
> archive and put it on a specific location, but in Jenkins i must fill in he
> download location for the binary archive. I'm sorry, but i don't know the
> exact url.*
> *Please can you help me?*
>
>
> *With kind regards*
>
> Op woensdag 17 april 2019 16:41:05 UTC+2 schreef Mark Waite:
>>
>> Review the new terms of the license agreement for Oracle JDK 8.  If they
>> are acceptable, then you can download the Oracle JDK binaries, place them
>> on a local location where your agents can find them, and add a JDK
>> installer to Jenkins for that location.
>>
>> The new Oracle JDK 8 license terms are more restrictive than the previous
>> terms.
>>
>> On Wed, Apr 17, 2019 at 8:31 AM  wrote:
>>
>>> Hi,
>>>
>>> Thank you for your quick reply Mark, but that's not the answer to my
>>> question.I don't think my question is clear.
>>>
>>> In Jenkins > Manage > Global Tool Configuration > JDK installlations you
>>> can install a JDK with the installer from java.sun.com
>>> Normaly it is possible to select a JDK from a drop-down list, but JDK 8
>>> update 211 is not in that list available. What is the procedure to install
>>> this JDK version.
>>>
>>> With kind regards, Wil
>>>
>>>
>>> Op woensdag 17 april 2019 15:21:26 UTC+2 schreef Mark Waite:

 I see Oracle Java SE Development Kit 8u211 at
 https://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
  .

 If that were not available, you could also consider downloading the
 Amazon Corretto 8 from
 https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/downloads-list.html

 On Wed, Apr 17, 2019 at 5:57 AM  wrote:

> Hi,
>
> How do i have to install this JDK while it is not in listed from
> java.sun.com
>
> With kind regards, Wil
>
> --
> 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 jenkins...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/9b833d57-b1b4-4448-a030-3d8b18284d84%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


 --
 Thanks!
 Mark Waite

>>> --
>>> 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 jenkins...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/a48a2df9-9db1-413c-ade9-390ba0dda8c9%40googlegroups.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Thanks!
>> Mark Waite
>>
> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/dc223758-5a0a-49b6-9be3-84c384a3f958%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAP7YuATeK6jpJVtWkLEyL-ghuHzDSR3BEiDUTjQhetb58r8kmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use AdoptOpenJDK as JDK Tool download source

[Martijn Verburg]

Hi all,

I help run AdoptOpenjDK - It's the defacto 'community' OpenJDK distro now
(Amazon, Azul, GoDaddy, IBM, jClarity, Microsoft, Pivotal, Red Hat et al
are collaborating there).  Let me know if you need any help connecting to
our API:

https://api.adoptopenjdk.net

Cheers,
Martijn


On Sat, 23 Feb 2019 at 18:14, Sverre Moe  wrote:

> Thanks for the link. Good to see that they are looking into it. Hope it
> doesn't take to long.
>
> fredag 22. februar 2019 15.38.57 UTC+1 skrev Devin Nusbaum følgende:
>>
>> There is some relevant discussion in
>> https://issues.jenkins-ci.org/browse/JENKINS-54305 that may be
>> interesting to you.
>>
>> On Feb 22, 2019, at 09:20, Sverre Moe  wrote:
>>
>> Now that Oracle has shut down any commercial use of their JDK, Jenkins
>> should add option to download JDK from AdoptOpenJDK
>>
>> Install automatically
>> Extract *.zip/*.tar.gz
>> Install from java.sun.com
>> Run Batch Command
>> Run Shell Command
>>
>> Now that the JDK from Oracle cannot be used in production we need another
>> source.
>>
>> Install from AdoptOpenJDK
>> https://adoptopenjdk.net/
>>
>> --
>> 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 jenkinsci-use...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/jenkinsci-users/6a0fc33b-e4b4-4c06-9674-2c49218617fe%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>>
>> --
> 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 jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/71bc76d5-8f1c-4761-8654-0c4961d95216%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAP7YuAT-guxrRa8J4GrpLfL_%2BUE4zZwCSa0GvEfUq49F2ficdQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Unable to reset password on jenkins.io

[Martijn Verburg]

Hi there,

I keep getting a connection timeout from this service with the originating
exception:

Caused by: java.net.ConnectException: Operation timed out (Connection timed out)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673)
at sun.security.ssl.SSLSocketImpl.(SSLSocketImpl.java:432)
at 
sun.security.ssl.SSLSocketFactoryImpl.createSocket(SSLSocketFactoryImpl.java:88)
at sun.reflect.GeneratedMethodAccessor20.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.sun.jndi.ldap.Connection.createSocket(Connection.java:328)
at com.sun.jndi.ldap.Connection.(Connection.java:203)


Cheers,
Martijn

-- 
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 jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAP7YuAQ3LQX18EkCkiWa2OnNSgujwQhhVeNi5%3DVuhLbkeDG_ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Sonar executing multiple times as a post-build action on a multi-configuration project

[Martijn Verburg]

Hi all,

We are having some problems with configuring a multi-configuration build
with Sonar.

I want to compile and test a project with multiple jdks' (6 and 7) to
make sure the project is functional under both. Additionally I want to
have Sonar execute, however want Sonar to execute on only one of the
builds to avoid executing it multiple times, which would duplicate data
in the Sonar db and waste time.

I have set this up as a multi-configuration project, with the two jvms
as an axis, and Sonar as a post build action. This builds and tests
fine, however it seems to execute Sonar on both builds.

One problem is what is the definition of a "post build action" on a
multi-configuration project. Is it something that executes after each
configuration, or something that is run once after all configurations
have finished. We have a Git publish action that seems to do what I
expect which is run once after all other configurations have been built,
however sonar appears to be the opposite. Is this a quirk of the Sonar
plugin and what it is doing is not really a "post build action"?

Is there any way of configuring a build that would achieve what I want?

Thanks,
Martijn

Re: svn 1.7

[Martijn Verburg]

Hmm, must be my bad - I was sure I read of the support somewhere (it's
my reason for upgrading as well) - M

On 6 February 2012 14:23, shanz  wrote:
> Martijn,
> I seem to already have the latest version of th plugin though (1.37)
> and 1.38 doesn't address svn 1.7 format yet ...
> Version 1.38 (not yet released)
>
>    Fixed issue #10227: Parameter "List subversion tag" was not
> displaying tags which have the same date.
>    Fixed issue #12201: NullPointerException during SVN update.
>    Fixed issue #8036: Subversion plugin to support SVN::Web browser.
>    Fixed issue #12525: SVN URL converted to lowercase -> Changes
> found every time it has an pull request.
>
>
>
>
> On Feb 6, 2:07 pm, Martijn Verburg  wrote:
>> Hi all,
>>
>> I believe the latest version of the Jenkins plugin does provide
>> support.  However,
>> Several of us have been having problems upgrading the SVN plugin (this was
>> originally thought to be an hpi vs jpi naming issue, but it seems to
>> be deeper than
>> that).
>>
>> I didn't have a chance to discuss it in detail with KK at FOSDEM, but I know 
>> a
>> few of the devs were discussing it.
>>
>> Cheers,
>> Martijn
>>
>> On 6 February 2012 14:02, shanz  wrote:
>>
>>
>>
>>
>>
>>
>>
>> > Just seen this on svnkit website ...
>>
>> > Lastest stable version of SVNKit (1.3.7) is not compatible with
>> > Subversion 1.7 working copy format. However, SVNKit 1.7 is under
>> > development now and we plan to release it in February 2012. Fully
>> > functional beta will be ready in January 2012.
>>
>> > Right now you may use SVNKit 1.7.0-alpha2 version, which is available
>> > in our maven repository or build SVNKit 1.7.0 from sources. SVNKit
>> > 1.7.0-alpha2 is compatible both with the new and old working copy
>> > formats, but does not yet support all of the Subversion operations.
>>
>> > On Feb 6, 1:55 pm, shanz  wrote:
>> >> I don't think I've got a choice since my Company is about to PUSH svn
>> >> 1.7 out automatically.
>> >> Today I've tried it out but now realise Jenkins isn't ready for it!
>>
>> >> On Feb 6, 1:48 pm,  wrote:
>>
>> >> > SVN 1.7 is a major change from 1.6. Subversion 1.7 clients use a new 
>> >> > working copy format. Subversion 1.7 clients cannot use Subversion 1.6 
>> >> > (and earlier) working copies. Existing working copies created with 
>> >> > Subversion 1.6 and earlier need to be upgraded before they can be used 
>> >> > with a Subversion 1.7 client.
>>
>> >> > If you are thinking of moving to subversion 1.7, consider all the tools 
>> >> > you use. For example, we use Jenkins, subversion command line, 
>> >> > subversion from Eclipse, etc. We won’t move until we can upgrade all of 
>> >> > them. There's no point in Jenkins checking out in 1.7 format, if I 
>> >> > can’t use the command line to look at the result (I have to do that 
>> >> > occasionally).
>>
>> >> > Hope that helps
>> >> > Matthew
>>
>> >> > > -Original Message-
>> >> > > From: jenkinsci-users@googlegroups.com 
>> >> > > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of shanz
>> >> > > Sent: 06 February 2012 13:34
>> >> > > To: Jenkins Users
>> >> > > Subject: svn 1.7
>>
>> >> > > Can Jenkins support svn 1.7?
>> >> > > My job complains with - "Please upgrade your Subversion (SVNKit)
>> >> > > client to use this working copy".
>> >> > > Can I manually upgrade SVNKit?
>> >> > > I'm using Jenkins 1.442.
>> >> > > Is it worth upgrading to Jenkins 1.450?
>>
>> >> > > Does anyone use svn 1.7.x with Jenkins successfully?
>>
>> >> > --
>> >> > This e-mail and any attachments may contain confidential, copyright and 
>> >> > or privileged material, and are for the use of the intended addressee 
>> >> > only. If you are not the intended addressee or an authorised recipient 
>> >> > of the addressee please notify us of receipt by returning the e-mail 
>> >> > and do not use, copy, retain, distribute or disclose the information in 
>> >> > or attached to the e-mail.
>> >> > Any opinions expressed within this e-mail are those of the individual 
>> >> > and not necessarily of Diamond Light Source Ltd.
>> >> > Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
>> >> > attachments are free from viruses and we cannot accept liability for 
>> >> > any damage which you may sustain as a result of software viruses which 
>> >> > may be transmitted in or with the message.
>> >> > Diamond Light Source Limited (company no. 4375679). Registered in 
>> >> > England and Wales with its registered office at Diamond House, Harwell 
>> >> > Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United 
>> >> > Kingdom

Re: svn 1.7

[Martijn Verburg]

Hi all,

I believe the latest version of the Jenkins plugin does provide
support.  However,
Several of us have been having problems upgrading the SVN plugin (this was
originally thought to be an hpi vs jpi naming issue, but it seems to
be deeper than
that).

I didn't have a chance to discuss it in detail with KK at FOSDEM, but I know a
few of the devs were discussing it.

Cheers,
Martijn

On 6 February 2012 14:02, shanz  wrote:
> Just seen this on svnkit website ...
>
> Lastest stable version of SVNKit (1.3.7) is not compatible with
> Subversion 1.7 working copy format. However, SVNKit 1.7 is under
> development now and we plan to release it in February 2012. Fully
> functional beta will be ready in January 2012.
>
> Right now you may use SVNKit 1.7.0-alpha2 version, which is available
> in our maven repository or build SVNKit 1.7.0 from sources. SVNKit
> 1.7.0-alpha2 is compatible both with the new and old working copy
> formats, but does not yet support all of the Subversion operations.
>
>
> On Feb 6, 1:55 pm, shanz  wrote:
>> I don't think I've got a choice since my Company is about to PUSH svn
>> 1.7 out automatically.
>> Today I've tried it out but now realise Jenkins isn't ready for it!
>>
>> On Feb 6, 1:48 pm,  wrote:
>>
>>
>>
>>
>>
>>
>>
>> > SVN 1.7 is a major change from 1.6. Subversion 1.7 clients use a new 
>> > working copy format. Subversion 1.7 clients cannot use Subversion 1.6 (and 
>> > earlier) working copies. Existing working copies created with Subversion 
>> > 1.6 and earlier need to be upgraded before they can be used with a 
>> > Subversion 1.7 client.
>>
>> > If you are thinking of moving to subversion 1.7, consider all the tools 
>> > you use. For example, we use Jenkins, subversion command line, subversion 
>> > from Eclipse, etc. We won’t move until we can upgrade all of them. There's 
>> > no point in Jenkins checking out in 1.7 format, if I can’t use the command 
>> > line to look at the result (I have to do that occasionally).
>>
>> > Hope that helps
>> > Matthew
>>
>> > > -Original Message-
>> > > From: jenkinsci-users@googlegroups.com 
>> > > [mailto:jenkinsci-users@googlegroups.com] On Behalf Of shanz
>> > > Sent: 06 February 2012 13:34
>> > > To: Jenkins Users
>> > > Subject: svn 1.7
>>
>> > > Can Jenkins support svn 1.7?
>> > > My job complains with - "Please upgrade your Subversion (SVNKit)
>> > > client to use this working copy".
>> > > Can I manually upgrade SVNKit?
>> > > I'm using Jenkins 1.442.
>> > > Is it worth upgrading to Jenkins 1.450?
>>
>> > > Does anyone use svn 1.7.x with Jenkins successfully?
>>
>> > --
>> > This e-mail and any attachments may contain confidential, copyright and or 
>> > privileged material, and are for the use of the intended addressee only. 
>> > If you are not the intended addressee or an authorised recipient of the 
>> > addressee please notify us of receipt by returning the e-mail and do not 
>> > use, copy, retain, distribute or disclose the information in or attached 
>> > to the e-mail.
>> > Any opinions expressed within this e-mail are those of the individual and 
>> > not necessarily of Diamond Light Source Ltd.
>> > Diamond Light Source Ltd. cannot guarantee that this e-mail or any 
>> > attachments are free from viruses and we cannot accept liability for any 
>> > damage which you may sustain as a result of software viruses which may be 
>> > transmitted in or with the message.
>> > Diamond Light Source Limited (company no. 4375679). Registered in England 
>> > and Wales with its registered office at Diamond House, Harwell Science and 
>> > Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

Re: Subversion 1.37 upgrade in Jenkins 1.450

[Martijn Verburg]

Hi there,

> I've read that some issues were seen for which fixes were targeted for
> Jenkins 1.450 for issues with upgrading Subversion from 1.34 to 1.37 but my
> clean install on Tomcat 6.0.35 (Windows Server 2008 R2 64-bit installer
> running as service) doesn't seem to work.

Likewise, clean install of Tomcat 7.0.25 and jenkins 1.450 - upgrading
the SVN and CVS
plugins both fail.

Although the extensions are now .jpi it still refuses to update the plugin.

Cheers,
Martijn