add git lfs install - #724
Draft
chrisw-shadow wants to merge 29 commits into
Draft
Conversation
* Updating build and prepare scripts * wget failing due to ssl cert fix * matching linux version formatting across scripts
) * Update additional_bashrc_cmds_noetic * Update Dockerfile * Update Dockerfile * Update Dockerfile * Create sr_quality_of_life.sh * Create additional_bashrc_commands_quality_of_life * move file * move to importable script * testing and tidying * oops * Update additional_bashrc_cmds_noetic * fixes * temp test * Update additional_bashrc_commands_quality_of_life * Update sr_quality_of_life.sh * Update additional_bashrc_commands_quality_of_life * Update sr_quality_of_life.sh * Update sr_quality_of_life.sh * Update Dockerfile * Update additional_bashrc_commands_quality_of_life * Update sr_quality_of_life.sh * Update additional_bashrc_commands_quality_of_life * Update sr_quality_of_life.sh * Update Dockerfile * Update buildspec.yml * Update buildspec.yml * Update sr_quality_of_life.sh * Update sr_quality_of_life.sh --------- Co-authored-by: Build Tools <build.tools@example.com>
…el/ folders (#709) * Rosbustify logic * uuups * Fix typos * Update user variable
* Update additional_bashrc_commands_quality_of_life * Update additional_bashrc_commands_quality_of_life
* Update Noetic Dockerfile * Update Humble Dockerfile * cleanup * Update Dockerfile * Update Dockerfile
* Change tag name for humble image, so that it doesn't specify the the base ubuntu image. The reason to do it is that the upstream image is silently moved from one ubuntu version to the next eventually. * changes to make te build work on the latest AWS ubuntu image * Fix missing space * Try to fix build by allowing higher version of PyYAML * Add needed double quotes to pip install * Add progress=plain option, as it seems to be necessary to see the output of docker build when using buildkit (new docker build engine). * Check what happens if we remove PYTHONUNBUFFERED. (Ansible output is looking odd right now). * Add verbosity * Remove fixed versions from requirements.txt * Remove deprecated json argument * Update ubuntu version name for humble * Fix conditions that checked for ROS2 versions. Add rosdep bash command for humble. * Add condition to ur-client-library role. It only makes sense in noetic. * Fix empy version to avoid error caused by the presence of the debian installed version * Changing rolling base image to be the correct one for development (to deveop packages on ROS2, not to develop ROS2 itself. Changes to allow for a newer codebuild image. * Undo some unnecessary changes * Fix typos in comment * Make requirements.txt compatible with jammy as well as focal * Make json loading compatible with newer versions of python --------- Co-authored-by: Nikolaus Holmes <143398822+niko-holmes@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proposed changes
Please explain the changes you made. Add pictures or videos to explain them better if appropriate.
Checklist
Before posting a PR ensure that from each of the below categories AT LEAST ONE BOX HAS BEEN CHECKED. If more than one category is applicable then more can be checked. Also ensure that the proposed changes have been filled out with relevant information for reviewers.
Tests
Documentation