Scan Multibranch Pipeline Log

Started by user Administrator
[Thu Feb 08 08:44:52 UTC 2024] Starting branch indexing...
 > git --version # timeout=10
 > git --version # 'git version 2.39.2'
using GIT_SSH to set credentials bitbucket access
[INFO] Currently running in a labeled security context
 > /usr/bin/chcon --type=ssh_home_t /tmp/jenkins-gitclient-ssh6174983307507994632.key
Verifying host key using known hosts file, will automatically accept unseen keys
 > git ls-remote --symref -- git@bitbucket.org:aquila-consortium/borg_conda # timeout=10
 > git rev-parse --resolve-git-dir /var/jenkins_home/caches/git-7dc371ab4b4dd6298effcf1f576dd9c5/.git # timeout=10
Setting origin to git@bitbucket.org:aquila-consortium/borg_conda
 > git config remote.origin.url git@bitbucket.org:aquila-consortium/borg_conda # timeout=10
Fetching & pruning origin...
Listing remote references...
 > git config --get remote.origin.url # timeout=10
 > git --version # timeout=10
 > git --version # 'git version 2.39.2'
using GIT_SSH to set credentials bitbucket access
[INFO] Currently running in a labeled security context
 > /usr/bin/chcon --type=ssh_home_t /var/jenkins_home/caches/git-7dc371ab4b4dd6298effcf1f576dd9c5@tmp/jenkins-gitclient-ssh8669979849831164020.key
Verifying host key using known hosts file, will automatically accept unseen keys
 > git ls-remote -h -- git@bitbucket.org:aquila-consortium/borg_conda # timeout=10
Fetching upstream changes from origin
 > git config --get remote.origin.url # timeout=10
using GIT_SSH to set credentials bitbucket access
[INFO] Currently running in a labeled security context
 > /usr/bin/chcon --type=ssh_home_t /var/jenkins_home/caches/git-7dc371ab4b4dd6298effcf1f576dd9c5@tmp/jenkins-gitclient-ssh17161446815175512846.key
Verifying host key using known hosts file, will automatically accept unseen keys
 > git fetch --tags --force --progress --prune -- origin +refs/heads/*:refs/remotes/origin/* # timeout=10
Checking branches...
  Checking branch release/3.3
      ‘Jenkinsfile’ found
    Met criteria
Scheduled build for branch: release/3.3
  Checking branch release/3.2
      ‘Jenkinsfile’ found
    Met criteria
Changes detected: release/3.2 (6bc5c7efc27158f28a60fee3121a1f248f168c7b → 517061741305b053d6d8fae05a95a4accee4f638)
Scheduled build for branch: release/3.2
  Checking branch release/3.1
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: release/3.1 (still at 4dbb247d1b6cfd2fccdcf7872e816fd26c085095)
  Checking branch release/3.0
      ‘Jenkinsfile’ found
    Met criteria
No changes detected: release/3.0 (still at 0ea341081d3ac612a40736842c0f4358e90a9400)
  Checking branch main
      ‘Jenkinsfile’ found
    Met criteria
Changes detected: main (abb4bbdbbfda45c18a81fb095af93a865441d6af → 2217fe6b1574d6ea99c64b0aa7ea9cf611eabe71)
Scheduled build for branch: main
Processed 6 branches
[Thu Feb 08 08:44:57 UTC 2024] Finished branch indexing. Indexing took 5.4 sec
Finished: SUCCESS