Skip to content

ci: Fix demo index workflow runs too early when a release is made#7892

Merged
avelad merged 2 commits intoshaka-project:mainfrom
avelad:demo-index-workflow
Jan 16, 2025
Merged

ci: Fix demo index workflow runs too early when a release is made#7892
avelad merged 2 commits intoshaka-project:mainfrom
avelad:demo-index-workflow

Conversation

@avelad
Copy link
Member

@avelad avelad commented Jan 15, 2025

Fixes #7379

@avelad avelad requested a review from joeyparrish January 15, 2025 12:16
@avelad avelad added type: bug Something isn't working correctly priority: P3 Useful but not urgent type: CI An issue with our continuous integration tests labels Jan 15, 2025
@shaka-bot
Copy link
Collaborator

Incremental code coverage: No instrumented code was changed.

@avelad avelad requested review from theodab and tykus160 January 16, 2025 06:52
@avelad avelad merged commit f31c6f0 into shaka-project:main Jan 16, 2025
11 of 17 checks passed
@avelad avelad deleted the demo-index-workflow branch January 16, 2025 10:21
update-demo-index:
name: Deploy Demo Version Index
needs: [appspot]
uses: ./.github/workflows/demo-version-index.yaml
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I might be misremembering, but don't we need a specific trigger for this in the target workflow?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not necessary, because we are using needs, so we wait for all the appspot tasks to finish before running this one.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand "needs", but I meant something else. I looked it up, and we need the workflow_call trigger on demo-version-index.yaml to use it this way. This differs from workflow_dispatch, which we already have for manual triggering.

types: [published]
# NOTE: So long as releases are made without a personal access token (PAT),
# they will not activate this workflow's release trigger. For now, the
# schedule trigger will compensate for that by updating the index nightly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we drop the schedule trigger now?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes!

joeyparrish added a commit that referenced this pull request Jan 16, 2025
The `workflow_call` trigger is required to allow calling a workflow from
another with "uses:". The `schedule` trigger was always a workaround,
and should now be removed.

See also PR #7892.
avelad pushed a commit that referenced this pull request Jan 17, 2025
The `workflow_call` trigger is required to allow calling a workflow from
another with "uses:". The `schedule` trigger was always a workaround,
and should now be removed.

See also PR #7892.
avelad pushed a commit that referenced this pull request Jan 17, 2025
The `workflow_call` trigger is required to allow calling a workflow from
another with "uses:". The `schedule` trigger was always a workaround,
and should now be removed.

See also PR #7892.
joeyparrish added a commit to joeyparrish/shaka-player that referenced this pull request Jan 17, 2025
joeyparrish added a commit that referenced this pull request Jan 17, 2025
avelad pushed a commit that referenced this pull request Jan 23, 2025
avelad pushed a commit that referenced this pull request Jan 23, 2025
joeyparrish added a commit that referenced this pull request Feb 22, 2025
The `workflow_call` trigger is required to allow calling a workflow from
another with "uses:". The `schedule` trigger was always a workaround,
and should now be removed.

See also PR #7892.
joeyparrish added a commit that referenced this pull request Feb 22, 2025
@shaka-bot shaka-bot added the status: archived Archived and locked; will not be updated label Mar 17, 2025
@shaka-project shaka-project locked as resolved and limited conversation to collaborators Mar 17, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

priority: P3 Useful but not urgent status: archived Archived and locked; will not be updated type: bug Something isn't working correctly type: CI An issue with our continuous integration tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Demo index workflow runs too early

4 participants