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

Pull changes for deploying to it-sre infra #3663

Merged
merged 17 commits into from May 22, 2019
Merged

Pull changes for deploying to it-sre infra #3663

merged 17 commits into from May 22, 2019

Conversation

ziegeer
Copy link
Contributor

@ziegeer ziegeer commented May 20, 2019

No description provided.

Copy link
Contributor

@kfferrando kfferrando left a comment

Choose a reason for hiding this comment

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

This looks good, thanks!

Copy link
Collaborator

@akatsoulas akatsoulas left a comment

Choose a reason for hiding this comment

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

I added a couple of nits/questions. LGTM. I am not sure if @jgmize / @metadave would like to have a quick look at this as well.

@@ -18,7 +18,7 @@ do
-t ${DOCKER_REPO}:${image}-${GIT_SHA_SHORT} \
--cache-from ${DOCKER_REPO}:${image}-latest \
--cache-from kitsune:${image}-latest \
-f docker/dockerfiles/${image} \
Copy link
Collaborator

Choose a reason for hiding this comment

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

@ziegeer could you please elaborate a bit about this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, this script is for building docker images locally, which I don't think anyone actually does anymore, but I had to and it pointed to some non-existant dockerfiles that look to have been previously consolidated into a single Dockerfile. So I just pointed the script at that and it worked.

docs/kitsune-support.md Outdated Show resolved Hide resolved
@@ -5,9 +5,9 @@ set -eo pipefail
# BRANCH_NAME, BUILD_NUMBER

# defaults and constants
CHANNEL="sumodev"
Copy link
Collaborator

Choose a reason for hiding this comment

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

Shall we use the existing channel? It's already well known by users and it usually doesn't have any noise apart from dev related topics. The new channel has also logs from yar which will make it harder to locate the builds.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I'd be happy to but in the interim it's going to be noisy while we get everything stood up, and I don't want to confuse a non-production event with a production event. Could we perhaps switch back post-migration to the current channels?

@bookshelfdave
Copy link
Contributor

👍

@ziegeer ziegeer merged commit f22615d into mozilla:itsre May 22, 2019
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.

None yet

5 participants