search

apache / incubator-devlake

Apache DevLake is an open-source dev data platform to ingest, analyze, and visualize the fragmented data from DevOps tools, extracting insights for engineering excellence, developer experience, and community growth.
https://devlake.apache.org/
Apache License 2.0
2.58k stars 518 forks source link

[Bug] Jenkins build name populating as the job name itself instead of the actual build name #7083

Open prateekj201 opened 7 months ago

prateekj201 commented 7 months ago

Search before asking

What happened

if using currentBuild.displayName to change the build name for any job, devlake table _tool_jenkins_stages shows build_name as the job name itself instead of the custom build name being set. Also, "{jenkins_url}/job/{JobName}/api/json" shows job name instead of custom build name which could be causing this

What do you expect to happen

build_name in _tool_jenkins_stages to be as custom build name being populated as per job configuration

How to reproduce

use currentBuild.displayName to change the build name for any job to reproduce this

Anything else

No response

Version

Apache 2.0 License v0.19.0@

Are you willing to submit PR?

Code of Conduct

d4x1 commented 7 months ago

IMO, the best way is DevLake provides some an option with a default rule in scope config , and user can change it manually.

@Startrekzky

Startrekzky commented 7 months ago

@d4x1 A configuration to let users decide the assignment logic of the Jenkins build_name?

d4x1 commented 7 months ago

@d4x1 A configuration to let users decide the assignment logic of the Jenkins build_name?

Yes.

github-actions[bot] commented 3 months ago

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

github-actions[bot] commented 1 month ago

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.