Results, artefacts, persistence

[rsuchecki]

We should revisit how GH releases are presented so that the distinction between a run capture release and a regular pipeline release is more obvious - I think this could be done by re-phrasing a few things under

repset/nextflow.config

Lines 186 to 199 in 5def49c

	releaseArgs = [
	REPO : workflow.repository.replaceFirst("^(http[s]?://github\\.com/|git@github\\.com:)","").replaceFirst("\\.git\$",""),
	COMMIT : workflow.commitId,
	LOCAL_FILES : [
	// "${params.outdir}/report.html",
	// "${params.outdir}/biokanga-manuscript.pdf",
	"${params.outdir}/allstats.json",
	"${params.infodir}/runmeta.json",
	"${params.infodir}/trace.tsv"
	],
	RELEASE_TAG: "${workflow.revision}_${workflow.runName}_${workflow.sessionId}",
	RELEASE_NAME: "${workflow.revision} - results and metadata for run '${workflow.runName}'",
	RELEASE_BODY: "Release created and artefacts uploaded for run '${workflow.runName}', session ID ${workflow.sessionId}, commit ${workflow.commitId}, see assets for more details."
	]

Alternatively, we could re-consider what we capture and where we deposit - perhaps we should be using https://developers.zenodo.org/#rest-api directly?

[rsuchecki]

Some changes already applied:

• run release & artefacts to be published to a fork
• more specific tag generated for a release (date/timestamp, releases kept in order on GH)
• more details in release body