[Bug]: Created AUTOCUT issues does not honor windows failure

[prudhvigodithi]

Describe the bug

Notice the following screenshots, even though the build failed for windows with error Error building OpenSearch-Dashboards, retry with: ./build.sh manifests/3.0.0/opensearch-dashboards-3.0.0.yml --component OpenSearch-Dashboards

subprocess.CalledProcessError: Command 'bash C:\Users\Administrator\jenkins\workspace\distribution-build-opensearch-dashboards\scripts\components\OpenSearch-Dashboards\build.sh -v 3.0.0 -p windows -a x64 -d zip -s false -o builds' returned non-zero exit status 1.

It still says Component OpenSearch-Dashboards passed, closing github issue

To reproduce

Here is the build failure log. https://build.ci.opensearch.org/blue/organizations/jenkins/distribution-build-opensearch-dashboards/detail/distribution-build-opensearch-dashboards/7008/pipeline/76/

Expected behavior

No response

Screenshots

If applicable, add screenshots to help explain your problem.

Host / Environment

No response

Additional context

No response

Relevant log output

No response

[gaiksaya]

[Triage] Need to check logic for windows issue creation for OpenSearch-Dashboards

[rishabh6788]

@prudhvigodithi @gaiksaya Is this happening for each run?

[rishabh6788]

The issue is coming from here. In the example mentioned above OSD for only windows stage failed due to permission issues, the rest built successfully. Since the post stage process logs from all the stages it was able to find Successfully built string for OSD from other stages and closed the issue. Till we stabilize windows env better we exclude windows platform from all the post process scripts. @gaiksaya @prudhvigodithi