Development Guide - dogtagpki/pki Wiki

🚨 github-wiki-see.page does not render asciidoc. Source for crawling below. Please visit the Original URL! 🚨


= Overview =

* link:https://www.dogtagpki.org/wiki/PKI_Coding_Style[Coding Style]
* link:https://www.dogtagpki.org/wiki/Patch_Review_Process[Patch Review Process]
* link:https://www.dogtagpki.org/wiki/PKI_Contributing[Contributing]
* link:https://www.dogtagpki.org/wiki/PKI_Licensing[Licensing]

= Environment =

* link:Setting-Up-Eclipse[Setting Up Eclipse]

= Repositories =

* link:https://gitlab.com/dogtagpki/pki[GitLab Repository]
** link:https://github.com/dogtagpki/pki/blob/master/docs/development/Synchronizing-GitLab-Branch.adoc[Synchronizing GitLab Branch]
* link:Azure-DevOps-Repository[Azure DevOps Repository]

= Dependencies =

* link:https://github.com/dogtagpki/resteasy/wiki/Development-Guide[RESTEasy Development Guide]
* link:https://github.com/dogtagpki/jss/wiki/Development-Guide[JSS Development Guide]

= Development =

* link:Design-Documents[Design Documents]
* link:Installation-Parameter-Deprecation[Installation Parameter Deprecation]
* link:CA-Development-Guide[CA Development Guide]
* link:TKS-Development-Guide[TKS Development Guide]
* link:TPS-Development-Guide[TPS Development Guide]
* link:ACME-Development-Guide[ACME Development Guide]
* link:SCEP-Development-Guide[SCEP Development Guide]

= Documentation =

* link:Migrating-PKI-Documentation[Migrating PKI Documentation]

= Builds =

* link:https://www.dogtagpki.org/wiki/PKI_FHS_Packaging[PKI FHS Packaging]
* link:https://github.com/dogtagpki/pki/blob/master/docs/development/Building_PKI.md[Building PKI]
* link:COPR-Repositories[COPR Repositories]
* link:Fedora-Packaging-Guide[Fedora Packaging Guide]
* link:CentOS-Packaging-Guide[CentOS Packaging Guide]

= Testing =

Contributors can help by finding new link:https://www.dogtagpki.org/wiki/PKI_Bugs[bugs], verifying link:https://bugzilla.redhat.com/bugzilla/buglist.cgi?query_format=advanced&product=Dogtag+Certificate+System&cmdtype=doit[existing bugs], polishing link:Home[documentation], and generally improving the quality of the various subsystems.

A good way to contribute to improving the quality of a subsystem would be to add automated tests for each of the features. Developers and contributors to the Dogtag Certificate System Project are encouraged to write unit tests for any new features, updates, and bug fixes being contributed. Where possible, the tests should be data driven. This allows for greater numbers of test cases, covering more of the features under testing, to be written with minimal effort. We suggest that tests be written in a scripting language such as Python for ease of maintenance.

* link:Testing-Standalone-Subsystems[Testing Standalone Subsystems]
* link:https://www.dogtagpki.org/wiki/Cloning_Tests[Cloning Tests]
* link:Continuous-Integration[Continuous Integration]
* link:https://github.com/dogtagpki/pki/blob/master/docs/development/Debugging_Pipeline.md[Debugging QE Pipeline Failures]

= See Also =

* https://github.com/dogtagpki/pki/tree/master/docs/development
* link:https://www.dogtagpki.org/wiki/PKI_Prerequisites[PKI Prerequisites]
* link:https://www.dogtagpki.org/wiki/PKI_Runtime_Environments[PKI Runtime Environments]
* link:https://www.dogtagpki.org/wiki/PKI_Data_Storage_Requirements[PKI Data Storage Requirements]
* link:https://www.dogtagpki.org/wiki/PKI_Development_Environments[PKI Development Environments]
* link:https://www.dogtagpki.org/wiki/PKI_10_Development[PKI 10 Development]
* link:https://www.dogtagpki.org/wiki/PKI_9_Development[PKI 9 Development]
* link:https://www.dogtagpki.org/wiki/PKI_Developers[PKI Developers]