-
-
Notifications
You must be signed in to change notification settings - Fork 511
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
chore: run rootless mode in nighlty builds #2611
Merged
mdelapenya
merged 1 commit into
testcontainers:main
from
mdelapenya:run-rootless-nightly
Jun 27, 2024
Merged
chore: run rootless mode in nighlty builds #2611
mdelapenya
merged 1 commit into
testcontainers:main
from
mdelapenya:run-rootless-nightly
Jun 27, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
mdelapenya
added
chore
Changes that do not impact the existing functionality
github_actions
Pull requests that update GitHub Actions code
labels
Jun 27, 2024
✅ Deploy Preview for testcontainers-go ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Merging, as there is no code related to the tests. The current failures in rootless mode are precisely the ones we want to proactively discover in this nightly build. |
mdelapenya
added a commit
to mdelapenya/testcontainers-go
that referenced
this pull request
Jun 27, 2024
* main: chore: run rootless mode in nighlty builds (testcontainers#2611)
mdelapenya
added a commit
that referenced
this pull request
Jun 28, 2024
mdelapenya
added a commit
to thaJeztah/testcontainers-go
that referenced
this pull request
Jun 28, 2024
* main: chore: test cleanups (testcontainers#2608) chore(ci): pass docker install type to the nightly build payload (testcontainers#2612) chore: run rootless mode in nighlty builds (testcontainers#2611) chore(deps): bump github.com/hashicorp/go-retryablehttp (testcontainers#2605) chore: improve log handling when container is stopping (testcontainers#2601)
mdelapenya
added a commit
to mdelapenya/testcontainers-go
that referenced
this pull request
Jul 2, 2024
* main: chore(deps): bump github.com/docker/docker from v26.1.4 to v27.0.2 (testcontainers#2593) fix: Rename TC_HOST environment variable to TESTCONTAINERS_HOST_OVERRIDE (testcontainers#2536) chore: test cleanups (testcontainers#2608) chore(ci): pass docker install type to the nightly build payload (testcontainers#2612) chore: run rootless mode in nighlty builds (testcontainers#2611) chore(deps): bump github.com/hashicorp/go-retryablehttp (testcontainers#2605) chore: improve log handling when container is stopping (testcontainers#2601)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
chore
Changes that do not impact the existing functionality
github_actions
Pull requests that update GitHub Actions code
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This PR updates the nightly build that uses the TEST channel of the Docker builds, so that we are able to run the nightly build for rootful and rootless mode.
Why is it important?
We want to detect regressions the soonest.
Related issues