Alit/mamba 2 0 migration
State: closed | Pull request: yes
Labels: name: NLP

name: Run CICD

# What does this PR do ?

Add a one line overview of what this PR aims to accomplish.

**Collection**: [Note which collection this PR will affect]

# Changelog 
- Add specific line by line info of high level changes in this PR.

# Usage
* You can potentially add a usage example below

```python
# Add a code snippet demonstrating how to use this 
```

# GitHub Actions CI

The Jenkins CI system has been replaced by GitHub Actions self-hosted runners.

The GitHub Actions CI will run automatically when the "Run CICD" label is added to the PR.
To re-run CI remove and add the label again.
To run CI on an untrusted fork, a NeMo user with write access must first click "Approve and run".

# Before your PR is "Ready for review"
**Pre checks**:
- [ ] Make sure you read and followed [Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md)
- [ ] Did you write any new necessary tests?
- [ ] Did you add or update any necessary documentation?
- [ ] Does the PR affect components that are optional to install? (Ex: Numba, Pynini, Apex etc)
  - [ ] Reviewer: Does the PR have correct import guards for all optional libraries?
  
**PR Type**:
- [ ] New Feature
- [ ] Bugfix
- [ ] Documentation

If you haven't finished some of the above items you can still open "Draft" PR.


## Who can review?

Anyone in the community is free to review the PR once the checks have passed. 
[Contributor guidelines](https://github.com/NVIDIA/NeMo/blob/main/CONTRIBUTING.md) contains specific people who can review PRs to various areas.

# Additional Information
* Related to # (issue)


Thanks for this, looks good! My one comment is that we want to move away from scripts in the example-dir that we use inside GH-actions etc. For that, we would like to move to using a recipe (like we defined for many models [here](https://github.com/NVIDIA/NeMo/tree/e76afdfc28a1835fcf8aac97c07261e24ca0407d/nemo/collections/llm/recipes), a recipe should contain everything for training so model/data/trainer/etc.). 

We are currently working on automatically exposing those in the CLI, for more docs around that see [this](https://github.com/NVIDIA/NeMo/blob/e76afdfc28a1835fcf8aac97c07261e24ca0407d/examples/llm/pretrain/README.md) readme inside this [WIP PR](https://github.com/NVIDIA/NeMo/pull/10300).

So would be great if you could add one (or a few) recipes for this model, you could for instance take llama3_8b as an [example](https://github.com/NVIDIA/NeMo/blob/e76afdfc28a1835fcf8aac97c07261e24ca0407d/nemo/collections/llm/recipes/llama3_8b.py).

> Thanks for this, looks good! My one comment is that we want to move away from scripts in the example-dir that we use inside GH-actions etc. For that, we would like to move to using a recipe (like we defined for many models [here](https://github.com/NVIDIA/NeMo/tree/e76afdfc28a1835fcf8aac97c07261e24ca0407d/nemo/collections/llm/recipes), a recipe should contain everything for training so model/data/trainer/etc.).
> 
> We are currently working on automatically exposing those in the CLI, for more docs around that see [this](https://github.com/NVIDIA/NeMo/blob/e76afdfc28a1835fcf8aac97c07261e24ca0407d/examples/llm/pretrain/README.md) readme inside this [WIP PR](https://github.com/NVIDIA/NeMo/pull/10300).
> 
> So would be great if you could add one (or a few) recipes for this model, you could for instance take llama3_8b as an [example](https://github.com/NVIDIA/NeMo/blob/e76afdfc28a1835fcf8aac97c07261e24ca0407d/nemo/collections/llm/recipes/llama3_8b.py).

@marcromeyn Thanks for your comment, I will remove the script from the MR