Different error states for internal and external CI when not able to fetch pipeline status

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

I think that having two different error states:

  • When internal CI can't fetch pipeline status
  • When external CI can't fetch pipeline status

It makes the problem much more explicit - i.e. you don't have to check if you're using external or internal CI.

Also see:

@dimitrieh's suggestion:

  • "Could not connect to the GitLab CI server, please check your settings and retry"

  • "Could not connect to the external CI server, please check your settings and retry"

Edited by 🤖 GitLab Bot 🤖