Skip to content
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

Run campaigns tests after an upgrade of PrestaShop #37

Closed
wants to merge 59 commits into from

Conversation

jolelievre
Copy link
Contributor

@jolelievre jolelievre commented Jun 21, 2023

Questions Answers
Description? Add manual workflow to test upgrades, the workflow lets you choose a source branch/tag and a target branch/tag You can also use the build from nightly if you prefer and there is an option to upload the shop files and DB if you want to debug locally after
Type? new feature
BC breaks? no
Deprecations? no
Fixed ticket? ~
Sponsor company ~
How to test? ~

@jolelievre jolelievre changed the title Test upgrade Run campaigns tests after an upgrade of PrestaShop Jun 22, 2023
Comment on lines 28 to 48
#source_version:
# type: string
# description: OR define a released version (ex 1.7.8.3) to start the upgrade from (ignored if left empty)
# required: false
target_ref:
type: choice
description: Use a target branch or tag to upgrade to
required: true
options:
- 'develop'
- '8.1.x'
- '8.0.x'
- '8.0.4'
- '8.1.0-rc.1'
- '8.1.0-build1'
default: '8.1.x'
# LATER, can include a PR from the core to test an autoupgrade debug, we may need to build a release archive from the PR
#target_pr_number:
# description: Pull request Id
# required: true
# LATER, handle a specific version and build the source based on the existing release archives or github tags

Choose a reason for hiding this comment

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

we can remove comments

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh you're right!!

@@ -0,0 +1,17 @@
# This is a temporary workflow to force triggering the new manual one which is not usable as long as it's not on the default branch
Copy link
Member

Choose a reason for hiding this comment

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

This file is unuseful. Please remove it.

Copy link
Member

@Progi1984 Progi1984 left a comment

Choose a reason for hiding this comment

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

Some feedbacks

options:
- 'dev'
- 'master'
- '1.7.8.x'

Choose a reason for hiding this comment

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

copy paste error i think

run: composer install
working-directory: ${{ env.PS_DIR }}/modules/autoupgrade
- name: Install module via CLI commands
run: docker exec -u www-data prestashop_autoupgrade php bin/console prestashop:module install autoupgrade

Choose a reason for hiding this comment

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

before version 1.7.4.0 the console was under /app, this will have to be taken into account if we add older versions

@jolelievre
Copy link
Contributor Author

Closed in favor of #51

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants