The final step is to create the repository configuration file. The file is required to
identify the path to the repository data, and check whether a GPG signature check should be
performed on the repository packages. You need only one repository configuration
file.
- Navigate to the repository directory.
- Create a repository file.
Alternatively, you can copy an existing repository file to edit.
-
Add the following content in the repository file:
#VERSION_NUMBER=<downloaded-version#>
[<service-name-abbreviation>]
This is composed of the service name abbreviation and version number (includes the
build number). Example: DAS-APP-1.4.5.0-x.
name=<service-name-abbreviation> Version - <service-name-abbreviation>
baseurl=http://<webserver-host-name>/<directory-containing-repo>
<webserver-host-name> is the FQDN of the web server host that contains the
repository. This is the same base URL that you used earlier to prepare the
repositories.
<directory-containing-repo> is the path expanded from the tarball.
gpgcheck=1
gpgkey=http://<webserver-host-name>/<directory-containing-repo>/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1
Example Repository File:
#VERSION_NUMBER=1.4.5.0-x
[DAS-APP-1.4.5.0-x]
name=DAS-APP Version - DAS-APP-1.4.5.0-x
baseurl=http://<your_webserver>:port/DAS-APP/centos7/1.4.5.0-x
gpgcheck=1
gpgkey=http://<your_webserver>:port/DAS-APP/centos7/1.4.5.0-x/RPM-GPG-KEY/RPM-GPG-KEY-Jenkins
enabled=1
priority=1