X-Git-Url: https://git.arvados.org/arvados.git/blobdiff_plain/7bd12f51c864ec78fc93f0fa95acf796a4999afc..224f384d411bb1b4cccc7165c55bb64fd5c695ad:/doc/user/tutorials/tutorial-submit-job.html.textile.liquid?ds=inline
diff --git a/doc/user/tutorials/tutorial-submit-job.html.textile.liquid b/doc/user/tutorials/tutorial-submit-job.html.textile.liquid
index eaafe96130..47e8dc750c 100644
--- a/doc/user/tutorials/tutorial-submit-job.html.textile.liquid
+++ b/doc/user/tutorials/tutorial-submit-job.html.textile.liquid
@@ -5,54 +5,28 @@ navmenu: Tutorials
title: "Running on an Arvados cluster"
...
+{% include 'pipeline_deprecation_notice' %}
+
This tutorial demonstrates how to create a pipeline to run your crunch script on an Arvados cluster. Cluster jobs can scale out to multiple nodes, and use @git@ and @docker@ to store the complete system snapshot required to achieve reproducibilty.
{% include 'tutorial_expectations' %}
This tutorial uses @$USER@ to denote your username. Replace @$USER@ with your user name in all the following examples.
-Also, this tutorial uses the @tutorial@ arvados repository created in "Add new arvados repository":add-new-repository.html as the example repository.
-
-h2. Clone arvados repository
-
-All Crunch scripts are managed through the Git revision control system. Before you start using Git, you should do some basic configuration (you only need to do this the first time):
-
-
-~$ git config --global user.name "Your Name"
-~$ git config --global user.email $USER@example.com
git@git.{{ site.arvados_api_host }}:$USER/tutorial.git
-~$ cd $HOME # (or wherever you want to install)
-~$ git clone git@git.{{ site.arvados_api_host }}:$USER/tutorial.git
-Cloning into 'tutorial'...
$ man gittutorial
+h2. Clone Arvados repository
-or *"search Google for Git tutorials":http://google.com/#q=git+tutorial*.
-{% include 'notebox_end' %}
+Please clone the *tutorial* repository using the instructions from "Working with Arvados git repository":git-arvados-guide.html, if you have not yet cloned already.
h2. Creating a Crunch script
-Start by entering the @tutorial@ directory created by @git clone@. Next create a subdirectory called @crunch_scripts@ and change to that directory:
+Start by entering the @tutorial@ directory created by @git clone@. Next, create a subdirectory called @crunch_scripts@ and change to that directory:
~$ cd $USER
-~/$USER$ mkdir crunch_scripts
-~/$USER$ cd crunch_scripts
+>~$ cd tutorial
+~/tutorial$ mkdir crunch_scripts
+~/tutorial$ cd crunch_scripts
~/tutorial/crunch_scripts$ git add
Next, commit your changes. All staged changes are recorded into the local git repository:
-~/tutorial/crunch_scripts$ git commit -m"my first script"
+~/tutorial/crunch_scripts$ git commit -m "my first script"
[master (root-commit) 27fd88b] my first script
1 file changed, 45 insertions(+)
create mode 100755 crunch_scripts/hash.py
@@ -104,7 +78,7 @@ In the editor, enter the following template:
{% code 'tutorial_submit_job' as javascript %}
-* @"repository"@ is the name of a git repository to search for the script version. You can access a list of available git repositories on the Arvados Workbench in the *Manage account* page using the top navigation menu icon.
+* @"repository"@ is the name of a git repository to search for the script version. You can access a list of available git repositories on the Arvados Workbench in the *Repositories* page using the top navigation menu icon.
* @"script_version"@ specifies the version of the script that you wish to run. This can be in the form of an explicit Git revision hash, a tag, or a branch (in which case it will use the HEAD of the specified branch). Arvados logs the script version that was used in the run, enabling you to go back and re-run any past job with the guarantee that the exact same code will be used as was used in the previous run.
* @"script"@ specifies the filename of the script to run. Crunch expects to find this in the @crunch_scripts/@ subdirectory of the Git repository.
* @"runtime_constraints"@ describes the runtime environment required to run the job. These are described in the "job record schema":{{site.baseurl}}/api/schema/Job.html