Skip to content

Build single requirement container, log if requirement not in best-practice channels#977

Merged
mvdbeek merged 4 commits intogalaxyproject:masterfrom
mvdbeek:fix_planemo_monitor
Dec 18, 2019
Merged

Build single requirement container, log if requirement not in best-practice channels#977
mvdbeek merged 4 commits intogalaxyproject:masterfrom
mvdbeek:fix_planemo_monitor

Conversation

@mvdbeek
Copy link
Member

@mvdbeek mvdbeek commented Dec 8, 2019

This also revealed quite a headache: We frequently don't specify exact versions in tool requirements (e.g <requirement type="package" version="3.7">conda</requirement>) instead of the full 3.7.1. This is very widespread in Galaxy tools. A single requirement like this will prevent building a container :(.

@mvdbeek mvdbeek force-pushed the fix_planemo_monitor branch from db0627e to 9b2f01c Compare December 8, 2019 15:16
@mvdbeek mvdbeek force-pushed the fix_planemo_monitor branch from 9b2f01c to 326af18 Compare December 8, 2019 15:27
contents = ",".join(target_strings)
f.write(contents)
ctx.vlog("Wrote requirements [%s] to file [%s]" % (contents, target_filename))
with open(target_filename, "a") as f:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess if the file already exists we should not append, isn't it? Is a really needed here?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a leftover from appending to hash.tsv

@mvdbeek mvdbeek merged commit 38edfb7 into galaxyproject:master Dec 18, 2019
@mvdbeek mvdbeek deleted the fix_planemo_monitor branch December 18, 2019 10:53
@bgruening
Copy link
Member

@mvdbeek I think we need a new planemo release. Then we could start testing and migrating the monitor repo ...

@mvdbeek
Copy link
Member Author

mvdbeek commented Dec 19, 2019

We need to wait for the cwltool upgrade so that we can use a yet-to-be released galaxy-tool-util package with the mulled updates.

@nsoranzo nsoranzo changed the title Build single requirement container, log if requirement not in best-pr… Build single requirement container, log if requirement not in best-practice channels Jan 29, 2020
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