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

Rosetta/test build rosetta dockerfile in ci #5635

Merged
merged 34 commits into from
Aug 13, 2020

Conversation

lk86
Copy link
Contributor

@lk86 lk86 commented Aug 13, 2020

Thank you for contributing to Coda! Please see CONTRIBUTING.md if you haven't
yet. In that doc, there are more details around how to start our CI.

Identical content to #5634 except with rosetta in the beginning of the branch name to trigger a rosetta dockerfile build. Some additional commits have been made to make the git branch more consistently use BUILDKITE_BRANCH which is immutable and set properly.

This PR extends the original goal of fixing docker builds in CI to also include properly building + pushing the rosetta image as this was a small change from the existing setup.

NOTE: Only develop, master, and branches with "rosetta/" as a leading prefix on the name will build rosetta images in CI as this setup is still very slow and does not leverage caching properly.

Explain your changes here.

Explain how you tested your changes here.

Checklist:

  • Document code purpose, how to use it
    • Mention expected invariants, implicit constraints
  • Tests were added for the new behavior
    • Document test purpose, significance of failures
    • Test names should reflect their purpose
  • All tests pass (CI will check this if you didn't)
  • Serialized types are in stable-versioned modules
  • Does this close issues? List them:

Closes #5151

@lk86 lk86 added the ci-build-me Add this label to trigger a circle+buildkite build for this branch label Aug 13, 2020
@lk86 lk86 requested review from a team as code owners August 13, 2020 04:22
@lk86 lk86 mentioned this pull request Aug 13, 2020
5 tasks
@lk86 lk86 added the ready-to-merge Adding this label will trigger mergify and trigger CI to run and merge the PR label Aug 13, 2020
echo "Exporting Variables: "
# Export Variables for Downstream Steps

GITHASH=$(git rev-parse --short=7 HEAD)
Copy link
Member

Choose a reason for hiding this comment

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

This environment setup seems to be duplicated in rebuild-deb. Can we move it to a separate file that they both source/call, so that we know they'll be kept in sync?

Copy link
Contributor

Choose a reason for hiding this comment

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

we've had that number get out of sync before too

Copy link
Contributor

@yourbuddyconner yourbuddyconner left a comment

Choose a reason for hiding this comment

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

Beautiful BASH

@mergify mergify bot merged commit 958c669 into develop Aug 13, 2020
@mergify mergify bot deleted the rosetta/test-build-rosetta-dockerfile-in-ci branch August 13, 2020 20:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci-build-me Add this label to trigger a circle+buildkite build for this branch ready-to-merge Adding this label will trigger mergify and trigger CI to run and merge the PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

setup Rosetta build in the new CI
4 participants