mirror of
https://github.com/jenkinsci/jenkins.git
synced 2026-11-16 05:22:22 +00:00
There's some expected performance gain since people often deploy $JENKINS_HOME over NFS.
142 lines
4.8 KiB
RPMSpec
142 lines
4.8 KiB
RPMSpec
# TODO:
|
|
# - how to add to the trusted service of the firewall?
|
|
|
|
%define _prefix %{_usr}/lib/jenkins
|
|
%define workdir %{_var}/lib/jenkins
|
|
|
|
Name: jenkins
|
|
Version: %{ver}
|
|
Release: 1.2
|
|
Summary: Continous Build Server
|
|
Source: jenkins.war
|
|
Source1: jenkins.init.in
|
|
Source2: jenkins.sysconfig.in
|
|
Source3: jenkins.logrotate
|
|
Source4: jenkins.repo
|
|
URL: http://jenkins-ci.org/
|
|
Group: Development/Tools/Building
|
|
License: MIT/X License, GPL/CDDL, ASL2
|
|
BuildRoot: %{_tmppath}/build-%{name}-%{version}
|
|
# see the comment below from java-1.6.0-openjdk.spec that explains this dependency
|
|
# java-1.5.0-ibm from jpackage.org set Epoch to 1 for unknown reasons,
|
|
# and this change was brought into RHEL-4. java-1.5.0-ibm packages
|
|
# also included the epoch in their virtual provides. This created a
|
|
# situation where in-the-wild java-1.5.0-ibm packages provided "java =
|
|
# 1:1.5.0". In RPM terms, "1.6.0 < 1:1.5.0" since 1.6.0 is
|
|
# interpreted as 0:1.6.0. So the "java >= 1.6.0" requirement would be
|
|
# satisfied by the 1:1.5.0 packages. Thus we need to set the epoch in
|
|
# JDK package >= 1.6.0 to 1, and packages referring to JDK virtual
|
|
# provides >= 1.6.0 must specify the epoch, "java >= 1:1.6.0".
|
|
#
|
|
# java-1_6_0-sun provides this at least
|
|
Requires: java >= 1.6
|
|
Obsoletes: hudson
|
|
PreReq: /usr/sbin/groupadd /usr/sbin/useradd
|
|
#PreReq: %{fillup_prereq}
|
|
BuildArch: noarch
|
|
|
|
%description
|
|
Jenkins monitors executions of repeated jobs, such as building a software
|
|
project or jobs run by cron. Among those things, current Jenkins focuses on the
|
|
following two jobs:
|
|
- Building/testing software projects continuously, just like CruiseControl or
|
|
DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called
|
|
continuous integration system, making it easier for developers to integrate
|
|
changes to the project, and making it easier for users to obtain a fresh
|
|
build. The automated, continuous build increases the productivity.
|
|
- Monitoring executions of externally-run jobs, such as cron jobs and procmail
|
|
jobs, even those that are run on a remote machine. For example, with cron,
|
|
all you receive is regular e-mails that capture the output, and it is up to
|
|
you to look at them diligently and notice when it broke. Jenkins keeps those
|
|
outputs and makes it easy for you to notice when something is wrong.
|
|
|
|
|
|
|
|
|
|
Authors:
|
|
--------
|
|
Kohsuke Kawaguchi <Kohsuke.Kawaguchi@sun.com>
|
|
|
|
%prep
|
|
%setup -q -T -c
|
|
|
|
%build
|
|
|
|
%install
|
|
rm -rf "%{buildroot}"
|
|
%__install -D -m0644 "%{SOURCE0}" "%{buildroot}%{_prefix}/%{name}.war"
|
|
%__install -d "%{buildroot}%{workdir}"
|
|
%__install -d "%{buildroot}%{workdir}/plugins"
|
|
|
|
%__install -d "%{buildroot}/var/log/jenkins"
|
|
%__install -d "%{buildroot}/var/cache/jenkins"
|
|
|
|
%__install -D -m0755 "%{SOURCE1}" "%{buildroot}/etc/init.d/%{name}"
|
|
%__sed -i 's,@@WAR@@,%{_prefix}/%{name}.war,g' "%{buildroot}/etc/init.d/%{name}"
|
|
%__install -d "%{buildroot}/usr/sbin"
|
|
%__ln_s "../../etc/init.d/%{name}" "%{buildroot}/usr/sbin/rc%{name}"
|
|
|
|
%__install -D -m0644 "%{SOURCE2}" "%{buildroot}/etc/sysconfig/%{name}"
|
|
%__sed -i 's,@@HOME@@,%{workdir},g' "%{buildroot}/etc/sysconfig/%{name}"
|
|
|
|
%__install -D -m0644 "%{SOURCE3}" "%{buildroot}/etc/logrotate.d/%{name}"
|
|
|
|
%__install -D -m0644 "%{SOURCE4}" "%{buildroot}/etc/zypp/repos.d/jenkins.repo"
|
|
%pre
|
|
/usr/sbin/groupadd -r jenkins &>/dev/null || :
|
|
# SUSE version had -o here, but in Fedora -o isn't allowed without -u
|
|
/usr/sbin/useradd -g jenkins -s /bin/false -r -c "Jenkins Continuous Build server" \
|
|
-d "%{workdir}" jenkins &>/dev/null || :
|
|
|
|
%post
|
|
[ $1 -eq 1 ] && /sbin/chkconfig --add jenkins
|
|
|
|
# If we have an old hudson install, rename it to jenkins
|
|
if test -d /var/lib/hudson; then
|
|
# leave a marker to indicate this came from Hudson.
|
|
# could be useful down the road
|
|
# This also ensures that the .??* wildcard matches something
|
|
touch /var/lib/hudson/.moving-hudson
|
|
mv -f /var/lib/hudson/* /var/lib/hudson/.??* /var/lib/jenkins
|
|
rmdir /var/lib/hudson
|
|
find /var/lib/jenkins -user hudson -exec chown jenkins {} + || true
|
|
fi
|
|
if test -d /var/run/hudson; then
|
|
mv -f /var/run/hudson/* /var/run/jenkins
|
|
rmdir /var/run/hudson
|
|
fi
|
|
|
|
%preun
|
|
if [ "$1" = 0 ] ; then
|
|
# if this is uninstallation as opposed to upgrade, delete the service
|
|
/sbin/service jenkins stop > /dev/null 2>&1
|
|
/sbin/chkconfig --del jenkins
|
|
fi
|
|
exit 0
|
|
|
|
%postun
|
|
if [ "$1" -ge 1 ]; then
|
|
/sbin/service jenkins condrestart > /dev/null 2>&1
|
|
fi
|
|
exit 0
|
|
|
|
%clean
|
|
%__rm -rf "%{buildroot}"
|
|
|
|
%files
|
|
%defattr(-,root,root)
|
|
%dir %{_prefix}
|
|
%{_prefix}/%{name}.war
|
|
%attr(0755,jenkins,jenkins) %dir %{workdir}
|
|
%attr(0750,jenkins,jenkins) /var/log/jenkins
|
|
%attr(0750,jenkins,jenkins) /var/cache/jenkins
|
|
%config(noreplace) /etc/logrotate.d/%{name}
|
|
%config /etc/init.d/%{name}
|
|
%config(noreplace) /etc/sysconfig/%{name}
|
|
%config(noreplace) /etc/zypp/repos.d/jenkins.repo
|
|
/usr/sbin/rc%{name}
|
|
|
|
%changelog
|
|
* Wed Sep 28 2011 kk@kohsuke.org
|
|
- See [http://jenkins-ci.org/changelog] for complete details
|