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

Install dependencies defined on packages.apt file in source code #317

Merged
merged 5 commits into from
Oct 9, 2020

Conversation

chapulina
Copy link
Contributor

@chapulina chapulina commented Oct 8, 2020

Related tickets: #190 / gazebo-tooling/action-gz-ci#15 / #316

All Ignition libraries now have .github/ci/package*.apt files in their source code defining all their debian dependencies. An elaborate example is ign-gazebo, which has 3 packages files:

  • packages.apt for dependencies common to all platforms
  • packages-bionic.apt for dependencies specific to Bionic
  • packages-focal.apt for dependencies specific to Focal

These files are being used by the GitHub actions CI in https://github.com/ignition-tooling/action-ignition-ci , and we can use them here too. Having these files living next to the source code make it easier to update dependencies at the same time as the source code changes.

Nothing is broken if a library doesn't have packages.apt files.

This was tested here, see how the packages listed here ended up in the PACKAGES_CACHE_AND_CHECK_UPDATES variable.

With this change, I think we don't need to keep dependencies_archive.sh updated whenever dependencies are added to Ignition libraries anymore? Not sure if that's used for something other than CI.

Signed-off-by: Louise Poubel <[email protected]>
Signed-off-by: Louise Poubel <[email protected]>
@scpeters
Copy link
Contributor

scpeters commented Oct 8, 2020

how do you feel about re-adding #305 into this PR so we can test that it's working?

@scpeters
Copy link
Contributor

scpeters commented Oct 8, 2020

I like storing this metadata in the repository much better than in dependencies_archive.sh, so I think this is a great idea; I'd just like to incorporate the changes from #305 and run a bunch of release branch CI jobs using this branch

@chapulina
Copy link
Contributor Author

This branch doesn't include #316 , so the test mentioned above is still at a state where #305 was in: https://build.osrfoundation.org/job/ignition_fuel-tools-ci-pr_any-ubuntu_auto-amd64/431/console

I'll add those changes here again just in case.

@chapulina
Copy link
Contributor Author

Updated this branch and reverted #316 .

Triggered new build for gazebosim/gz-transport#188, which this is meant to fix:

Build Status

@chapulina
Copy link
Contributor Author

run a bunch of release branch CI jobs using this branch

Just saw you said a bunch, so here we go:

  • Version without packages.apt: ign-math5 Build Status
  • Blueprint version: ign-rendering2: Build Status
  • Version used in multiple collections: ign-common3: Build Status

@scpeters
Copy link
Contributor

scpeters commented Oct 8, 2020

ok, I should have said, "let's test all the dome jobs whose build scripts were affected by #305", so the ign-transport build is a good one, but I'd like to test the others too. I'll start them and post build badges

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