Hide Forgot
Scott, not sure if this is an issue of needing to package the newer versions of the plugins, or it's another repo tagging problem. Wen, that file has no actual bearing on the plugin versions in rhel, it's only used for centos. We should probably remove that file from the rhel image, but I would still expect us to have packaged versions of those plugin versions installed.
tested openshift3/jenkins-1-rhel7:1.651.2-19, plugins are updated as below version: Durable Task Plugin 1.10 Credentials Plugin 2.1.0 but matrix-project plugin in is 1.4.1 ,not 1.7 ,should be updated too.
Created attachment 1193844 [details] matrix project plugin
RPM content must be bad, it's got the "right" version of the rpm installed. bash-4.2$ rpm -q jenkins-plugin-matrix-project jenkins-plugin-matrix-project-1.7-1.el7.x86_64
@Scott, hm. I believe Troy did all the packaging on those.
The MD5 sum of the plugin inside the container matches the md5sum as downloaded from jenkins-ci for matrix-project 1.7. Can we confirm what QE is seeing in comment #4 and see if there's any other way this could be happening? # docker run -u root -it --entrypoint /usr/bin/md5sum brew-pulp-docker01.web.prod.ext.phx2.redhat.com:8888/openshift3/jenkins-1-rhel7:1.651.2-19 /usr/lib64/jenkins/matrix-project.hpi 7c592fbf784ecbee22da6fef775859d0 /usr/lib64/jenkins/matrix-project.hpi # wget -q http://mirrors.jenkins-ci.org/plugins/matrix-project/1.7/matrix-project.hpi # md5sum matrix-project.hpi 7c592fbf784ecbee22da6fef775859d0 matrix-project.hpi
need to ping matrix-project as well
https://github.com/openshift/jenkins/pull/148
tested with brew....openshift3/jenkins-1-rhel7 023723e2e0ff matrix project plugin also 1.4.1
Yeah this got in after Scott started the rhel image build; did not expect this to change with the image you tried @WangHaoran
brew pulp latest now has pull 148 and I confirmed that the matrix project plugin is now at 1.7 QE can verify
verified with openshift3/jenkins-1-rhel7 a2b7f45b9e0d now it's 1.7 ,thanks
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://access.redhat.com/errata/RHBA-2016:1937