Google Git
Sign in
apache/devlake/869256888618c315fb03f1a267add37bdd662efd
commit
869256888618c315fb03f1a267add37bdd662efd
[log]
author
Klesh Wong <klesh@qq.com>
Fri Sep 04 17:44:15 2026 +0800
committer
GitHub <noreply@github.com>
Fri Sep 04 17:44:15 2026 +0800
tree
06862facfb88abe16cf2ce4061d7ba6a3b9fd52a
parent
e355317df1f1d40af094d5e9c63d7dc9b5530f83 [diff]
chore(python): deprecate Python plugin framework (PyDevLake) (#9097)

Phase 1 of the deprecation plan in #9092. Adds deprecation warnings across
the codebase to inform users that the Python plugin framework will be
removed in 3 months in favor of Go-based plugins.

Changes:
- backend/python/README.md: add DEPRECATED banner + migration guidance
- backend/python/plugins/azuredevops/README.md: mark plugin deprecated,
  point users to azuredevops_go
- backend/core/runner/loader.go: emit a WARN log line at server startup
  when remote (Python) plugins are being loaded
- backend/core/plugin/plugin_meta.go: add PluginDeprecation interface
- backend/server/services/remote/plugin/plugin_impl.go: implement
  PluginDeprecation on RemotePlugin so all Python plugins are flagged
- backend/server/api/plugininfo/plugininifo.go: expose  field
  on GET /plugins so config-ui can detect deprecated plugins
- config-ui: add isDeprecated/deprecationMessage to IPluginConfig, mark
  the azuredevops (Python) plugin deprecated, and render a 'Deprecated'
  badge + message in the Connections page
10 files changed
tree: 06862facfb88abe16cf2ce4061d7ba6a3b9fd52a
  1. .devcontainer/
  2. .github/
  3. backend/
  4. config-ui/
  5. devops/
  6. e2e/
  7. grafana/
  8. resources/
  9. tools/
  10. .asf.yaml
  11. .codespellrc
  12. .dockerignore
  13. .editorconfig
  14. .gitattributes
  15. .gitignore
  16. .licenserc.yaml
  17. AGENTS.md
  18. DISCLAIMER
  19. docker-compose-dev-mysql.yml
  20. docker-compose-dev-postgresql.yml
  21. docker-compose.datasources.yml
  22. env.example
  23. LICENSE
  24. Makefile
  25. NOTICE
  26. README.md
README.md

Apache DevLake

PRs Welcome Dockerhub pulls unit-test Go Report Card Slack Twitter

🤔 What is Apache DevLake?

Apache DevLake is an open-source dev data platform that ingests, analyzes, and visualizes the fragmented data from DevOps tools to extract insights for engineering excellence, developer experience, and community growth.

Apache DevLake is used by Engineering Leads, Open Source Software Maintainers and development teams looking to make better sense of their development process and to bring a more data-driven approach to their own practices. You can ask Apache DevLake many questions regarding your development process. Just connect and query.

🎯 What can be accomplished with Apache DevLake?

  1. Your Dev Data lives in many silos and tools. DevLake brings them all together to give you a complete view of your Software Development Life Cycle (SDLC).
  2. From DORA to scrum retros, DevLake implements metrics effortlessly with prebuilt dashboards supporting common frameworks and goals.
  3. DevLake fits teams of all shapes and sizes, and can be readily extended to support new data sources, metrics, and dashboards, with a flexible framework for data collection and transformation.

👉 Live Demos

The main way you interact with DevLake is through the integrated dashboards powered by Grafana.

Live DORA Dashboard

Dashboards for Engineering Leads

Dashboards for OSS Maintainers

💪 Supported Data Sources

DevLake supports connections to many popular development tools, including GitHub, GitLab, Jenkins, Jira, Sonarqube and more. Here you can find all data sources supported by DevLake, their scopes, supported versions and more!

🚀 Getting Started

Installation

You can set up Apache DevLake by following our step-by-step instructions for either Docker Compose or Helm. Feel free to ask the community if you get stuck at any point.

🤓 Usage

Please see detailed usage instructions. Here's an overview on how to get started using DevLake.

1. Set up DevLake

Install using either Docker Compose or Helm.

2. Create a Blueprint

The DevLake Configuration UI will guide you through the process (a Blueprint) to define the data connections, data scope, transformation and sync frequency of the data you wish to collect.

3. Track the Blueprint's progress

You can track the progress of the Blueprint you have just set up.

4. View the pre-built dashboards

Once the first run of the Blueprint is completed, you can view the corresponding dashboards.

5. Customize the dashboards with SQL

If the pre-built dashboards are limited for your use cases, you can always customize or create your own metrics or dashboards with SQL.

Contributing

Please read the contribution guidelines before you make contribution. The following docs list the resources you might need to know after you decided to make contribution.

👩🏾‍💻 Contributing Code

If you plan to contribute code to Apache DevLake, we have instructions on how to get started with setting up your Development environemtn.

📄 Contributing Documentation

One of the best ways to get started contributing is by improving DevLake's documentation.

⌚ Roadmap

  • Roadmap: Detailed roadmaps for DevLake.

💙 Community

Message us on Slack

📄 License

This project is licensed under Apache License 2.0 - see the LICENSE file for details.