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

Add Dockerfile for e2e base image #3284

Merged
merged 1 commit into from
Feb 1, 2024

Conversation

AlanGreene
Copy link
Member

Changes

Related to #3283

Add a Dockerfile which will be used to create the base images used for running the e2e tests. This allows us direct control over the Chrome and Node.js versions used instead of waiting for Cypress to release a new image which happens very infrequently.

Move the kubectl install and much of the other config into this Dockerfile so that the one used to package the tests is more focused and doesn't have to duplicate the foundations each time the tests run.

Pipeline definitions and related config to build and publish the image will follow separately.

/kind misc

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Docs included if any changes are user facing
  • Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (new features, significant UI changes, API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

Add a Dockerfile which will be used to create the base images
used for running the e2e tests. This allows us direct control
over the Chrome and Node.js versions used instead of waiting
for Cypress to release a new image which happens very infrequently.

Move the kubectl install and much of the other config into
this Dockerfile so that the one used to package the tests is
more focused and doesn't have to duplicate the foundations each
time the tests run.

Pipeline definitions and related config to build and publish
the image will follow separately.
@tekton-robot tekton-robot added kind/misc Categorizes issue or PR as a miscellaneuous one. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Feb 1, 2024
@AlanGreene
Copy link
Member Author

AlanGreene commented Feb 1, 2024

Timed out waiting for the second run to complete, will add this to the list of tests to watch for flake (first time it's failed in PR jobs). This change has no impact on any existing tests.
/retest

Copy link
Contributor

@briangleeson briangleeson left a comment

Choose a reason for hiding this comment

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

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 1, 2024
@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: briangleeson

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 1, 2024
@tekton-robot tekton-robot merged commit 3e6ebe5 into tektoncd:main Feb 1, 2024
8 checks passed
@AlanGreene AlanGreene deleted the e2e_base_image branch February 1, 2024 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants