-
Notifications
You must be signed in to change notification settings - Fork 87
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
shed_upload silent if missing .shed.yml include files #158
Labels
Comments
jmchilton
added a commit
to jmchilton/planemo
that referenced
this issue
May 1, 2015
- Shed actions (e.g. upload) will fail for that repository. - Shed linting will warn about this. Fixes galaxyproject#158 reported by @peterjc.
Not sure it is meant to be this noisy, but the example does fail now :)
|
jmchilton
added a commit
to jmchilton/planemo
that referenced
this issue
May 1, 2015
For shed operations - catch exceptions, log them, but continue to completion and then return a 254 exit code at the end indicating there were problems with one or more repositories. This behavior has can be disabled with any of the shed operations using the new --fail_fast option. Clean up noisy exception reported by @peterjc @ galaxyproject#158 (comment) (unless --fail_fast is used - then you get the full stack trace). Tests. Fixes galaxyproject#114.
jmchilton
added a commit
to jmchilton/planemo
that referenced
this issue
May 1, 2015
For shed operations - catch exceptions, log them, but continue to completion and then return a 254 exit code at the end indicating there were problems with one or more repositories. This behavior has can be disabled with any of the shed operations using the new --fail_fast option. Clean up noisy exception reported by @peterjc @ galaxyproject#158 (comment) (unless --fail_fast is used - then you get the full stack trace). Tests. Fixes galaxyproject#114.
jmchilton
added a commit
to jmchilton/planemo
that referenced
this issue
May 1, 2015
For shed operations - catch exceptions, log them, but continue to completion and then return a 254 exit code at the end indicating there were problems with one or more repositories. This behavior has can be disabled with any of the shed operations using the new --fail_fast option. Clean up noisy exception reported by @peterjc @ galaxyproject#158 (comment) (unless --fail_fast is used - then you get the full stack trace). Tests. Fixes galaxyproject#114.
This was referenced May 5, 2015
jmchilton
added a commit
to jmchilton/planemo
that referenced
this issue
Oct 20, 2015
- Shed actions (e.g. upload) will fail for that repository. - Shed linting will warn about this. Fixes galaxyproject#158 reported by @peterjc.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
My reading of the code suggests that the default
include
value is**
(all files next to the.shed.yml
file). I have tried adding an explicit listing of files, e.g.This fails to complain about missing
venn_list_with_typo.py
:On the positive side, it did not include
venn_list.py
because it wasn't asked to (deliberate mismatch withvenn_list_with_typo.py
).I want this example to fail, complaining that
venn_list_with_typo.py
was listed in the includes, but not found. Ideally the error would list all named but missing files, but just the first missing file would be acceptable.As an aside, would checking the include files exist also fall under
planemo lint
functionality for validating the.shed.yml
?The text was updated successfully, but these errors were encountered: