Metadata-Version: 2.1
Name: py3status-jenkins-status
Version: 0.0.1.dev4
Summary: py3status module to display the current jenkins job status
Home-page: https://gitlab.com/schmidtandreas/py3status-jenkins
Author: Andreas Schmidt
Author-email: mail@schmidt-andreas.de
License: UNKNOWN
Platform: UNKNOWN
Classifier: Development Status :: 2 - Pre-Alpha
Classifier: Operating System :: POSIX :: Linux
Classifier: License :: OSI Approved :: MIT License
Classifier: Environment :: Console
Classifier: Topic :: Utilities
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3.6
Classifier: Programming Language :: Python :: 3.7
Description-Content-Type: text/markdown
Requires-Dist: py3status (>=3.20)
Requires-Dist: jenkins
Requires-Dist: pypass
Provides-Extra: lint
Requires-Dist: pre-commit ; extra == 'lint'
Provides-Extra: test
Requires-Dist: pytest ; extra == 'test'
Requires-Dist: py3status ; extra == 'test'

[![Documentation Status](https://readthedocs.org/projects/py3status-jenkins/badge/?version=latest)](https://py3status-jenkins.readthedocs.io/en/latest/?badge=latest)

# py3status-jenkins-status

A [py3status](https://github.com/ultrabug/py3status) module displays the current status of jenkins jobs.


# CHANGELOG

This project uses [semantic versioning](https://semver.org/).

## [x.x.x] - tbd

## [0.0.1-dev4] - 2021-04-28
### Added

* changelog entries
* Initial documentation (sphinx)
* readme file for documentation
* username/password credentials handling

### Fixing

* remove debug pring
* failure status name in description
* version (adjust to semantic versioning)

## [0.1.dev3] - 2021-04-27
### Fixed

* Module name and path

## [0.1.dev2] - 2021-04-26
### Added

* Missing author and athor_email in setup.py
* Main chapter to readme
* MIT license file
* Manifest file

## [0.1] - 2021-04-25
### Added

* Initial implementation of jenkins job status viewer

---

# About this Changelog

https://keepachangelog.com suggests:

Guiding Principles

* Changelogs are for humans, not machines.
* There should be an entry for every single version.
* The same types of changes should be grouped.
* Versions and sections should be linkable.
* The latest version comes first.
* The release date of each version is displayed.
* Mention whether you follow Semantic Versioning.

Types of changes

* **Added for new features.**
* **Changed for changes in existing functionality.**
* **Deprecated for soon-to-be removed features.**
* **Removed for now removed features.**
* **Fixed for any bug fixes.**
* **Security in case of vulnerabilities.**


