[GitHub] [incubator-devlake] Startrekzky commented on issue #5633: [Feature][Jenkins-Data] Jenkins plugin option to add all the multibranch job to be monitored

["Startrekzky (via GitHub)" <gi...@apache.org>]

Startrekzky commented on issue #5633:
URL: https://github.com/apache/incubator-devlake/issues/5633#issuecomment-1722726123

   > Yes, as an example I have a multi branch job in jenkins, which inside It executes multiple separated pipelines, these pipelines are created on demand as we create pull requests in github but the issue related to devlake is that the pipelines that are generated on demand are not triggered automatically by the jenkins connection in devlake
   
   Hi @KrPetrovDev , may I ask are there any rules for the naming, folder structure, or other patterns of the auto-created Jenkins jobs in the pipelines?
   
   Currently, DevLake needs users to define the `data scope` with the `absolute data scope id` before collecting data, which is the `Jenkins job path` in this case. 
   
   @klesh If the on-premise-created Jenkins jobs follow certain rules, I guess the possible solution is to allow users to input a pattern (regex) to define the `relative data scope pattern` to collect.
   
   Then this issue would be similar to https://github.com/apache/incubator-devlake/issues/5002
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org