GitHub user vasukiiyengar98 created a discussion: [GitHub] Workflow runs with
in_progress status are skipped and not collected after completion
Hi DevLake team,
We are using Apache DevLake v1.0.2 with the GitHub plugin to collect GitHub
Actions workflow runs.
Our DevLake deployment is running on AWS ECS. We have created the required ECS
containers/services using the official Apache DevLake Docker images.
We have some GitHub Actions workflows that run for several hours. During the
"Collect Workflow Runs" task, DevLake logs messages like:
Skipping run{id: 3372***, number: 1158***} with status in_progress
Skipping run{id: 3372***, number: 303***} with status in_progress
Our concern is that these workflow runs are skipped while they are still
in_progress.
Later, when the GitHub Actions workflow finishes and its status changes to
completed, a subsequent incremental sync does not appear to collect or update
the previously skipped workflow run.
Our expected behavior is:
1. Detect the workflow run while it is in_progress.
2. Keep it as an unfinished/in-progress run.
3. Re-check the run during subsequent syncs.
4. Once GitHub reports the run as completed, update the existing workflow run
record.
Could you please confirm:
- Is this expected behavior in DevLake v1.0.2?
- Is there any configuration that makes DevLake re-check in_progress workflow
runs during later syncs?
- Has this behavior been fixed or changed in a newer DevLake version?
- If not, what is the recommended approach for handling long-running GitHub
Actions workflows?
Since our DevLake deployment is running on AWS ECS using the official DevLake
Docker images, we would prefer to use a supported configuration or upgrade
rather than maintain a custom DevLake code/image if possible.
Any guidance on the recommended approach would be greatly appreciated.
Thanks!
GitHub link: https://github.com/apache/devlake/discussions/9125
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]
