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

BUILDTOOLS-2329: Update Dockerfile to mirror smithy.yaml #253

Merged
merged 1 commit into from
Apr 25, 2018

Conversation

ci-push-wf
Copy link

Overview

In order to improve build isolation, reduce costs, reduce support burden, remove black magic, and improve local consistency, we are migrating away from smithy.yaml and existing Smithy infrastructure to Dockerfile builds supported by off the shelf AWS resources.

Reviewing and merging this PR is the first step in that process; this PR simply copies the contents of your smithy.yaml into a more explicit Dockerfile.
In order to begin running Dockerfile builds you will need to enable Dockerfile builds from your repo configuration page in Smithy.
Once you have enabled Dockerfile builds for your repo, rebuilding the PR build in smithy will trigger the newly enabled Dockefile build.

Expectations

With only a couple of exceptions the behavior of this new Dockerfile should match the existing behavior in your smithy.yaml
Therefore, our expectations are for you to merge this PR as soon as possible. If for any reason you discover a problem post merge, you can disable the new builds and re-enable smithy.yaml builds in your repo configuration page in Smithy

Support/Questions

The migration to Dockerfile builds is our top priority, so please reach out to us if you have any questions, comments, or concerns during this process. Non-urgent questions should go into Confluence Questions and urgent support can be requested in the Support: Build Tools Hipchat Room

More Info

Information about the migration to dockerfile can be found here
A user guide for Dockerfile builds can be found here

@jayudey-wf

@ci-push-wf ci-push-wf requested a review from a team as a code owner April 5, 2018 19:33
@jayudey-wf jayudey-wf closed this Apr 5, 2018
@jayudey-wf jayudey-wf reopened this Apr 5, 2018
@codecov-io
Copy link

codecov-io commented Apr 5, 2018

Codecov Report

Merging #253 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #253   +/-   ##
=======================================
  Coverage   22.98%   22.98%           
=======================================
  Files           7        7           
  Lines         161      161           
=======================================
  Hits           37       37           
  Misses        124      124

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 04832a7...7b5f2a2. Read the comment docs.

@jayudey-wf
Copy link
Contributor

+1

@jayudey-wf
Copy link
Contributor

jayudey-wf commented Apr 6, 2018

QA +1

  • Testing instruction
  • Dev +1's
  • Dev/QA +10 with detail of what was tested
    • verified build completed as expected
  • Security review (if required)
  • Unit tests created/updated (n/a)
  • All unit tests pass
  • Rosie has run and reports properly the release the ticket will be included in

Merging into master.

@jayudey-wf
Copy link
Contributor

@Workiva/release-management-pp

@jayudey-wf
Copy link
Contributor

need one more reviewer on this pr

Copy link
Contributor

@travisreed-wf travisreed-wf left a comment

Choose a reason for hiding this comment

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants