[Guide] Advanced Index Actions

[nhtruong]

Create guides/advanced_index_actions.md similar to the Ruby guide

You must assure that:

• All code-blocks, when run from start to finish in order they appear in the guide, do not throw any errors. If you want to demonstrate that certain statements will throw errors, they must be wrapped in a try/catch and print out the expected error.
• All code-blocks are properly marked with the language it's written in (i.e. ```ruby)
• The instructions, though mostly identical to the Ruby guide, are suitable for this repo.

[gaiksaya]

Hi @jmazanec15 ,

We are creating a generic autocut failure issues for all platforms/architectures combinations. It would be difficult to parse the all stages and get specific failure. Currently, the logic is even if we find one Error building string, it would create an issue for that component.

I believe, along with the workflow run, it would be helpful to provide specific node raw logs. Example: https://build.ci.opensearch.org/blue/rest/organizations/jenkins/pipelines/distribution-build-opensearch/runs/9674/nodes/72/steps/491/log/?start=0

What do you think?

P.S: I am not sure if it possible to get this URL dynamically.

[jmazanec15]

But if we can find the "Error building" string, couldnt we get the logs? For instance, dont we run ./gradlew integTest? Can we capture the exit code and check and cut issue based on that?

Raw node logs would also be helpful

[zelinh]

Right now for test workflow, we are using report workflow to generate a test-report including all the logs from the testing. We can have a build_recorder similar to the test_recorder (https://github.com/opensearch-project/opensearch-build/tree/main/src/test_workflow/test_recorder) so that we could enhance current report workflow to create reports for building workflow as well.

[peterzhuamazon]

[Triage] We can think of other ways to solve this such as:

• Adding a tee to each gradle/yarn build command in build.sh > into a specific plugin named log file
• Attach the log as part of the jenkins run
• Add the log url as part of the description/comment of the github issue.

Thanks.

[Swiddis]

Can I get this assigned to me?

[peterzhuamazon]

Thanks @Swiddis contribution.