The file /etc/yum.repos.d/jenkins.repo belongs to the jenkins package.
This is IMHO a non-sense. Please think about people that integrate jenkins with other repository system (e.g. pulp).
It is not bad to have a repo in a RPM, but other tools/repos like EPEL have a dedicated RPM besides other rpms.
So I propose to split the jenkins-repo rpm from the jenkins rpm.
- duplicates
-
JENKINS-22690 RPM install jenkins.repo file
-
- Resolved
-
- is related to
-
JENKINS-12757 It is not possible to use the RedHat/Fedora/Centos RPM:s on a private network.
-
- Closed
-
I fully agree.
Yum repository information should not be stored in the main jenkins RPM.
A unwelcome side-effect of this is that the file /etc/yum.repos.d/jenkins.repo is removed when the Jenkins RPM is removed from the system.
This forces a server-administrator to (manually) place the jenkins.repo file on the server again.
Most of the time this kind yum repository information is stored in a separate *-release.rpm
For jenkins this RPM would be named as: jenkins-release.rpm
A nice example for this can be fedora-release-18-1.noarch.rpm or rpmfusion-free-release-18-3.noarch