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

Remove generate target from build/test targets #1874

Merged
merged 2 commits into from
Jan 29, 2024

Conversation

andrewsykim
Copy link
Contributor

Why are these changes needed?

Since adding applyconfiguration for generated clients (#1818), code generation has taken longer (~2 mins). We currently run generate for the build / test targets and the additional 2 minutes adds up over time.

This PR removes the generate target from build/test targets, removing the 2 min delay. I was initially hesitant about removing this target because it would make it easier to forget code generation. However, I think this mostly mitigated by the fact that we have checks to verify generated code.

Related issue number

Checks

  • I've made sure the tests are passing.
  • Testing Strategy
    • Unit tests
    • Manual tests
    • This PR is not tested :(

Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
Signed-off-by: Andrew Sy Kim <andrewsy@google.com>
@andrewsykim
Copy link
Contributor Author

@astefanutti @kevin85421 thoughts?

Copy link
Contributor

@astefanutti astefanutti left a comment

Choose a reason for hiding this comment

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

+1, it's pretty conventional to separate code generation from build targets, and have verification checks automated in CI.

@kevin85421 kevin85421 merged commit e2e4208 into ray-project:master Jan 29, 2024
23 checks passed
ryanaoleary pushed a commit to ryanaoleary/kuberay that referenced this pull request Feb 13, 2024
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

3 participants