https://dev.arvados.org/https://dev.arvados.org/favicon.ico?15576888422014-03-28T18:48:15ZArvadosArvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=91142014-03-28T18:48:15ZTom Cleggtom@curii.com
<ul><li><strong>Description</strong> updated (<a title="View differences" href="/journals/9114/diff?detail_id=7022">diff</a>)</li></ul> Arvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=93822014-04-09T13:40:48ZTom Cleggtom@curii.com
<ul><li><strong>Assigned To</strong> set to <i>Peter Amstutz</i></li></ul> Arvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=94822014-04-12T22:14:16ZTom Cleggtom@curii.com
<ul></ul><p>Organization much improved. (Someday all of our API pages will have actual information in them like this...!)</p>
api/schema/Job.html
<ul>
<li>"When the job starts, Arvados updates this field to the precise git commit hash used by the job."
<ul>
<li>Prefer "full" (or nothing) rather than "precise". ("Precise hash" sounds weird: what's an imprecise hash?)</li>
</ul>
</li>
<li>"May be a git hash or tag to specify an exact version, or a branch. If it is a branch, use the branch head."
<ul>
<li>In git, a branch is a pointer to a commit -- branch head is not a thing. Suggest: "This can be any git ref that resolves to a commit, such as a full or abbreviated commit hash, a tag, or a branch." </li>
<li>Branches and tags are equally precise. The only ambiguity comes from when they are resolved -- which, unfortunately, currently seems to depend on various subtle factors -- and this could (pathologically) apply to abbrev hashes as well. It is at least safe to say something like "Arvados updates this to a full 40-character commit hash before the job starts." </li>
</ul>
</li>
<li>"The git ref of the the git commit"
<ul>
<li>"git branch, tag, or commit hash" is clearer. Or "git ref (e.g., branch, tag, commit hash)". (Above sentence sounds like each commit has one git ref, which is backwards.)</li>
</ul></li>
</ul>
api/methods/jobs.html
<ul>
<li>version hash → commit hash</li>
<li>"minimum acceptable script version" would be nice to explain more precisely in git language, but I think most people would correctly guess what it does, so maybe OK.</li>
<li>"May be a git hash or tag to specify an exact version, or a branch. If it is a branch, use the branch head."
<ul>
<li>As above.</li>
</ul></li>
</ul> Arvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=94902014-04-13T16:14:34ZTom Cleggtom@curii.com
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>In Progress</i></li></ul> Arvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=95712014-04-15T22:04:23ZTom Cleggtom@curii.com
<ul></ul><p>Good to merge.</p> Arvados - Bug #2488: Update http://doc.arvados.org/api/schema/Job.html re. nondeterministic and repository attributeshttps://dev.arvados.org/issues/2488?journal_id=96002014-04-16T09:26:10ZPeter Amstutzpeter.amstutz@curii.com
<ul><li><strong>Status</strong> changed from <i>In Progress</i> to <i>Resolved</i></li></ul>