Default not to create/update issues during integration test runs

[peternied]

Description

In Security we are getting spammed from the concurrent-search-test integration runs. Since I do not plan on supporting runs on this flavor of build I don't want to get issues in our codebase for it.

Note; I'm happy to have issues filed once they've been root caused and our team is at issue, but non-standard builds are not supported by our project and it creates noise.

Issues Resolved

• Related [AUTOCUT] Integration Test failed for security: 2.12.0 tar distribution security#3876

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (810f742) 91.27% compared to head (b3bec56) 91.27%.
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #4323   +/-   ##
=======================================
  Coverage   91.27%   91.27%           
=======================================
  Files         189      189           
  Lines        6163     6163           
=======================================
  Hits         5625     5625           
  Misses        538      538           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[gaiksaya]

Default it to false maybe?

[peternied]

This is the distribution build job - we want it to keep sending notifications, no? Are any 'unsupported' jobs run with this task?

[gaiksaya]

Sorry missed the fact that this is a distribution build job. I think we might re-think the logic once #4301 feature support is added.

[gaiksaya]

Thanks for adding this.

[peternied]

@gaiksaya Looks like I see another notification [1] from last nights scheduled run. Taking a quick peak at a recent run's logs [2] [3], I don't see the new parameters - is there anything that needs to be done to deploy this change?

• [1] Notification from cron scheduled concurrent-search integ-test [AUTOCUT] Integration Test failed for security: 2.12.0 tar distribution security#3876 (comment)
• [2] Distribution triggered integ-test job ~1 hour ago, +14 hours after this PR was merged https://build.ci.opensearch.org/blue/organizations/jenkins/integ-test/detail/integ-test/6894/pipeline
• [3] Pipeline log - shows parameters https://build.ci.opensearch.org/blue/rest/organizations/jenkins/pipelines/integ-test/runs/6894/log/?start=0

[prudhvigodithi]

Hey @peternied works as expected based on you change right?, I did notice the integ test 6894 has the parameter UPDATE_GITHUB_ISSUES as the upstream job is distribution build https://build.ci.opensearch.org/job/distribution-build-opensearch/9143 where UPDATE_GITHUB_ISSUES is defaulted to true.