From Fedora Project Wiki

(update contribution guide links)
(ResultsDB is still operational)
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
{{admon/caution|Taskotron development reached end of life|Taskotron has been [https://kparal.wordpress.com/2020/04/30/taskotron-is-eol-end-of-life-today/ sunset] in Fedora Infrastructure. It is no longer running and no longer being developed. You can use these wiki pages to learn about its history, but please be aware that the information is no longer actual.}}
 +
 +
{{admon/tip|ResultsDB is still operational|Even when Taskotron is EOL, [[ResultsDB]] is still being used. You can use our simple web frontend to explore the [https://taskotron.fedoraproject.org/resultsdb/ production instance].}}
 +
 
== Overview ==
 
== Overview ==
  
'''Taskotron''' is a framework for automated task execution. It currently runs selected package checks in Fedora.
+
'''Taskotron''' was a framework for automated task execution. It ran selected package checks in Fedora.
  
 
Some of its major envisioned features:
 
Some of its major envisioned features:
Line 11: Line 15:
 
* Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle
 
* Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle
 
* Useful for other Linux distributions as well, not just Fedora
 
* Useful for other Linux distributions as well, not just Fedora
 
== Our systems ==
 
 
* [https://taskotron.fedoraproject.org/ Taskotron production instance]
 
* [https://taskotron.stg.fedoraproject.org/ Taskotron staging instance]
 
  
 
== Source code, getting involved and contributing ==
 
== Source code, getting involved and contributing ==
  
Taskotron consists of multiple separate components, mainly hosted in the {{code|taskotron}} namespace in [https://pagure.io Pagure]. Pagure currently does not provide an overview page for namespaces; once it does, we will link to it here. For now, see the [[QA:Taskotron contribution guide|contribution guide]] for a full list of repositories.
+
Taskotron consisted of multiple separate components, mainly hosted in the [https://pagure.io/group/taskotron {{code|taskotron}} namespace in Pagure]. The general tasks that were developed along with Taskotron were named with the ''task-'' prefix.
 
 
The general tasks that are developed along with Taskotron can be found in the [https://bitbucket.org/fedoraqa Fedora QA Bitbucket project] for now.
 
  
Issues and proposed changes ('pull requests' in git terminology, but referred to as 'diffs' in Phabricator) are tracked in a tool called [[QA/Phabricator|Phabricator]] (Fedora QA instance [https://phab.qa.fedoraproject.org/ here]). You can submit diffs using a tool called {{command|arcanist}}. Please see the [[QA:Taskotron contribution guide|contribution guide]] for detailed instructions and the full list of repositories and Phabricator projects.
+
Contributors could use the [[Taskotron contribution guide|contribution guide]].
  
The main mailing list for Taskotron discussion is {{fplist|qa-devel}}. The main IRC channel is {{fpchat|#fedora-qa}}.
+
The main mailing list for Taskotron discussion was {{fplist|qa-devel}}. The main IRC channel was {{fpchat|#fedora-qa}}.
  
 
== Documentation and further reading ==
 
== Documentation and further reading ==
  
Please see the [https://qa.fedoraproject.org/docs/libtaskotron/latest/quickstart.html Libtaskotron quick start] and the [https://qa.fedoraproject.org/docs/libtaskotron/latest/ Taskotron documentation]. You may also find this further reading of interest:
+
There was [https://qa.fedoraproject.org/docs/libtaskotron/latest/quickstart.html Libtaskotron quick start] and [https://qa.fedoraproject.org/docs/libtaskotron/latest/ Taskotron documentation]. You may also find this further reading of interest:
  
 
* [[User:Tflink/taskotron development plan]]
 
* [[User:Tflink/taskotron development plan]]

Latest revision as of 14:59, 7 May 2020

Stop (medium size).png
Taskotron development reached end of life
Taskotron has been sunset in Fedora Infrastructure. It is no longer running and no longer being developed. You can use these wiki pages to learn about its history, but please be aware that the information is no longer actual.
Idea.png
ResultsDB is still operational
Even when Taskotron is EOL, ResultsDB is still being used. You can use our simple web frontend to explore the production instance.

Overview

Taskotron was a framework for automated task execution. It ran selected package checks in Fedora.

Some of its major envisioned features:

  • Support for distribution-wide checks - e.g. Can this set of packages be pushed to stable updates repository? or Is this new system compose installable?
  • Support for package-related checks - e.g. Can this new build of firefox package be safely updated? or Do the functional tests pass for this new build of openssh?
  • Simple check management - package maintainers in full control of their package-related checks, no hurdles
  • Event-based - where applicable only the simplest interaction between services is used - passing messages through a message bus - for both check triggering and result reporting. No hardcoded tie-ins to specific services.
  • Decoupled design - comprised of loosely-coupled standalone units (tools, libraries) so that important logical functions are separated and one unit can be replaced with a different unit with similar functionality
  • Trivial local execution - no need to replicate the production environment with all its servers and configurations, the check authors can easily run and develop their checks on their local machine with no unnecessary software setup hassle
  • Useful for other Linux distributions as well, not just Fedora

Source code, getting involved and contributing

Taskotron consisted of multiple separate components, mainly hosted in the taskotron namespace in Pagure. The general tasks that were developed along with Taskotron were named with the task- prefix.

Contributors could use the contribution guide.

The main mailing list for Taskotron discussion was qa-devel. The main IRC channel was #fedora-qa[?].

Documentation and further reading

There was Libtaskotron quick start and Taskotron documentation. You may also find this further reading of interest: