[BUG] [Plugin CI] OS artifacts not updated immediately in Github runners resulting in blocked plugin CI

[DarshitChanpura]

Describe the bug
Security Plugin CI failed due to a breaking change introduced in core via opensearch-project/OpenSearch#6009. An PR with the fix was pushed via opensearch-project/security#2418 but the CI failed because the change expected latest artifact to be updated with commit f9eb9bfe17b71aae7e2a00ac0337909f1b3e61e7, but it wasn't.

Here is a task from the failing CI build: https://github.com/opensearch-project/security/actions/runs/4019330649/jobs/6907961463

As a side effect, an auto-cut issue was created because OS distribution build with security plugin failed due to toStrings() signature change not being addressed, even though the fix was available to be merged in time.

Is there a feasible way we can get CI runners updated with latest artifacts as soon as possible to avoid this scenario in future?

Related to opensearch-project/security#2276

Update: As of now CI in unblocked. Seems like the Github runners have updated artifact.

Expected behavior
Github runners should have latest artifacts, so CI is not blocked.

Plugins
Security

[minalsha]

@bbarani could you please look into this issue? From OpenSearch Core side, our build is successful but snapshots are stale. Thank you.

[zelinh]

It looks like our check-for-build is currently failing because of a syntax error in this PR. #3149
Working on a quick fix.

[bbarani]

@DarshitChanpura I am closing this issue as the workflows has started publishing snapshot artifacts for 3.x now. Feel free to re-open if you still have any issues.

[DarshitChanpura]

Related: #3199