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

Explain how to test a Drake canary #55

Open
jwnimmer-tri opened this issue Jul 6, 2023 · 1 comment
Open

Explain how to test a Drake canary #55

jwnimmer-tri opened this issue Jul 6, 2023 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@jwnimmer-tri
Copy link
Contributor

Currently, our examples are pinned run against the latest stable version of Drake.

During development, it's sometimes helpful to run against a WIP build of Drake instead, to see the effect of Drake changes.

We should make it as easy as practical to do that, and document how to do it.

@jwnimmer-tri jwnimmer-tri added the documentation Improvements or additions to documentation label Jul 6, 2023
@jwnimmer-tri jwnimmer-tri self-assigned this Jul 6, 2023
@jwnimmer-tri
Copy link
Contributor Author

Roughly, I believe it would go like:

  • Open a Drake PR.
  • Trigger an expermental Wheel build job on the PR (see https://drake.mit.edu/jenkins.html).
  • Find the wheel's URL in the log of the Wheel build. (There will be multiple wheels build for different Python versions. Find the wheel that matches the Python version used for this code at the time.)
  • Change examples/requirements.in to replace drake with the experimental wheel's URL.
  • Re-run ./bazel run //examples:requirements.update -- --upgrade to switch the lockfile to the experimental wheel.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant