File jenkins-plugin-configuration-as-code.spec of Package jenkins-plugin-configuration-as-code

#
# spec file for package jenkins-plugin-configuration-as-code
#
# Copyright (c) 2023 SUSE LLC
#
# All modifications and additions to the file contributed by third parties
# remain the property of their copyright owners, unless otherwise agreed
# upon. The license for this file, and modifications and additions to the
# file, is the same license as for the pristine package itself (unless the
# license for the pristine package is not an Open Source License, in which
# case the license is the MIT License). An "Open Source License" is a
# license that conforms to the Open Source Definition (Version 1.9)
# published by the Open Source Initiative.

# Please submit bugfixes or comments via https://bugs.opensuse.org/
#


%define plugin configuration-as-code
Name:           jenkins-plugin-%{plugin}
Version:        1670
Release:        0
Summary:        Jenkins Configuration as Code (JCasC)
License:        Apache-2.0
Group:          Development/Tools/Building
URL:            https://plugins.jenkins.io/configuration-as-code
Source:         https://updates.jenkins.io/latest/%{plugin}.hpi
BuildRequires:  jenkins
Requires:       jenkins
Requires:       jenkins-plugin-caffeine-api >= 2.9.3
Requires:       jenkins-plugin-commons-text-api >= 1.10.0
Requires:       jenkins-plugin-snakeyaml-api >= 1.33
BuildArch:      noarch

%description
Setting up Jenkins is a complex process, as both Jenkins and its plugins require some tuning and configuration, with dozens of parameters to set within the web UI manage section.

Experienced Jenkins users rely on groovy init scripts to customize Jenkins and enforce the desired state. Those scripts directly invoke Jenkins API and, as such, can do everything (at your own risk). But they also require you to know Jenkins internals and are confident in writing groovy scripts on top of Jenkins API.

The Configuration as Code plugin is an opinionated way to configure Jenkins based on human-readable declarative configuration files. Writing such a file should be feasible without being a Jenkins expert, just translating into code a configuration process one is used to executing in the web UI.

%prep

%build

%install
install -d %{buildroot}%{_localstatedir}/lib/jenkins/plugins
install -t %{buildroot}%{_localstatedir}/lib/jenkins/plugins %{SOURCE0}

%files
%dir %attr(0755, jenkins, jenkins) %{_localstatedir}/lib/jenkins/plugins
%{_localstatedir}/lib/jenkins/plugins/%{plugin}.hpi

%changelog