-
Notifications
You must be signed in to change notification settings - Fork 825
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
upgrade xonotic version #2669
upgrade xonotic version #2669
Conversation
examples/xonotic/go.mod
Outdated
@@ -0,0 +1,19 @@ | |||
module agones.dev/agones/examples/xonotic |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you still run make build
from this directory to build this locally outside of the docker container?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
examples/xonotic/go.mod
Outdated
google.golang.org/protobuf v1.26.0 // indirect | ||
) | ||
|
||
replace agones.dev/agones v0.0.0-dev => ../../ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@markmandel - what do you think about building this from head vs. a specific agones release? STK is currently built against 1.8.0, which is pretty old but also makes it clear the last time we updated it as well as making the build reproducible.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤔 hmnn, that's a good question.
The benefit I see of running against the development branch is that you can build out an example against something that is currently being worked on and not released.
That being said - pointing to a specific version (like we do in STK) is probably a better experience for the end user, so we should probably be consistent and do the same here.
It would also make the Docker build simpler as we don't have to force building from project root and copying in files (basically copy what we do in STK).
If we need to have in-development features, we can worry about it when it happens.
The only conflict I have - in simple-game-server we do probably want to continue building against a development version, as editing that binary is often necessary to implementing and testing new features. So that's likely the exception to the above rule.
Sound good?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
pointing to a specific version (like we do in STK) is probably a better experience
I also feel that xonotic is pretty much similar STK example.
If we need to have in-development features, we can worry about it when it happens.
Should we target to agones v1.8.0 (Works fine, just tested) or any other specific version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's use what is latest - 1.24.0
. Then we know when this example was built.
87568ff
to
2a4ea06
Compare
examples/xonotic/Makefile
Outdated
@@ -41,6 +41,10 @@ image_tag = $(REPOSITORY)/xonotic-example:0.8 | |||
build: | |||
cd $(root_path) && docker build -f $(project_path)/Dockerfile --tag=$(image_tag) . |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cd $(root_path) && docker build -f $(project_path)/Dockerfile --tag=$(image_tag) . | |
docker build -f $(project_path)/Dockerfile --tag=$(image_tag) . |
We no longer need all of Agones to build it, so we can avoid a big Docker context pull now!
STK example:
agones/examples/supertuxkart/Makefile
Lines 40 to 41 in 15e9000
build: | |
docker build -f $(project_path)/Dockerfile --tag=$(image_tag) . |
Other than that, I think this is good to go (I should test making it, but I'll do that one this is complete).
Not for this PR - but I noticed that make build
doesn't build the windows image -- we should probably track that work somewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the suggestion 😃. Please see if it looks good now.
2a4ea06
to
24332bd
Compare
Build Succeeded 👏 Build Id: af499f85-5af1-48bc-b317-c3aafd5d4e0b 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:
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: markmandel, mridulji The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Build Succeeded 👏 Build Id: ea112731-4f1d-40fd-b05e-b9546475661f 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:
|
What type of PR is this?
/kind feature
What this PR does / Why we need it: This PR upgrades the xonotic version to 0.8.5 provided in the examples.
Which issue(s) this PR fixes:
Closes #2664
Special notes for your reviewer: