-
Notifications
You must be signed in to change notification settings - Fork 1
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
V4.16.0.1 merge #15
Open
davkutalek
wants to merge
325
commits into
master
Choose a base branch
from
v4.16.0.1-merge
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
V4.16.0.1 merge #15
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
Fixes Container logs are not uploaded when dependencies fail to start buildkite-plugins#327
…e-froms Test PR Multiple cache froms
…logs-when-dependencies-fail-to-start
…oad-logs-when-dependencies-fail-to-start Upload logs when dependencies fail to start
…_multiple_versions_keys_in_config Support multiple `version` keys in docker-compose config
…_issue-312 Warnings with step-level array commands
…_deactivate_renovate_dependency_dashboard Deactivate renovate dependency dashboard
…ate/plugin-linter-3.x Update buildkite plugin plugin-linter to v3.2.0
…_fix_tester Fix tester
…_signal_handling Better signal handling (for Job cancellations)
…re-new-release Update version to next release
The `docker-compose` plugin currently seems to ignore the `skip-pull` option. For example, this configuration: ``` steps: - command: bundle exec rubocop plugins: - docker-compose#v4.14.0: run: ruby skip-pull: true config: docker-compose.yml cli-version: 2 ``` Results in a command that includes the `--pull` flag, something like this: ``` docker compose -f docker-compose.yml -p buildkite0123456789 build --pull ruby ``` This PR updates run.sh to fully support the `skip-pull` option. The same configuration as above now results in the `--pull` flag being omitted from the generated command: ``` docker compose -f docker-compose.yml -p buildkite0123456789 build ruby ```
…rt-for-skip-pull-option Add --skip-pull support to v2 run command
…-from-details Add more info on cache-from
…se-args Collapse logging of run output by default
… service startups
Add --include-deps option to Docker image pulls and retries to Docker service startups
rayalan
approved these changes
May 10, 2024
Add logging to DD, attempt to make shutdown more graceful
[CE-4035] Prevent process restarts when sig term received
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.