Create elastic-agent-pull-requests.yml

[jlind23]

Automatically move PR to an Elastic Agent board as soon as they are labelled with either "team:elastic-agent-control-plane" or "team:elastic-agent-data-plane".

[mergify]

This pull request does not have a backport label. Could you fix it @jlind23? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

• backport-v./d./d./d is the label to automatically backport to the 7./d branch. /d is the digit

NOTE: backport-skip has been added to this pull request.

[elasticmachine]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Reason: null

• Start Time: 2022-02-04T08:39:14.432+0000

• Duration: 14 min 29 sec

• Commit: c8ff94b

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[ph]

Not completely familiar with github action but the graphql looks good.

[jlind23]

@v1v this beats-ci/pr-merge seems to fail because there is no changes made to the code base. Shouldn't we exclude some repositories from the check?

[jlind23]

@ph if you want give a try at a graphql request, github offers this: https://graphql.github.com/

[ruflin]

@jlind23 I wonder why the action to add it to the Data plane board was skipped?

[ruflin]

Nit: If you shorten the title, this looks more descriptive.

[jlind23]

Yup it keeps only the last run in it.

[jlind23]

@ruflin it was not. Each labelling generate an event on github side which then generate a github action run.
2 labels means two runs. If you check each one of those you will find both condition being succesful.

[ruflin]

/test

[ruflin]

Triggering the tests again as it seems it was aborted (manually?)

[v1v]

@v1v this beats-ci/pr-merge seems to fail because there is no changes made to the code base. Shouldn't we exclude some repositories from the check?

@jlind23 , as far as I see there were two consecutive commits and the on-going builds were killed for the new one. That's the existing approach since the very beginning.

If you click on #30177 (comment) you can see the previous build results. The comment contains as much details as possible regarding the build status. Let me know if that message is not clear and we can change it

If no code changes, then only the linting is validated, we could exclude the .github folder, but for simplicity I'd rather prefer to run a basic linting than adding more complexity in the CI.

What do you think?

[jlind23]

@v1v basic linting suits me well then. I am for reducing the complexity too.

[cmacknz]

I think this is causing some CI failures because GITHUB_TOKEN is missing, example: https://github.com/elastic/beats/runs/5098115833?check_suite_focus=true