Arvados

Maybe something like this:

art release create -n 2.4.0 -p project_id -s sprint_id -g arvados=011742f3936e88338e7a2e3f2d92e74b89361958 -g arvados-workbench2=c0bbd8e4f7c38eacece83de646afe2b5689c6b86

• do `art redmine issues create-release-issue -n 2.4.0 -p project_id -s sprint_id -json` which will give us a redmine release ID (will it? check)
• add the git hashes to the release ticket
• create some local state? Or maybe we can just come up with a formatting convention that lets us use the release ticket to keep the git hash state
• kick off the appropriate jenkins jobs for the git hashes

and

art release update -r release_id -g arvados=011742f3936e88338e7a2e3f2d92e74b89361958 -g arvados-workbench2=c0bbd8e4f7c38eacece83de646afe2b5689c6b86

• update the git hashes for the release
• kick off the appropriate jenkins jobs for the git hashes

and

art release test -r release_id

• kick off the appropriate jenkins jobs for the git hashes