Bug 1197576 - Upgrade Jenkins from jenkins-1.565.3-1 to jenkins-1.580.3-1
Summary: Upgrade Jenkins from jenkins-1.565.3-1 to jenkins-1.580.3-1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 2.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Mike Barrett
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-02 05:25 UTC by Jaspreet Kaur
Modified: 2019-08-15 04:18 UTC (History)
7 users (show)

Fixed In Version: jenkins-1.609.1-1.el6op
Doc Type: Enhancement
Doc Text:
Certain Jenkins plug-ins insist on a specific minimum version of Jenkins. As time passes, more and more Jenkins plug-ins will be unable to be upgraded or installed because the minimum version of Jenkins required is later than that provided by OpenShift. This enhancement upgrades the Jenkins cartridge to jenkins-1.609.1.
Clone Of:
Environment:
Last Closed: 2015-09-30 16:36:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:1844 0 normal SHIPPED_LIVE Important: Red Hat OpenShift Enterprise 2.2.7 security, bug fix and enhancement update 2015-09-30 20:35:28 UTC

Description Jaspreet Kaur 2015-03-02 05:25:26 UTC
Description of problem:

Customer has requested to upgrade Jenkins from jenkins-1.565.3-1 to jenkins-1.580.3-1 in Openshift

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Here is the link where a detail has been mentioned to use this repository  http://pkg.jenkins-ci.org/redhat-stable/

Comment 3 Miciah Dashiel Butler Masters 2015-09-18 18:25:41 UTC
We will ship Jenkins 1.609.1 with OpenShift Enterprise 2.2.7.

Comment 6 Johnny Liu 2015-09-21 09:55:29 UTC
Verified this bug with 2.2/2015-09-18.2, and PASS.


[root@node1 ~]# rpm -q jenkins
jenkins-1.609.1-1.el6op.noarch


Create a new app, embed jenkins-client, trigger jenkins build. Build is finished successfully.

[jialiu@jialiu-laptop php53app]$ vim index.php 
[jialiu@jialiu-laptop php53app]$ git commit -a -mx; git push
<--snip-->
Counting objects: 5, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (3/3), done.
Writing objects: 100% (3/3), 309 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
remote: Syncing git content to other proxy gears
remote: Executing Jenkins build.
remote: 
remote: You can track your build at https://jenkins-jialiu1.ose22-auto.com.cn/job/scaphp53app-build
remote: 
remote: Waiting for build to schedule................................Done
remote: Waiting for job to complete......................Done
remote: SUCCESS
remote: New build has been deployed.
remote: -------------------------
remote: Git Post-Receive Result: success
remote: Deployment completed with status: success
To ssh://jialiu1-scaphp53app-1.com.cn/~/git/scaphp53app.git/
   fbba337..23c3edf  master -> master



$ curl scaphp53app-jialiu1.ose22-auto.com.cn|grep title
<title>Welc111ome to OpenShift</title>

Comment 8 errata-xmlrpc 2015-09-30 16:36:37 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-1844.html


Note You need to log in before you can comment on or make changes to this bug.