Repository navigation
Move environment version check out of PR CI #7628
Description
Not a real issue, here i think that the CI Self Check is too restrictive.
A contributor will face to environment issue completely not related to his PR. I've an example on my last PRs
- fix: unable to use objectId size higher than 19 on GraphQL API #7627
- refactor: minor changes to remove mongo deprecation warnings #7626
I think CI Self check is useful but not on a pull request event.
I suggest here to switch the CI Self Check on weekly github action to ensure that CI env is up to date as much as possible.
What do you think @mtrezza ?
Activity
parse-github-assistant commentedon Oct 14, 2021
Thanks for opening this issue!
mtrezza commentedon Oct 14, 2021
Yes, this was discussed internally when we introduced the environment check. The goal was to automatically open a PR that already bumps everything, so it only needs to be reviewed, once we have a concept for release automation. I think we are almost there now.
The CI Self Check does more than only check for environment versions, so we would not move the whole check into a separate PR but keep some parts in the CI.
For now, the contributor can just ignore the check.
[-]May be remove ci / CI Self-Check and trigger it each week independently [/-][+]Move environment version check our of PR CI[/+][-]Move environment version check our of PR CI[/-][+]Move environment version check out of PR CI[/+]mtrezza commentedon Oct 14, 2021
Closing via #7631, #7635; replaced the "CI Self Check" with the "Node Engine Check", splitting the environment check into a separate scheduled job.