Skip to content
This repository was archived by the owner on Mar 8, 2025. It is now read-only.

Conversation

@jtmcdole
Copy link
Member

Instead of tracking engine.version, dynamically determine its value using the Git hash.

The logic for determining the version is as follows:

  • When running on a bot or for a release, engine.version is set to the HEAD commit hash.
  • In all other cases, engine.version is set to the merge-base between HEAD and the master branch.

This change also updates .ci.yaml to detect actual changes to the engine, rather than relying on the previously tracked engine.version file.

@jtmcdole
Copy link
Member Author

I expect this to fail after the engine is built because the flutter tests are still looking in some other castle / realm

@jtmcdole
Copy link
Member Author

Once cocoon and luci changes roll out; we can retry this one and should see tests passing and downloading the correct engine.

@jtmcdole
Copy link
Member Author

Changes rolled out. Will retry this with an empty push

@jtmcdole
Copy link
Member Author

I still don't know why Web isn't being built. I'm off of master.

When running on a bot or release; engine.version should be the HEAD. When running
in other cases, engine.version should be based on a commit in master.

engine.version shouldn't be tracked - so ci.yaml needs to be updated to
look for real changes to the engine.
@jtmcdole
Copy link
Member Author

Cocoon & LUCI updated; running a new set of tests after removing non-existing tests.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants