create hello-nf-on-vwb example#24
Open
samhornstein wants to merge 5 commits into
Open
Conversation
…sults vs work dir
samhornstein
marked this pull request as ready for review
July 21, 2026 22:54
samhornstein
requested review from
PeterSu92 and
kirtanav98
and removed request for
PeterSu92
July 21, 2026 22:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
nextflow/hello-nf-on-vwb/, a minimal, self-contained Nextflow pipeline that runs unchanged locally or on Verily Workbench via Google Batch. Modeled on the officialHello Nextflow training: reads greetings from a CSV, uppercases them in parallel, collects into one file. The point is the
Workbench wiring (profiles, params, containers, GCS work directory), not the string processing.
Also links the new example from
nextflow/README.md.What's included
main.nfplusmodules/(sayHello,convertToUpper,collectGreetings) and bundled sampledata/greetings.csv.nextflow.configwith three profiles:standard— local, no containerdocker— local, containerizedverily_workbench— Google Batch executor, private-address VMs, Workbench VPC/subnet, project and service account pulled from env varstest-params.yamlfor overriding inputs/outdir.README.mdcovering local runs, Workbench setup (bucket creation), and running from both the Workflows UI andwb nextflowCLI.Design notes
cpus/memorylive on theprocessblock (nf-coreconf/base.configpattern), not the executor profile; Google Batch sizes the VM from these. Boot disk stays in theprofile.
outdir/work_dirmust be fullgs://paths on Workbench — pipeline fails fast otherwise.debian:stable-slimimage by default; README documents swapping in a private Artifact Registry image.Commits
feat(hello-nf-on-vwb): minimal Nextflow-on-Verily-Workbench examplerefactor: task cpus/memory to process block, boot disk in profile (nf-core pattern)refactor: rename profile toverily_workbench, params over env varsdocs/fix: README simplification, droplogsPath, clarify results vs work dirTest plan
nextflow run main.nf -profile standardproducesresults/COLLECTED-greetings.txtnextflow run main.nf -profile docker(Docker running)wb nextflow run main.nf -profile verily_workbenchwithgs://paths