Magento2: testing new instance feature

[DanielRuf]

@magento-engcom-team give me 2.2.4 instance

[DanielRuf]

@magento-engcom-team give me 2.3 instance

[orlangur]

Looks like only PRs are supported :)

Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:
- `@magento-engcom-team give me test instance` - deploy test instance based on Pull Request changes
- `@magento-engcom-team give me new test instance` - deploy **NEW** test instance based on Pull Request changes
- `@magento-engcom-team give me {$VERSION} instance` - deploy Vanilla Magento instance for Issue or Pull Request

For more details, please, review the [Magento Contributor Assistant](https://github.com/magento/magento2/wiki/Magento-Contributor-Assistant) documentation

[orlangur]

Hmmm,

"for Issue or Pull Request"

is misleading then

[DanielRuf]

Hmmm,

"for Issue or Pull Request"

is misleading then

Exactly. I thought I could use it to create a test instance for projects where we can not give the URL or some text description is not enough and a real demo would be needed.

[okorshenko]

@magento-engcom-team give me 2.2.4 instance

[magento-engcom-team]

Hi @okorshenko. Thank you for your request. I'm working on Magento 2.2.4 instance for you

[magento-engcom-team]

Hi @okorshenko, here is your Magento instance.
Admin access: https://i-16163-2-2-4.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[okorshenko]

Hi @DanielRuf

Sorry for confusing. I can explain why it does not work:

1. use used the command @magento-engcom-team give me 2.2.4 instance in the issue description, but it should be in the comment. That's why it didn't work

1. use used the command @magento-engcom-team give me 2.3 instance in the issue comment which is correct, but we don't have 2.3 release available yet (it is not released). So to get 2.3 you need to use @magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @okorshenko. Thank you for your request. I'm working on Magento 2.2.4 instance for you

[magento-engcom-team]

Hi @okorshenko, here is your Magento instance.
Admin access: https://i-16163-2-2-4.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[DanielRuf]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @DanielRuf. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[DanielRuf]

Awesome =)

[magento-engcom-team]

Hi @DanielRuf, here is your Magento instance.
Admin access: https://i-16163-2-3-develop.engcom.dev.magento.com/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[orlangur]

but we don't have 2.3 release available yet (it is not released)

@okorshenko thanks for comprehensive explanation, some response from bot like "no 2.3 released yet, you may use 2.3-develop" or "invalid release specified, available releases: 2.1.15, 2.2.4, 2.3-develop" would not hurt though.

[CristiLodor]

@magento-engcom-team give me 2.3.2 instance

[magento-engcom-team]

Hi @CristiLodor. Thank you for your request. I'm working on Magento 2.3.2 instance for you

[magento-engcom-team]

Hi @CristiLodor, here is your Magento instance.
Admin access: https://i-16163-2-3-2.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[DanielRuf]

@magento give me 2.3.0 instance

[magento-engcom-team]

Hi @DanielRuf. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[DanielRuf]

Seems the bot got stuck. Let's try again

@magento give me 2.3.0 instance

[magento-engcom-team]

Hi @DanielRuf. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[DanielRuf]

Hm, let's create a new issue.

[m2-assistant[bot]]

Hi @sdzhepa. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: :point_down:

• [ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• [ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• [ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• [ ] 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and _stop verification process here_!

• [ ] 5. Add label Issue: Confirmed once verification is complete.

• [ ] 6. Make sure that automatic system confirms that report has been added to the backlog.

[DanielRuf]

And another try

@magento give me 2.3.0 instance

[magento-engcom-team]

Hi @DanielRuf. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[sdzhepa]

Hello @DanielRuf

I am working on this issue give me 2.3.0 instance.
I will keep you updated here or directly in Slack

Sorry for inconveniences

[DanielRuf]

It does not seem to work with any tagged version. Only branches (2.3-develop).

[sdzhepa]

Hello @DanielRuf

Just update.
There root cause of this issue with the deployer is PHP version on the server with deployer.
Recently we have updated it to 7.3.11 and as a result, we have:

On GitHub> @magento give me 2.3.0 instance

In logs > 
Problem 1
    - This package requires php ~7.1.3||~7.2.0 but your PHP version (7.3.11) does not satisfy that requirement.

Now I am trying to figure out how it can be hotfixed.
One of the possible quick solutions is downgrade PHP to 7.2.0.

[sdzhepa]

@magento give me 2.3.0 instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.3.0 instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-16163-2-3-0.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sdzhepa]

@magento give me 2.3-develop instance

[magento-engcom-team]

Hi @sdzhepa. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @sdzhepa, here is your Magento instance.
Admin access: https://i-16163-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[sdzhepa]

@DanielRuf

We have applied hotfix and it works now for 2.3.0 ... 2.3-develop

I hope it is a temporary solution because we have a lot of tasks in our backlog related to Instance Deployer functionality(refactor/rewrite). We planned to work on it starting from the next year.

Also, let me remind that the main goals of this tool are

• provides the ability to check(confirm) is a newly created issue can be reproduced on the latest codebase
• provides the ability to deploy a Magento instance based on created PR for the latest code
• It has a limited feature list and can be used only for some high-level verification. This point I hope will be improved but even after all planned changes it will have limitation(do not expect it will be the same access/control as for local instance)

[DanielRuf]

Awesome, many thanks.

Well but about testing 2.2 releases and testing against specific releases? This is a valid usecase.

[sdzhepa]

A couple of months ago 2.2-develop branch was closed/removed for the public repository and after it, we no longer accept Pull Request/Issue for 2.2.x version in this repository.

For more details:

We no longer accept pull requests to the v2.2 ... release lines to focus all development efforts on v2.3.
Related DevDoc was updated https://devdocs.magento.com/guides/v2.3/contributor-guide/contributing.html#rules

MAGENTO OPEN SOURCE SOFTWARE MAINTENANCE POLICY

So, according to all mentioned above support of 2.2.x was disabled for Instance Deployer as well