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

Move the stable api group and promote it to v1 #894

Merged
merged 14 commits into from
Jul 17, 2019

Conversation

roberthbailey
Copy link
Member

@roberthbailey roberthbailey commented Jul 10, 2019

I wanted to get the first part of this out for folks to look at before I go through all of the docs and install bits and get them updated. I've done the package move and version change and fixed enough of the code to get the unit tests to pass.

Part of #703.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: ee19a6c6-008c-4270-953d-72dd1f513696

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@roberthbailey roberthbailey force-pushed the stable-to-core-v1 branch 2 times, most recently from e553164 to 3ba3196 Compare July 12, 2019 09:50
@roberthbailey
Copy link
Member Author

The newest push has the a bunch of the remaining bits updated (I think all that remains is the docs). I've done a first pass on the SDKs, but I still need to figure out how to test them more thoroughly, since it seems like make test-sdks only tests the go and node SDKs.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: a00e7ddb-460f-495a-a08c-6e821671753a

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 7265be7c-c666-4c4a-bb5e-750dc052b5a5

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 2ea8355b-6122-4983-9bba-fc21f522e365

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 3eaf4a79-b4d5-4d7a-89fa-02aeaa60e3ed

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@markmandel
Copy link
Member

Had a quick look through - approach looks good. Not seeing any red flags on my end 👍

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 4968f309-4984-47cd-a379-b0636e9679e7

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@roberthbailey roberthbailey marked this pull request as ready for review July 13, 2019 08:17
Copy link
Member Author

@roberthbailey roberthbailey left a comment

Choose a reason for hiding this comment

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

I've finished going through all of the docs and updating them. This PR won't pass tests until we delete the helm install (like the previous breaking changes) but I'm wondering.... once we do that will all other PRs fail tests until they rebase on top of this one?

I'm happy to let this sit for a couple of days while we merge other PRs to prevent other contributors from having to rebase, since this is likely to force every other PR to need a rebase, but it would be nice to get it in before the end of next week so that I don't have to rebase it for too long.

@@ -29,7 +29,7 @@
[5.890398, "o", "\u001b[?1l\u001b>\u001b[?2004l\r\r\n"]
[5.891151, "o", "\u001b]2;kubectl apply -f fleet.yaml\u0007\u001b]1;kubectl\u0007"]
[5.891306, "o", "\u001b]133;C;\u0007"]
[6.329093, "o", "fleet.stable.agones.dev/simple-udp created\r\n"]
[6.329093, "o", "fleet.agones.dev/simple-udp created\r\n"]
Copy link
Member Author

Choose a reason for hiding this comment

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

I'm not sure whether the feature flag things work in this file....

Copy link
Collaborator

Choose a reason for hiding this comment

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

this file is interpreted by javascript to render the cast.

Copy link
Member Author

Choose a reason for hiding this comment

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

I wasn't sure how to fix it properly. One option is just put this into a separate PR and merge it right before we cut 0.12.0 so that the website flips is only different from the latest release for a short period of time.

Copy link
Member Author

Choose a reason for hiding this comment

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

I've moved this change into #911.

Copy link
Collaborator

Choose a reason for hiding this comment

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

awesome.

@@ -236,7 +293,6 @@ $ curl http://localhost:8001/apis/stable.agones.dev/v1alpha1/namespaces/default/

# allocate a gameserver from a fleet named 'simple-udp', with GameServerAllocation

{{% feature expiryVersion="0.12.0" %}}
Copy link
Member Author

Choose a reason for hiding this comment

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

This looks a bit funny, but I split all of the new stuff into a different block so that it's easier to see what changed.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: e0c313f3-7b37-43fa-b0e4-c148b26a0c8c

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 78b025a6-035f-4d3c-8175-24f1650a2d01

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: 5f7a04a9-ae26-4511-839b-9b845070b7bf

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: d16836d2-54ec-47d7-8e90-b7e5df08caf6

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@@ -4,7 +4,12 @@ linkTitle: "Create an Allocator Service (Go)"
date: 2019-01-03T03:15:34Z
description: >
This tutorial describes how to interact programmatically with the
{{% feature expiryVersion="0.12.0" %}}
Copy link
Member Author

