Skip to content

Remove Varnish 4/5 support #38052

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

Conversation

gquintard
Copy link
Contributor

@gquintard gquintard commented Oct 9, 2023

Description (*)

Varnish 6.0 is half a decade old. 4.x and 5.x have been EOL'd years ago and there shouldn't be any more distribution carrying those, there's no good reason to keep them around.

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
  • All automated tests passed successfully (all builds are green)

Resolved issues:

  1. resolves [Issue] Remove Varnish 4/5 support #38304: Remove Varnish 4/5 support

@m2-assistant
Copy link

m2-assistant bot commented Oct 9, 2023

Hi @gquintard. Thank you for your contribution!
Here are some useful tips on 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 give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:
  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests
  13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.


For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

@ihor-sviziev
Copy link
Contributor

LGTM, but let's run the tests
@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

Varnish 6.0 is half a decade old. 4.x and 5.x have been EOL'd years ago
and there shouldn't be any more distribution carrying those, there's no
good reason to keep them around
@gquintard
Copy link
Contributor Author

missed at least one occurrence
@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

Copy link
Contributor

@ihor-sviziev ihor-sviziev left a comment

Choose a reason for hiding this comment

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

Hi @gquintard,
Could you please fix SVC failure by reverting constant removal and instead marking them as deprecated with an explanation that Varnish 4 and 5 has reached EOL?
Also, could you pls fix failing static tests?

@ihor-sviziev ihor-sviziev added Progress: pending review Priority: P2 A defect with this priority could have functionality issues which are not to expectations. and removed Progress: needs update labels Oct 10, 2023
@ihor-sviziev ihor-sviziev changed the title scrub varnish 4/5 references Remove Varnish 4/5 support Oct 10, 2023
@gquintard
Copy link
Contributor Author

gquintard commented Oct 10, 2023

Sure, do you have an example on how to mark constants deprecated?

@hostep
Copy link
Contributor

hostep commented Oct 10, 2023

@gquintard: here are some examples:

/** @deprecated Redundant dependency */
public const CONTAINER_VARIABLE = 'VARIABLE';
/** @deprecated Redundant dependency */
public const CONTAINER_FLAT_RATE_BOX = 'FLAT RATE BOX';
/** @deprecated Redundant dependency */
public const CONTAINER_FLAT_RATE_ENVELOPE = 'FLAT RATE ENVELOPE';
/** @deprecated Redundant dependency */
public const CONTAINER_RECTANGULAR = 'RECTANGULAR';
/** @deprecated Redundant dependency */
public const CONTAINER_NONRECTANGULAR = 'NONRECTANGULAR';

@hostep
Copy link
Contributor

hostep commented Oct 16, 2023

@magento run all tests

@magento-automated-testing
Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@gquintard
Copy link
Contributor Author

@ihor-sviziev, I saw that tests complained about missing @see comments so I just added them, however, that made me notice that VARNISH_SUPPORTED_VERSION_X and VARNISH_X_CONFIGURATION_PATH constants exist in both app/code/Magento/PageCache/Model/Varnish/VclTemplateLocator.php and app/code/Magento/PageCache/Model/Config.php, which feels a bit redundant

@engcom-Delta engcom-Delta added the Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it label Dec 4, 2023
@sinhaparul sinhaparul added the Project: Community Picked PRs upvoted by the community label Dec 18, 2023
@engcom-Echo engcom-Echo self-assigned this Dec 19, 2023
@engcom-Echo
Copy link
Contributor

@magento run all tests

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

@magento create issue

@engcom-Echo
Copy link
Contributor

@magento run WebAPI Tests,Integration Tests,Functional Tests CE,Functional Tests EE,Functional Tests B2B

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

@magento run WebAPI Tests,Functional Tests B2B

Copy link

The requested builds are added to the queue. You should be able to see them here within a few minutes. Please message the #magento-devops slack channel if they don't show in a reasonable amount of time and a representative will look into any issues.

@engcom-Echo
Copy link
Contributor

engcom-Echo commented Dec 20, 2023

Functional Tests B2B failure are different on last two run on same commit.
Run1
Screenshot 2023-12-20 at 7 42 56 PM

Run2
Screenshot 2023-12-20 at 7 43 20 PM

Moving it to To Approve as for SVC need to raise internal approval ticket

@engcom-Echo
Copy link
Contributor

We have raise internal approval JIRA. Once we get approval we will move this PR forward.
Till the time Moving it to Pending Approval

@engcom-Echo
Copy link
Contributor

Functional Tests B2B failure are flaky based on comment.
We have got approval for JIRA.
Hence moving it to Merge In Progress.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Project: Community Picked PRs upvoted by the community Risk: low Triage: Dev.Experience Issue related to Developer Experience and needs help with Triage to Confirm or Reject it
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Issue] Remove Varnish 4/5 support
7 participants