Project

General

Profile

Actions

Bug #6863

closed

[Documentation] Clarify the different ways to input your tools to Arvados

Added by Bryan Cosca over 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
-
Story points:
-

Description

A quick version from the port-a-pipeline wiki.

  • Install on Docker
    Pull an Arvados-base docker image (I would prefer bcosc/arv-base because I know that works)
    Install wget, wget file into docker image.
    Build tool as normal, install dependencies as needed.
    *note path of tool binary*
    Commit image
    Arv keep docker to upload image
    
  • Put binary in git repo (Only standalone binaries please, we do not want to have a huge git repo [I think...])
    Copy binary or any of your scripts to your git repo.
    Git add
    Git commit
    Git push
    If using run-command, specify path to binary in a command
    If using python SDK, specify path in a variable.
    
  • Put binary in keep
    Input your pre-compiled binary along with the folder it was built in to keep
    Arv-put
    If using run-command, specify path to binary in a command
    If using python SDK, specify path in a variable.
    
Actions #1

Updated by Peter Amstutz over 4 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF