After a bit of a struggle with the pds-doi-service build (and its unprecedented 2 hour Roundup time) it became apparent that pds-doi-service had in its dependencies several packages (pygit2, importlib-metadata, importlib-resources, beautifulsoup4) that it wasn't using. But it had specified versions of those packages in its install_requires that were incompatible with the tools the Roundup was using (pds-github-util and especially twine).
This helped reveal that pds-doi-service didn't need these redundant dependencies. But it also revealed that the Roundup's own dependencies could conflict with those of the packages it builds.
The Roundup should build packages in a protected environment, perhaps using a Python virtual environment.
📜 To Reproduce
Create a new package pds-problem
In pds-problem's setup.cfg include the dependency beautifulsoup4==4.8.2.
Add the unstable-cicd.yaml workflow to the pds-problem repository.
🐛 Describe the bug
After a bit of a struggle with the
pds-doi-service
build (and its unprecedented 2 hour Roundup time) it became apparent thatpds-doi-service
had in its dependencies several packages (pygit2
,importlib-metadata
,importlib-resources
,beautifulsoup4
) that it wasn't using. But it had specified versions of those packages in itsinstall_requires
that were incompatible with the tools the Roundup was using (pds-github-util
and especiallytwine
).This helped reveal that
pds-doi-service
didn't need these redundant dependencies. But it also revealed that the Roundup's own dependencies could conflict with those of the packages it builds.The Roundup should build packages in a protected environment, perhaps using a Python virtual environment.
📜 To Reproduce
pds-problem
pds-problem
'ssetup.cfg
include the dependencybeautifulsoup4==4.8.2
.unstable-cicd.yaml
workflow to thepds-problem
repository.🕵️ Expected behavior
It should go all right.
📚 Version of Software Used
roundup-action@main
🩺 Test Data / Additional context
See