Choose a reason for hiding this comment

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

It looks like I can't use the curly braces in the yaml part here, since it causes the tests to fail. So I'm going to leave this with the v1alpha1 version and we'll need to change it around the time we cut the 0.12.0 release.

@roberthbailey roberthbailey force-pushed the stable-to-core-v1 branch 2 times, most recently from 82c8220 to 8d01dfe Compare July 15, 2019 22:48
@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: a3f92ffd-f8a1-482c-80b7-b617b8f29fa2

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: eeb06864-93f3-4134-ad60-0c4ee17f94c2

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

Copy link
Collaborator

@cyriltovena cyriltovena left a comment

Choose a reason for hiding this comment

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

LGTM. Should we merge tomorrow ?

@roberthbailey
Copy link
Member Author

LGTM. Should we merge tomorrow ?

I'm wondering if we should get @markmandel's PR for the Reserve() SDK in first, since this is going to conflict and I'm happy to do the resolving on my end. Once that one is in I don't see nearly as many open PRs that will conflict so it'd probably be a good time to do it.

@roberthbailey
Copy link
Member Author

I added a commit that I think will make e2e pass, but I should also run through the other examples and see if they need a recompile / image update as well.

@markmandel
Copy link
Member

Good point - they probably do.

@markmandel
Copy link
Member

/cc @aLekSer will this affect the conformance tests?

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: e65add73-fdef-4365-9841-1d87af6daacb

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: d803b573-e5cb-4820-82b1-5ff9a4b0748a

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@roberthbailey
Copy link
Member Author

The latest build failed during the helm upgrade

Error: UPGRADE FAILED: MutatingWebhookConfiguration.admissionregistration.k8s.io "agones-mutation-webhook" is invalid: webhooks[0].clientConfig.url: Required value: exactly one of url or service is required && ValidatingWebhookConfiguration.admissionregistration.k8s.io "agones-validation-webhook" is invalid: webhooks[0].clientConfig.url: Required value: exactly one of url or service is required
make: *** [install] Error 1
Makefile:277: recipe for target 'install' failed

I'm going to restart it and see if we can get a signal from the sdk conformance tests.

@agones-bot
Copy link
Collaborator

Build Failed 😱

Build Id: bf136040-bd3b-403f-83be-54e57a9bc338

To get permission to view the Cloud Build view, join the agones-discuss Google Group.

@aLekSer
Copy link
Collaborator

aLekSer commented Jul 17, 2019

Regarding conformance tests I don't see any issues. Let see if they pass on Cloud Build.

@roberthbailey
Copy link
Member Author

The conformance tests are passing locally for me; hopefully they also pass in CI.

@agones-bot
Copy link
Collaborator

Build Succeeded 👏

Build Id: 9c790210-4bbc-4259-8c2e-ab9e6bd30891

The following development artifacts have been built, and will exist for the next 30 days:

A preview of the website (the last 30 builds are retained):

To install this version:

  • git fetch https://github.com/GoogleCloudPlatform/agones.git pull/894/head:pr_894 && git checkout pr_894
  • helm install install/helm/agones --namespace agones-system --name agones --set agones.image.tag=0.12.0-554bc72

@markmandel markmandel merged commit d6cb007 into googleforgames:master Jul 17, 2019
@markmandel
Copy link
Member

xug5ger

@roberthbailey
Copy link
Member Author

Regarding:

I think for now to unstick us, create a 0.12 manually and push it up, and we'll come up with a more formal process later. WDYT?

I've created #917. And in the meantime, I've rebuilt the container image from the master branch and pushed it.

@markmandel markmandel added the kind/cleanup Refactoring code, fixing up documentation, etc label Aug 1, 2019
@roberthbailey roberthbailey deleted the stable-to-core-v1 branch August 1, 2019 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/breaking Breaking change kind/cleanup Refactoring code, fixing up documentation, etc
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants