You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@devlake.apache.org by kl...@apache.org on 2022/11/07 07:46:17 UTC
[incubator-devlake-website] branch kw-devlake-3468-plugin-blueprint updated (d011d248a -> 4962cd427)
This is an automated email from the ASF dual-hosted git repository.
klesh pushed a change to branch kw-devlake-3468-plugin-blueprint
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
discard d011d248a docs: remove detailed information for PluginBlueprint interface
omit 8319892de fix: broken link for gitextractor
omit b72ec82b8 docs: add PluginBlueprint doc for Developer
add 82e4f38c5 docs: update migration interface (#299)
add 5d38f309e docs: add PluginBlueprint doc for Developer (#300)
add 0eb615ec9 docs: add config ui availability (#302)
add e5409a9a6 docs: add doc for invoking Bitbucket plugin through API (#303)
add 6f2e58510 Update helm deployment (#306)
add 53fa743bf doc: added bitbucket doc to v0.14
add ce842c47a Update bitbucket.md
add 917b5f0cf Update bitbucket.md
add 1a77185bb Update bitbucket.md
add 34ca26783 docs: fix missing '>' in domain layer schema (#309)
add 72d137d3d update pr deploy time
add 260e73916 docs: add scope for jenkins; fix some other some question
add 01825ba38 fix: fix for review
new 4962cd427 docs: remove detailed information for PluginBlueprint interface
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d011d248a)
\
N -- N -- N refs/heads/kw-devlake-3468-plugin-blueprint (4962cd427)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docs/DataModels/DevLakeDomainLayerSchema.md | 20 +++---
docs/DeveloperManuals/PluginImplementation.md | 2 +-
docs/GettingStarted/HelmSetup.md | 4 +-
docs/Metrics/DeployTime.md | 21 +++++-
docs/Metrics/LeadTimeForChanges.md | 19 ++---
docs/Plugins/bitbucket.md | 77 +++++++++++++++++++++
docs/Plugins/jenkins.md | 3 +-
docs/SupportedDataSources.md | 28 ++++----
docs/UserManuals/ConfigUI/GitHub.md | 3 +-
docs/UserManuals/ConfigUI/GitLab.md | 12 ++--
docs/UserManuals/ConfigUI/Jenkins.md | 13 +++-
static/img/Metrics/pr-commit-deploy.jpeg | Bin 0 -> 269913 bytes
.../img/Metrics/pr-commit-deployment-relation.png | Bin 0 -> 4857 bytes
.../DataModels/DevLakeDomainLayerSchema.md | 20 +++---
.../DataModels/DevLakeDomainLayerSchema.md | 20 +++---
.../DataModels/DevLakeDomainLayerSchema.md | 20 +++---
.../version-v0.14/GettingStarted/HelmSetup.md | 45 ++++++++++--
versioned_docs/version-v0.14/Plugins/bitbucket.md | 77 +++++++++++++++++++++
18 files changed, 295 insertions(+), 89 deletions(-)
create mode 100644 docs/Plugins/bitbucket.md
create mode 100644 static/img/Metrics/pr-commit-deploy.jpeg
create mode 100644 static/img/Metrics/pr-commit-deployment-relation.png
create mode 100644 versioned_docs/version-v0.14/Plugins/bitbucket.md
[incubator-devlake-website] 01/01: docs: remove detailed information for PluginBlueprint interface
Posted by kl...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
klesh pushed a commit to branch kw-devlake-3468-plugin-blueprint
in repository https://gitbox.apache.org/repos/asf/incubator-devlake-website.git
commit 4962cd427a23eabbfad4b95068ffa3ea96d2ce78
Author: Klesh Wong <zh...@merico.dev>
AuthorDate: Mon Nov 7 15:03:56 2022 +0800
docs: remove detailed information for PluginBlueprint interface
---
docs/DeveloperManuals/PluginImplementation.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/DeveloperManuals/PluginImplementation.md b/docs/DeveloperManuals/PluginImplementation.md
index 01ee505b5..0f1d3dd55 100644
--- a/docs/DeveloperManuals/PluginImplementation.md
+++ b/docs/DeveloperManuals/PluginImplementation.md
@@ -37,7 +37,7 @@ A plugin mainly consists of a collection of subtasks that can be executed by Dev
4. [PluginApi](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_api.go) lets a plugin exposes some self-defined APIs
5. [PluginMigration](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_migration.go) is where a plugin manages its database migrations
6. [PluginModel](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_model.go) allows other plugins to get the model information of all database tables of the current plugin through the GetTablesInfo() method.If you need to access Domain Layer Models,please visit [DomainLayerSchema](https://devlake.apache.org/docs/DataModels/DevLakeDomainLayerSchema/)
-7. [PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_blueprint.go) is the foundation for Blueprint and Plugin to collaborate to generate a reasonable Pipeline Plan based on User Settings, for example, users may declare that he wanted to collect data from a Github Repo, it implies not only the issues/prs, but also the git-meta-data including commits history, branches, tags, etc, in order to do it and do it fast, leveragin [GitExtractor](../Plugins [...]
+7. [PluginBlueprint](https://github.com/apache/incubator-devlake/blob/main/plugins/core/plugin_blueprint.go) is the foundation for Blueprint and Plugin to collaborate to generate a reasonable Pipeline Plan based on User Settings, for example, users may declare that he wanted to collect data from a Github Repo, it implies not only the issues/prs, but also the git-meta-data including commits history, branches, tags, etc, in order to do it and do it fast, leveraging [GitExtractor](../Plugin [...]
The diagram below shows the control flow of executing a plugin: