%global _empty_manifest_terminate_build 0
Name:		python-ansible-lint-junit
Version:	0.17.7
Release:	1
Summary:	ansible-lint to JUnit converter.
License:	MIT License
URL:		https://github.com/wasilak/ansible-lint-junit
Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/c2/e3/4991add8c239c1f0b1807a1bfb3e63be74de04aa372237a7a5eabb7023df/ansible-lint-junit-0.17.7.tar.gz
BuildArch:	noarch

Requires:	python3-ansible-lint

%description
The [ansible-lint](https://github.com/willthames/ansible-lint) to JUnit converter.
### Installation
via pip:
```shell
pip install ansible-lint-junit
```
### Updating
via pip:
```shell
pip install ansible-lint-junit --upgrade
```
### Usage:
- You can run `ansible-lint` on your playbook(s) and redirect output to pipe
  ```shell
  ansible-lint playbook.yml -p --nocolor | ansible-lint-junit -o ansible-lint.xml
  ```
- You can use a temporary file to store the output of `ansible-lint`.
  After that run `ansible-lint-junit` and pass generated file to it
  ```shell
  ansible-lint -p --nocolor your_fancy_playbook.yml > ansible-lint.txt
  ansible-lint-junit ansible-lint.txt -o ansible-lint.xml
  ```
### Output
- If there are any lint errors, full JUnit XML will be created.
- If there are no errors, empty JUnit XML will be created, this is for
  i.e. [Bamboo](https://www.atlassian.com/software/bamboo) JUnit parser plugin compatibility.\
  It will break build if XML is missing or incorrect, and there is really no way of generating XML with *"PASSED"* tests
  in case of linter.
### License
The ansible-lint-junit project is distributed under the [MIT] license.

%package -n python3-ansible-lint-junit
Summary:	ansible-lint to JUnit converter.
Provides:	python-ansible-lint-junit
BuildRequires:	python3-devel
BuildRequires:	python3-setuptools
BuildRequires:	python3-pip
%description -n python3-ansible-lint-junit
The [ansible-lint](https://github.com/willthames/ansible-lint) to JUnit converter.
### Installation
via pip:
```shell
pip install ansible-lint-junit
```
### Updating
via pip:
```shell
pip install ansible-lint-junit --upgrade
```
### Usage:
- You can run `ansible-lint` on your playbook(s) and redirect output to pipe
  ```shell
  ansible-lint playbook.yml -p --nocolor | ansible-lint-junit -o ansible-lint.xml
  ```
- You can use a temporary file to store the output of `ansible-lint`.
  After that run `ansible-lint-junit` and pass generated file to it
  ```shell
  ansible-lint -p --nocolor your_fancy_playbook.yml > ansible-lint.txt
  ansible-lint-junit ansible-lint.txt -o ansible-lint.xml
  ```
### Output
- If there are any lint errors, full JUnit XML will be created.
- If there are no errors, empty JUnit XML will be created, this is for
  i.e. [Bamboo](https://www.atlassian.com/software/bamboo) JUnit parser plugin compatibility.\
  It will break build if XML is missing or incorrect, and there is really no way of generating XML with *"PASSED"* tests
  in case of linter.
### License
The ansible-lint-junit project is distributed under the [MIT] license.

%package help
Summary:	Development documents and examples for ansible-lint-junit
Provides:	python3-ansible-lint-junit-doc
%description help
The [ansible-lint](https://github.com/willthames/ansible-lint) to JUnit converter.
### Installation
via pip:
```shell
pip install ansible-lint-junit
```
### Updating
via pip:
```shell
pip install ansible-lint-junit --upgrade
```
### Usage:
- You can run `ansible-lint` on your playbook(s) and redirect output to pipe
  ```shell
  ansible-lint playbook.yml -p --nocolor | ansible-lint-junit -o ansible-lint.xml
  ```
- You can use a temporary file to store the output of `ansible-lint`.
  After that run `ansible-lint-junit` and pass generated file to it
  ```shell
  ansible-lint -p --nocolor your_fancy_playbook.yml > ansible-lint.txt
  ansible-lint-junit ansible-lint.txt -o ansible-lint.xml
  ```
### Output
- If there are any lint errors, full JUnit XML will be created.
- If there are no errors, empty JUnit XML will be created, this is for
  i.e. [Bamboo](https://www.atlassian.com/software/bamboo) JUnit parser plugin compatibility.\
  It will break build if XML is missing or incorrect, and there is really no way of generating XML with *"PASSED"* tests
  in case of linter.
### License
The ansible-lint-junit project is distributed under the [MIT] license.

%prep
%autosetup -n ansible-lint-junit-0.17.7

%build
%py3_build

%install
%py3_install
install -d -m755 %{buildroot}/%{_pkgdocdir}
if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
pushd %{buildroot}
if [ -d usr/lib ]; then
	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/lib64 ]; then
	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/bin ]; then
	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
fi
if [ -d usr/sbin ]; then
	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
fi
touch doclist.lst
if [ -d usr/share/man ]; then
	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
fi
popd
mv %{buildroot}/filelist.lst .
mv %{buildroot}/doclist.lst .

%files -n python3-ansible-lint-junit -f filelist.lst
%dir %{python3_sitelib}/*

%files help -f doclist.lst
%{_docdir}/*

%changelog
* Fri May 05 2023 Python_Bot <Python_Bot@openeuler.org> - 0.17.7-1
- Package Spec generated