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

Pin all versions of python dependencies. #759

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

clalancette
Copy link
Contributor

This allows us to be in control of our destiny,
and not have random python upstream package updates destroy the entire buildfarm.

We accomplish this through 3 different mechanisms, depending on the platform:

  1. Ubuntu - we install everything from debian packages, and nothing from pip. Because Ubuntu promises to not to breaking changes within a distribution, this guarantees we won't break. This also serves as our canonical version of what should work.
  2. RHEL - For RHEL-9, we install everything from RPM packages, and nothing from pip. For RHEL-8, we install most everything from RPM packages, with the exception of mypy, pytest, and pytest-rerunfailures. Since RHEL/EPEL typically doesn't update major versions within a release, we typically won't break.
  3. Windows - We install all python packages via pip, and we constrain the versions we install to those in Ubuntu. This means that we'll always match what works on Ubuntu and we should always work.

Still a draft, as I need to run CI here and see what happens.

@clalancette
Copy link
Contributor Author

clalancette commented Mar 20, 2024

Initial CI:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • Windows Build Status

@clalancette
Copy link
Contributor Author

Note that this needs ros-infrastructure/ros2-cookbooks#66 as well.

@clalancette
Copy link
Contributor Author

clalancette commented Mar 21, 2024

Here's additional CI:

  • RHEL Build Status
  • Windows Debug Build Status

This allows us to be in control of our destiny,
and not have random python upstream package updates
destroy the entire buildfarm.

We accomplish this through 3 different mechanisms,
depending on the platform:

1.  Ubuntu - we install everything from debian packages,
             and nothing from pip.  Because Ubuntu promises
             to not to breaking changes within a distribution,
             this guarantees we won't break.  This also
             serves as our canonical version of what should work.
2.  RHEL - For RHEL-9, we install everything from RPM packages,
           and nothing from pip.  For RHEL-8, we install most
           everything from RPM packages, with the exception of
           mypy, pytest, and pytest-rerunfailures.  Since RHEL/EPEL
           typically doesn't update major versions within a release,
           we typically won't break.
3.  Windows - We install all python packages via pip, and we constrain
              the versions we install to those in Ubuntu.  This means
              that we'll always match what works on Ubuntu and we should
              always work.

Signed-off-by: Chris Lalancette <[email protected]>
@clalancette clalancette force-pushed the clalancette/windows-pip-install branch from 2120d5d to 496ae0e Compare March 21, 2024 18:55
@claraberendsen
Copy link
Contributor

Re-running CI on windows with the latest changes as sanity check:
Build Status

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.

2 participants