-
Notifications
You must be signed in to change notification settings - Fork 644
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove deprecated workflow publish [DSL2]
- Loading branch information
1 parent
6b655b1
commit 1bd7b4a
Showing
5 changed files
with
4 additions
and
95 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
1bd7b4a
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is the recommended alternative to workfow publish then? I actually really like it, because it allows me to have the an explicit statement in the main workflow of where things should go. Otherwise it's hidden in the
nextflow.config
file. It also makes it hard to output the result of multiple sub-workflows to different directories. For example, I perform variant calling with 3 different programs in 3 sub-workflows. The last process in each case is "annotateVcf". However, I want to ouput the resulting vcf file to 3 different directories, depending on sub-workflow. Previously, I was able to do:Without
publish
in the main workflow, this gets very hairy. I actually think a dedicatedpublish
operator would be the best solution (see #1540)