Skip to content

Conversation

@aaron-congo
Copy link
Contributor

@aaron-congo aaron-congo commented Jun 13, 2025

Minor Blue/Green fixes

  • adds null/empty checks
  • adds some local variables to reuse retrieved values that have been verified to be non-empty/non-null
  • fixes a minor bug where the wrong key was being used to add some B/G logging info
  • fixes incorrect threadFinishCount in BlueGreenDeploymenTests#testSwitchover
  • IT tests: skip de-authorization of IP and deletion of DB cluster parameter group if REUSE_RDS_DB=true

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions
Copy link

github-actions bot commented Jun 13, 2025

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

  1. Register at Qodana Cloud and configure the action
  2. Use GitHub Code Scanning with Qodana
  3. Host Qodana report at GitHub Pages
  4. Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/[email protected]
        with:
          upload-result: true
Contact Qodana team

Contact us at [email protected]

@sergiyvamz sergiyvamz changed the title fix: minor Blue/Green F fix: minor Blue/Green fixes Jun 13, 2025
@aaron-congo aaron-congo marked this pull request as ready for review July 3, 2025 18:46
if (conn == null) {

this.bgStatus = this.pluginService.getStatus(BlueGreenStatus.class, this.bgdId);
if (this.bgStatus == null) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this.endTimeNano won't be set up in such case.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it will, when the return statement is hit we will automatically enter the finally block which sets the endTimeNano if it hasn't been set yet. But let me know if I'm incorrect

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Then the measured time includes an actual connect time. Original idea was to measure that routing time. If it's easy to fix I'd prefer just routing time.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, okay I've updated the code to set the end time before connecting

@aaron-congo aaron-congo merged commit 3e52577 into main Jul 4, 2025
6 of 7 checks passed
@aaron-congo aaron-congo deleted the bg-fixes branch July 4, 2025 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants