Added a Release task for the Jenkins plugin for scan multibranch.
This is to triggrer the build job without the branch name but this logs are Jobbuildname/indexing

by: de monplanet c. | 10 months ago | Integrations

Comments

• Could you provide additional details regarding the use case, particularly regarding the structure of job builds and branch organization?
  Additionally, could you elaborate on the parameters or attributes employed to initiate these builds?

  by: DevOps Product tram | 9 months ago

  official response

• A build Jenkins can be a 'Multibranch pipeline'.
  That it is connect to the repo git with more than one branch.
  When the devolopper creates a new branch on the repo git.
  There is a link 'scan mltibranch' on jenkins ui on the root path of build jenkins.
  Our use case is a CI worflow defined in Release.
  This action must be automated in Release for the workflow to continue.
  No interruption for this manual action in jenkins.
  
  When Release launches a new build Jenkins with specific branch, it execute this url
  Jenkins_server/job/JOBNAME/job/Branch
  and parse the log
  Jenkins_server/job/JOBNAME/job/Branch/BUILDNUMBER/api/json?depth=0&tree=name....
  for scan mltibranch
  Jenkins_server/job/JOBNAME
  and parse log
  Jenkins_server/job/JOBNAME/indexing/consoleText --> the line last one it is result.

  by: de monplanet c. | 9 months ago

• We are planning to implement this as part of the upcoming Fuji release. We will share updates via Early Access releases for your feedback.

  by: DevOps Product team | 8 months ago

  official response

• This change is available in 24.3 release.

  by: DevOps Product team | about a month ago

  official response