If you are still on 1.609, you are likely vulnerable to wide array of
security issues.

Suggest that you use a restored backup to test the upgrade and see what the
issues are, if any.

On Wed, Aug 23, 2017, 5:01 PM Mark Waite <[email protected]> wrote:

> With that age of a system, I'd either leave it alone or replace it with a
> new Jenkins version.  I wouldn't attempt to upgrade it "in place".
>
> If you decide to not leave it alone, refer to the
> https://jenkins.io/doc/upgrade-guide/ and realize that you're moving
> across a 2 year gap and a major version number change, with significant new
> functionality added in that two year period.
>
> Jenkins 2 is really great, and has real, very serious advantages over
> 1.609.3.  Some of those advantages include:
>
>    - Blue Ocean user experience is intensely focused on developers
>    - Pipeline expresses job definitions in a domain specific language
>    tuned to continuous delivery
>    - Multi-branch Pipeline will create and destroy jobs automatically
>    based on discovered branches
>    - Java 8 is required (placing you on a currently supported JDK)
>    - Many security advisories have been resolved
>    - Performance and scale improvements
>    - Reliability improvements
>    - Significant enhancements in many plugins
>
> Mark Waite
>
> On Wed, Aug 23, 2017 at 2:44 PM louwho <[email protected]> wrote:
>
>> Off and on, I have touched upon Jenkins.  My expertise is InstallShield
>> development, with some Release engineering.  Anyway, new project, taking
>> over the Jenkins build system also.  Current  Jenkins version is 1.609.3,
>> the Jenkins LTS is now 2.6.03.  Putting aside (for now), the old adage of
>> 'if it an't broken, don't fix it', are there any real advantages to
>> upgrading to the latest version, or should I just leave it alone?   The
>> product builds are building PowerBuilder and Java products..and then
>> InstallShield, copies to AWS S3, etc.  We are also considering using some
>> third party tools that will allow us to move the Powerbuilder stuff from
>> the CVS repository to GIT.  As an aside, does anyone know if you can have
>> two versions of PowerBuilder on the same build system?
>>
>> --
>> 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/70caafe3-ec9a-4730-ada5-e598b401973a%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/70caafe3-ec9a-4730-ada5-e598b401973a%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFDVK28Tz_FYuGG7J1vqbZx5-14ePOkOJNK3wG64voM5w%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtFDVK28Tz_FYuGG7J1vqbZx5-14ePOkOJNK3wG64voM5w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANHK%3DJ2jK%3Dt8H68-wSWfOy9AfSi3gzPVFn%2Bb2uUcOwvVXix%3D8g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to