-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Use tardis-refdata from Azure mirror (CI/CD) #1304
Conversation
@@ -27,43 +24,28 @@ jobs: | |||
maxParallel: 2 | |||
|
|||
steps: | |||
- checkout: self | |||
|
|||
- checkout: git://TARDIS/tardis-refdata |
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.
can we specify branches here?
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.
Yes. According to the documentation:
- checkout: git://MyProject/MyRepo@features/tools # checks out the features/tools branch
- checkout: git://MyProject/MyRepo@refs/heads/features/tools # also checks out the features/tools branch
- checkout: git://MyProject/MyRepo@refs/tags/MyTag # checks out the commit referenced by MyTag.
Codecov Report
@@ Coverage Diff @@
## master #1304 +/- ##
==========================================
+ Coverage 80.54% 81.50% +0.95%
==========================================
Files 41 46 +5
Lines 3423 3784 +361
==========================================
+ Hits 2757 3084 +327
- Misses 666 700 +34 Continue to review full report at Codecov.
|
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.
looks very good.
* Use tardis-refdata from Azure mirror * Checkout `self` repo * Debugging pipeline * Debugging pipeline * Debugging pipeline * Fetch just necessary refdata * (revert) Fetch just necessary refdata * Download atom data from Azure * Download atom data from GitHub LFS * Debugging pipeline * Debugging pipeline * Debugging pipeline * Debugging pipeline * Debugging pipeline * Re-writing CI doc section (1) * Moving to a template schema * Moving to a template schema (2) * Moving to a template schema (3) * Moving to a template schema (4) * Moving to a template schema (5) * Moving to a template schema (6) * Moving to a template schema (7) * Moving to a template schema (8) * Moving to a template schema (9) * Moving to a template schema (10) * Moving to a template schema (11) * Moving to a template schema (12) * Moving to a template schema (13) * Moving to a template schema (15) * Moving to a template schema (16) * Moving to a template schema (16) * Moving to a template schema (17) * Moving to a template schema (18) * Moving to a template schema (19) * Moving to a template schema (20) * Moving to a template schema (21) * Moving to a template schema (21) * Moving to a template schema (22) * Moving to a template schema (23) * Moving to a template schema (24) * Moving to a template schema (25) * Moving to a template schema (26) * Moving to a template schema (27) * Moving to a template schema (28) * Finished template [skip-ci] * Minor changes to step names * Minor changes to step names * Complete documentation * Use custom variables for repo paths * Minor changes to documentation * Minor changes * More documentation on pipelines * Minor changes * Minor changes
Description
tardis-sn/tardis-refdata
repository in Azure Repos.simple_test_framework.yml
pipelinetardis/data/atomic_data_repo.yml
default
template for TARDIS pipelines with common steps, then move most of thesimple_test_framework.ym;
pipeline steps to this template.Next thing to do is take care of NumPy/macOS issue.
Motivation and Context
Recently we ran out of GitHub LFS bandwidth. To avoid this problem in the future we mirrored the reference data repository to Azure Repos (no LFS limits).
Also, all the TARDIS pipeline share common steps, such as configuring
conda
and installing the TARDIS environment. The adoption of a template allows us to make pipelines easier to create and maintain.How Has This Been Tested?
Tests on Azure.
Screenshots (if appropriate):
Types of changes
Checklist: