potiuk commented on pull request #11276: URL: https://github.com/apache/airflow/pull/11276#issuecomment-703615555
> I'm a little bit confused where this details shows up though? I looked in : > * [Build CI Images of the Build Images workflow](https://github.com/apache/airflow/runs/1208459768?check_suite_focus=true) This is where actual jobs are executed and you can see errors that result from - for example - wrong dependencies. > * [Wait for PROD Images of the CI Build workflow](https://github.com/apache/airflow/pull/11276/checks?check_run_id=1208457959) Here you do not have much information and can't easily have as I explained in https://github.com/apache/airflow/pull/11276#issuecomment-703531663 - happy if someone writes another action (I already added quite a lot to the "cancel workflow" action to get it all possible using GitHub APIS. that might be a good exercise for someone try to learn about the process. Those jobs are basically polling for images to appear in Github Registry. This is by far the easiest way to check if the images are ready. Trying to use GithHub APIs to retrieve this information will be significantly more complex. GitHub does not have good support for workflow_runs linking to the PR :(. So I am using "Github Checks" to simulate that. Github Checks is the way that for example Travis CI builds can report their progress in Github PR. They provide status and optional link that you can use to see the details, but usually it is a 3rd-party link. In this case, it is not really "3rd party" but another Workflow run - loosely related to the original PR. So I am reporting status using checks from the other workflow. Unfortunately When I try to pass "details_url" to this workflow, Github apparently overrides the detail_url with link to the "Check" and not link to the "workflow build job". So instead of passing the URL in "Details_url" I am passing it in the "summary message" - this way from the "Build Image Check" you can get the link to the "Build Image Job". ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
