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

Merge changes for 1.15.1 from the v1.15.x branch to dev #1072

Closed
wants to merge 3 commits into from

Conversation

nmeyerhans
Copy link
Contributor

Summary

This PR ensures that changes that have already been staged for release as 1.15.1 are reflected in the dev branch for future feature releases.

In reality, this only pull in the addition of a unit test and a changelog update.

Implementation details

git checkout dev
git merge v1.15.x

There were merge conflicts because there was a minimal change in 1.15.x to address #1067 while the same issue was fixed as part of a larger refactor in the dev branch. The conflict was resolved by keeping the fix from the dev branch.

Testing

  • Builds on Linux (make release)
  • Builds on Windows (go build -out amazon-ecs-agent.exe ./agent)
  • Unit tests on Linux (make test) pass
  • Unit tests on Windows (go test -timeout=25s ./agent/...) pass
  • Integration tests on Linux (make run-integ-tests) pass
  • Integration tests on Windows (.\scripts\run-integ-tests.ps1) pass
  • Functional tests on Linux (make run-functional-tests) pass
  • Functional tests on Windows (.\scripts\run-functional-tests.ps1) pass

New tests cover the changes:

Description for the changelog

CHANGELOG.md updates are included here as appropriate.

Licensing

This contribution is under the terms of the Apache 2.0 License: yes

@@ -3,6 +3,7 @@
## Unreleased
* Feature - Support pulling from Amazon ECR with specified IAM role in task definition
* Feature - Enable support for task level CPU and memory constraints.
* Bug - Fixed a bug where container state information wasn't reported. [#1067](https://github.com/aws/amazon-ecs-agent/pull/1067)
Copy link
Contributor

Choose a reason for hiding this comment

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

Should all three of these bug fixes be in the ## 1.15.1 header for this merge as well?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Dev already has the other fixes and their corresponding changelog. The merge just pulls in the one entry that was missing.

@nmeyerhans
Copy link
Contributor Author

We may want to skip this merge and wait to merge all the 1.15.2 changes when they're ready. I don't see a need to merge this PR as is. Any disagreement?

@jhaynes
Copy link
Contributor

jhaynes commented Nov 15, 2017

Seems reasonable to me.

@richardpen
Copy link

yes, this was included in 1.15.2, we can just merge 1.15.2 to dev.

@nmeyerhans
Copy link
Contributor Author

We merged all the 1.15.x changes up to and including 1.15.2 in #1082. We don't need this PR.

@nmeyerhans nmeyerhans closed this Nov 20, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants