-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature][Jenkins] Investigate and implement Jenkins Action #2637
Labels
type/feature-request
This issue is a proposal for something new
Comments
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Jul 30, 2022
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Jul 30, 2022
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Jul 30, 2022
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Jul 30, 2022
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Aug 1, 2022
warren830
added a commit
to merico-dev/lake
that referenced
this issue
Aug 1, 2022
add builds_triggered builds and up_down_jobs closes apache#2637
abeizn
pushed a commit
to merico-dev/lake
that referenced
this issue
Aug 3, 2022
add builds_triggered builds and up_down_jobs closes apache#2637
abeizn
pushed a commit
that referenced
this issue
Aug 3, 2022
add builds_triggered builds and up_down_jobs closes #2637
3 tasks
closed by mistake, reopened |
This was referenced Aug 4, 2022
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Description
According to issue #2537 , Before this, we need to investigate Jenkins
Actions and write a table schema in this issue.
Use case
We need to investigate Jenkins Actions first, and try to implement collector and extractor.
Then we can compare several CI/CD plugins' tool layers and go back to work on #2537
After domain layer design, we can continue to finish this issue
Related issues
No response
Are you willing to submit a PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: