Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Feature][Gitlab job] gitlab trigger job bridge as job for Scope Config #6576

Closed
2 of 3 tasks
clement-igonet opened this issue Dec 6, 2023 · 3 comments
Closed
2 of 3 tasks

[Feature][Gitlab job] gitlab trigger job bridge as job for Scope Config #6576

clement-igonet opened this issue Dec 6, 2023 · 3 comments
Labels
type/duplicated duplicated issues type/feature-request This issue is a proposal for something new

Comments

@clement-igonet
Copy link

Search before asking

  • I had searched in the issues and found no similar feature requirement.

Use case

In the CI/CD deployment setup, we can set job name in order to define what to consider as a DevLake Deployment.

However, gitlab CI/CD can also have trigger job (useful to delegate deployment part) that are seen as "bridge" in gitlab API.

Description

Gitlab bridge trigger job type should be also collected as any other job to identify a deployment job.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct
@clement-igonet clement-igonet added the type/feature-request This issue is a proposal for something new label Dec 6, 2023
@clement-igonet clement-igonet changed the title [Feature][Gitlab job] Add gitlab trigger job (bridge) as job for Scope Config [Feature][Gitlab job] gitlab trigger job bridge as job for Scope Config Dec 6, 2023
@abeizn
Copy link
Contributor

abeizn commented Dec 7, 2023

@Startrekzky

@clement-igonet
Copy link
Author

Maybe a clone of #6135

@d4x1
Copy link
Contributor

d4x1 commented Dec 11, 2023 •
edited
Loading

Maybe a clone of #6135

Yes it's duplicated. Let's move to the original issue for further discussion.

@d4x1 d4x1 added the type/duplicated duplicated issues label Dec 11, 2023
@d4x1 d4x1 closed this as completed Dec 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type/duplicated duplicated issues type/feature-request This issue is a proposal for something new
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@d4x1 @clement-igonet @abeizn