Skip to content

Add Github workflow to allow for automatic preview releases #22367

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 22 commits into from
Aug 13, 2024

Conversation

michalkleiner
Copy link
Contributor

Description:

Adds a new workflow that determines what the new preview version should be, updates the version file, runs the tests for the new version and on success publishes a preview release.

If any of the steps fail along the way the action stops and doesn't create a release.

This introduces 5.x-preview branch that is always reset to the top of 5.x-dev before the version number is increased and tests are run, it can technically be deleted as it will be recreated every time.

The check for code changes is done between the newest preview version tag and 5.x-dev, excluding the line that contains the version number change in core/Version.php.

We can consider extending the range of changes we want to ignore in a follow up.

We either need to merge this for testing after a code review or people can run this in their own forks.

Review

@michalkleiner michalkleiner requested a review from a team July 3, 2024 08:13
@michalkleiner michalkleiner added c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Better processes Indicates an issue is about improving how we work. Needs Review PRs that need a code review labels Jul 3, 2024
@michalkleiner michalkleiner added this to the 5.2.0 milestone Jul 3, 2024
@michalkleiner michalkleiner force-pushed the preview-automation branch 2 times, most recently from bf8567c to f9dfc98 Compare July 12, 2024 05:50
@michalkleiner michalkleiner requested review from sgiehl, mneudert and a team July 16, 2024 21:36
Copy link
Contributor

This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers

@github-actions github-actions bot added the Stale The label used by the Close Stale Issues action label Jul 30, 2024
Comment on lines 23 to 28
# TODO: remove manual dispatch after testing and enable cron
workflow_dispatch:
branches:
- 5.x-dev
#schedule:
# - cron: '0 1 * * *' # 1am daily
Copy link
Member

Choose a reason for hiding this comment

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

Should we change that before merging or leave it in, so we can test that manually before having it run as cron?

Copy link
Member

@mneudert mneudert Aug 5, 2024

Choose a reason for hiding this comment

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

I would say we merge it as workflow_dispatch and run it once manually before updating it to a schedule. Just so we don't have to wait for the first scheduled run to see if any of the recent repository changes has an unforeseen impact 🤔

@caddoo caddoo requested a review from mneudert August 9, 2024 01:39
@caddoo caddoo merged commit fac18d8 into matomo-org:5.x-dev Aug 13, 2024
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Better processes Indicates an issue is about improving how we work. c: Platform For Matomo platform changes that aren't impacting any of our APIs but improve the core itself. c: Tests & QA For issues related to automated tests or making it easier to QA & test issues. Needs Review PRs that need a code review Stale The label used by the Close Stale Issues action
Development

Successfully merging this pull request may close these issues.

4 participants