-
Notifications
You must be signed in to change notification settings - Fork 119
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.
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
[develop] Fix for SonarQube forked repo renaming failure #1115
[develop] Fix for SonarQube forked repo renaming failure #1115
Conversation
The Fundamental WE2E tests were successfully run on Hera:
Launching Jenkins tests to ensure updates for |
Keeping echo statements in to print to the jenkins log so the two jobs can more easily be tracked together |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the ufs-srw_sonarqube/174, the issue in Clone Sources
has been addressed.
Approving PR now.
DESCRIPTION OF CHANGES:
SonarQube job fails to find user's repository if they rename when creating a fork, this change to the Jenkinsfile will pass the user's url to the SonarQube job so that it doesn't have to form the URL itself. Also passes change ID (PR number) so that information on the SonarQube job can be archived to s3 and properly aligned with the corresponding PR
Type of change
TESTS CONDUCTED:
CHECKLIST
LABELS (optional):
A Code Manager needs to add the following labels to this PR:
CONTRIBUTORS (optional):