Skip to content

Fix status checks#1376

Merged
reakaleek merged 3 commits intoelastic:mainfrom
reakaleek:feature/fix-status-checks
Jun 13, 2023
Merged

Fix status checks#1376
reakaleek merged 3 commits intoelastic:mainfrom
reakaleek:feature/fix-status-checks

Conversation

@reakaleek
Copy link
Member

@reakaleek reakaleek commented Jun 13, 2023

Details

Only docs PR cannot be merged because the Lint status check is not created.
However, the all status check is created because of the ci-docs.yml workflow.

Reference: #1375 (comment)

This PR create a single status check named all in both only-docs and code changes which can then be set as required.

To Do

Adjust branch protection rules shortly before merging:

  • Add all as required status check
  • Remove Lint as required status check

@reakaleek reakaleek requested review from a team, bmorelli25 and vigneshshanmugam June 13, 2023 20:10
@reakaleek reakaleek mentioned this pull request Jun 13, 2023
@reakaleek reakaleek marked this pull request as ready for review June 13, 2023 20:15
@reakaleek
Copy link
Member Author

@amannocci any clue why Lint is failing here?

@amannocci
Copy link
Contributor

Since this is a forked PR, the token provided doesn't allow to write the commit status.
@reakaleek

@reakaleek
Copy link
Member Author

reakaleek commented Jun 13, 2023

Since this is a forked PR, the token provided doesn't allow to write the commit status. @reakaleek

Ah, yeah right.

We need to support PRs from forks.
I will comment it out for now and can you then fix this in a follow-up? You have the context and are more suitable.

WDYT?

Thank you!

@reakaleek
Copy link
Member Author

jenkins test this please

@reakaleek
Copy link
Member Author

reakaleek commented Jun 13, 2023

@cachedout

the elasticsearch-ci/docs status check is not created, but the jenkins job that should create it was successful.

However, there is an error message in the end:

23:02:02 Using context: elasticsearch-ci/docs
23:02:02 FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo.
23:02:02 org.kohsuke.github.GHFileNotFoundException: https://api.github.com/repos/elastic/apm-agent-rum-js/statuses/cfc0754e0cc22589cd413fc4efdd566f2130d146 {"message":"Not Found","documentation_url":"https://docs.github.com/rest/commits/statuses#create-a-commit-status"}

Also happens on other PRs.

Do you think this is related to role changes?

// Update:

I added elasticsearchmachine to collaborators and the status check is now created again.

@reakaleek
Copy link
Member Author

jenkins test this please

@reakaleek reakaleek merged commit 0f40176 into elastic:main Jun 13, 2023
@reakaleek reakaleek deleted the feature/fix-status-checks branch June 13, 2023 21:37
@cachedout
Copy link
Contributor

cachedout commented Jun 14, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants