Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Template standardization #10

Merged
merged 101 commits into from
Nov 17, 2023
Merged

Template standardization #10

merged 101 commits into from
Nov 17, 2023

Conversation

l-mansouri
Copy link
Contributor

@l-mansouri l-mansouri commented Nov 17, 2023

Overview

This PR aims to standardize the pipeline to better conform to the template. DO NOT MIND the insane amount of COMMITS, there was an issue with the sync in my local repo! SORRY!

Purpose

This PR aims to standardize the pipeline to better conform to the template. It mainly involves:

  • parametrisation of the container name, with the url of the container bein in conf/quay.config
  • parametrisation of the paths of the reference data for the pipeline to better accommodate for different AWS regions using the params.reference_data_bucket parameter
  • the collection of the reference/pipeline specific data in conf/data/data.conf
  • implementation of extra config files as needed to better adhere to the guidelines

Acceptance Criteria/Jira Ticket

DEL-16132

Changes

  • Refactors the container names
  • Refactors nextflow.config accordingly
  • Refactors conf/data/data.config to accommodate for the new parametrisation of the path
  • Refactors the documentation to reflect changes
  • Moved config file to better reflect the template
  • Added some config file to better reflect the template

Internal CloudOS Tests

Not necessary if run in Internal CloudOS CI

Client CloudOS Tests

PR Checklist

Author to check:

  • The PR title is informative and begins with appropriate [Fix:|Feat:|Docs:] based on PR type
  • This PR is raised to dev branch for DSL1 or DSL2-dev for DSL2 translations
  • The description contains the acceptance criteria or link to the associated Jira ticket
  • The description contains links to CloudOS tests covering all test cases in client environment

Reviewer to check:

  • A new test profile covering new functions for acceptance criteria is created if it does not already exist
  • Nextflow configs have associated profiles named to match the config basename
  • The Jenkinsfile has been updated with current Nextflow profiles
  • The internal_lifebit_cloudos_ci.yml has been updated to run all current Nextflow profiles
  • Redundant tests have been removed
  • The README.md has been updated with parameter changes and current results/ and conforms to the README.md guidelines
  • The code is logical, readable, reasonably optimal and meets the acceptance criteria
  • The containers folder has been updated with the necessary containers to run this pipeline if needed

nextflow.config Show resolved Hide resolved
@l-mansouri l-mansouri merged commit d7736c8 into dev Nov 17, 2023
0 of 3 checks passed
@l-mansouri l-mansouri deleted the template_standardization branch November 17, 2023 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants