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

Find alternative to Travis CI for workflows #88

Open
cricketsloan opened this issue Nov 19, 2018 · 1 comment
Open

Find alternative to Travis CI for workflows #88

cricketsloan opened this issue Nov 19, 2018 · 1 comment
Assignees

Comments

@cricketsloan
Copy link

Find alternative to Travis CI for workflows - Dockstore or Jenkins?
Workflow requirements for memory, disk and time to run exceed Travis CI capabilities

┆Issue is synchronized with this JIRA Story
┆Issue Number: TOP-27
┆Epic: Integration tests for all workflows

@cricketsloan
Copy link
Author

➤ Walt Shands commented:

Markus Kinsella at HCA suggested: Honestly, your best bet is probably to get some test data that runs much more quickly. In general, you want automated tests to give pretty quick feedback to developers. It looks like the input cram file isn't all that big; do you know what's taking so much time? One thing you could try is getting a reference that's limited to, say, chromosome 22 if there's some task whose time depends on the reference size.

@cricketsloan cricketsloan changed the title Find alternative to Travis CI for workflows Find alternative to Travis CI for workflows Dec 10, 2018
@aofarrel aofarrel mentioned this issue Dec 4, 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

No branches or pull requests

2 participants