Auto-update from backup job
This commit is contained in:
parent
46ac68822c
commit
1727f2b157
@ -0,0 +1 @@
|
||||
This is a test file
|
78
data/282180fe7e5d9cbf297f2f0ef813cffe60ce2328/README.md
Normal file
78
data/282180fe7e5d9cbf297f2f0ef813cffe60ce2328/README.md
Normal file
@ -0,0 +1,78 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is a git repository called `devops-technical-test-data`.
|
||||
|
||||
The repository `devops-technical-test-data` is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `datestamp-test` branch on the `devops-technical-test-data` repository.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the branch `datestamp-test` of the repository.
|
||||
|
||||
The execution of the script should be carried with a github-action / gitlab-pipeline or any other git automated workflow.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `devops-technical-test-data`.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate_backup_repository` should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
4
data/3724d6a1366feafe6366403ff394ccff940dde62/doc.txt
Normal file
4
data/3724d6a1366feafe6366403ff394ccff940dde62/doc.txt
Normal file
@ -0,0 +1,4 @@
|
||||
This is a doc
|
||||
Hello, world !
|
||||
|
||||
Biology, regarded instance, on average, less
|
1
data/46fe26c9dcf2354a0ed3f304ed6818de9606f7b5/doc.txt
Normal file
1
data/46fe26c9dcf2354a0ed3f304ed6818de9606f7b5/doc.txt
Normal file
@ -0,0 +1 @@
|
||||
This is a doc
|
2
data/47998b5317e66b3bd456cfb07268c93e223704f2/doc.txt
Normal file
2
data/47998b5317e66b3bd456cfb07268c93e223704f2/doc.txt
Normal file
@ -0,0 +1,2 @@
|
||||
This is a doc
|
||||
Hello, world !
|
@ -0,0 +1 @@
|
||||
Tidsskrift, Band gender equality and
|
@ -0,0 +1 @@
|
||||
This is project1
|
@ -0,0 +1 @@
|
||||
Being conveyed democratic and republican based on the location where
|
@ -0,0 +1,3 @@
|
||||
This is project1
|
||||
|
||||
Of modules Matter. Princeton University Press. ISBN 0691024170. "FY 2012 Arts in Media
|
@ -0,0 +1 @@
|
||||
Not members is solely a federal republic in central-western Europe. It is
|
84
data_main/005a9f74f588073a321f45e7f527b0f09df6b3c7/README.md
Normal file
84
data_main/005a9f74f588073a321f45e7f527b0f09df6b3c7/README.md
Normal file
@ -0,0 +1,84 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is the `DD-MM-YYYY-test` branch of the current `descartes-underwriting/devops-technical-test-data` git repository.
|
||||
|
||||
## Property
|
||||
|
||||
The `descartes-underwriting/devops-technical-test-data` repository is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `DD-MM-YYYY-test` branch multiple times every day.
|
||||
|
||||
The `DD-MM-YYYY-test` branch name will be adapted using standard datetime convention eg: `01-01-2022-test` for the 1st of January 2022.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `candidate/descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the changes fo the branch `DD-MM-YYYY-test` of the `descartes-underwriting/devops-technical-test-data` repository.
|
||||
|
||||
The execution of the script should be carried out with a github-action / gitlab-pipeline or any other tool automating git workflow on your git project.
|
||||
|
||||
It is highly recommended to use a scheduling tool to execute the back up process.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `descartes-underwriting/devops-technical-test-data`.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `descartes-underwriting/devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate/descartes-backup-project` repository should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
@ -0,0 +1 @@
|
||||
This is a test file
|
78
data_main/282180fe7e5d9cbf297f2f0ef813cffe60ce2328/README.md
Normal file
78
data_main/282180fe7e5d9cbf297f2f0ef813cffe60ce2328/README.md
Normal file
@ -0,0 +1,78 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is a git repository called `devops-technical-test-data`.
|
||||
|
||||
The repository `devops-technical-test-data` is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `datestamp-test` branch on the `devops-technical-test-data` repository.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the branch `datestamp-test` of the repository.
|
||||
|
||||
The execution of the script should be carried with a github-action / gitlab-pipeline or any other git automated workflow.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `devops-technical-test-data`.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate_backup_repository` should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
@ -0,0 +1 @@
|
||||
This is a doc
|
@ -0,0 +1,2 @@
|
||||
This is a doc
|
||||
Hello, world !
|
89
data_main/59e9ddff4dea9f744a2b84f6183c84afae559279/README.md
Normal file
89
data_main/59e9ddff4dea9f744a2b84f6183c84afae559279/README.md
Normal file
@ -0,0 +1,89 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is the `DD-MM-YYYY-test` branch of the current `descartes-underwriting/devops-technical-test-data` git repository.
|
||||
|
||||
## Property
|
||||
|
||||
The `descartes-underwriting/devops-technical-test-data` repository is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `DD-MM-YYYY-test` branch multiple times every day.
|
||||
|
||||
The `DD-MM-YYYY-test` branch name will be adapted using standard datetime convention eg: `01-01-2022-test` for the 1st of January 2022.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `candidate/descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
Especially:
|
||||
|
||||
* <https://github.com/alexandreCameron>
|
||||
* <https://github.com/Mareak>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the changes fo the branch `DD-MM-YYYY-test` of the `descartes-underwriting/devops-technical-test-data` repository.
|
||||
|
||||
The execution of the script should be carried out with a github-action / gitlab-pipeline or any other tool automating git workflow on your git project.
|
||||
|
||||
It is highly recommended to use a scheduling tool to execute the back up process.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `descartes-underwriting/devops-technical-test-data`.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `descartes-underwriting/devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate/descartes-backup-project` repository should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
91
data_main/729e5d2addf0a3566e454ddccf549041f2e9ab17/README.md
Normal file
91
data_main/729e5d2addf0a3566e454ddccf549041f2e9ab17/README.md
Normal file
@ -0,0 +1,91 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is the `DD-MM-YYYY-test` branch of the current `descartes-underwriting/devops-technical-test-data` git repository.
|
||||
|
||||
## Property
|
||||
|
||||
The `descartes-underwriting/devops-technical-test-data` repository is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `DD-MM-YYYY-test` branch multiple times every day.
|
||||
|
||||
The `DD-MM-YYYY-test` branch name will be adapted using standard datetime convention eg: `01-01-2022-test` for the 1st of January 2022.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `candidate/descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
Especially:
|
||||
|
||||
* <https://github.com/alexandreCameron>
|
||||
* <https://github.com/Mareak>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the changes fo the branch `DD-MM-YYYY-test` of the `descartes-underwriting/devops-technical-test-data` repository.
|
||||
|
||||
The execution of the script should be carried out with a github-action / gitlab-pipeline or any other tool automating git workflow on your git project.
|
||||
|
||||
It is highly recommended to use a scheduling tool to execute the back up process.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `descartes-underwriting/devops-technical-test-data`.
|
||||
|
||||
Starting from the initial commit [282180fe7e5d9cbf297f2f0ef813cffe60ce2328](https://github.com/descartes-underwriting/devops-technical-test-data/commit/282180fe7e5d9cbf297f2f0ef813cffe60ce2328), all the history should be backup.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `descartes-underwriting/devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate/descartes-backup-project` repository should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
100
data_main/77feffe3f6ccdf44a5f4150b3258e1a745e57807/README.md
Normal file
100
data_main/77feffe3f6ccdf44a5f4150b3258e1a745e57807/README.md
Normal file
@ -0,0 +1,100 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is the `DD-MM-YYYY-test` branch of the current `descartes-underwriting/devops-technical-test-data` git repository.
|
||||
|
||||
## Property
|
||||
|
||||
The `descartes-underwriting/devops-technical-test-data` repository is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `DD-MM-YYYY-test` branch multiple times every day.
|
||||
|
||||
The `DD-MM-YYYY-test` branch name will be adapted using standard datetime convention eg: `01-01-2022-test` for the 1st of January 2022.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
If something is not clear, you can ask questions to the recruiter.
|
||||
|
||||
When submitting your project, your version should **not be draft** but complete and following best practices.
|
||||
|
||||
The solution should be saved on a **private** `descartes-devops` repository on your github account.
|
||||
|
||||
The solution should include:
|
||||
|
||||
- source code
|
||||
- test code
|
||||
|
||||
When the final version is ready:
|
||||
|
||||
1. Send an email to the recruiter indicating that you finished the project and sharing the url of the project
|
||||
2. Grant access to:
|
||||
|
||||
- <https://github.com/alexandreCameron>
|
||||
- <https://github.com/Mareak>
|
||||
- <https://github.com/jrdescartes>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the changes fo the branch `DD-MM-YYYY-test` of the `descartes-underwriting/devops-technical-test-data` repository.
|
||||
|
||||
The execution of the script should be carried out with a github-action / gitlab-pipeline or any other tool automating git workflow on your git project.
|
||||
|
||||
It is highly recommended to use a scheduling tool to execute the back up process.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `descartes-underwriting/devops-technical-test-data`.
|
||||
|
||||
Starting from the initial commit [282180fe7e5d9cbf297f2f0ef813cffe60ce2328](https://github.com/descartes-underwriting/devops-technical-test-data/commit/282180fe7e5d9cbf297f2f0ef813cffe60ce2328), all the history should be backup.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `descartes-underwriting/devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate/descartes-backup-project` repository should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
@ -0,0 +1 @@
|
||||
This is project1
|
92
data_main/c37c77fbf9d12418c83e1510fb0bdece8bd2e11c/README.md
Normal file
92
data_main/c37c77fbf9d12418c83e1510fb0bdece8bd2e11c/README.md
Normal file
@ -0,0 +1,92 @@
|
||||
# Descartes Underwriting
|
||||
|
||||
## Context
|
||||
|
||||
We wish to create a backup tool that will save only the last modified files of a storage unit.
|
||||
|
||||
In our example, the storage unit is **not a bucket**.
|
||||
|
||||
The storage unit is the `DD-MM-YYYY-test` branch of the current `descartes-underwriting/devops-technical-test-data` git repository.
|
||||
|
||||
## Property
|
||||
|
||||
The `descartes-underwriting/devops-technical-test-data` repository is not frozen and will have new commits.
|
||||
|
||||
Commits will be added to the `DD-MM-YYYY-test` branch multiple times every day.
|
||||
|
||||
The `DD-MM-YYYY-test` branch name will be adapted using standard datetime convention eg: `01-01-2022-test` for the 1st of January 2022.
|
||||
|
||||
## Task
|
||||
|
||||
Develop a backup tool to save the modified files at each commit.
|
||||
|
||||
### Submission
|
||||
|
||||
Script and data should be saved on a private `candidate/descartes-backup-project` repository on your github account.
|
||||
|
||||
Access should be granted to all members of the `descartes-underwriting` group:
|
||||
|
||||
<https://github.com/orgs/descartes-underwriting/people>
|
||||
|
||||
Especially:
|
||||
|
||||
* <https://github.com/alexandreCameron>
|
||||
* <https://github.com/Mareak>
|
||||
* <https://github.com/jrdescartes>
|
||||
|
||||
### Script
|
||||
|
||||
Create a script to automate the backup process using open source software.
|
||||
|
||||
The script should track the changes fo the branch `DD-MM-YYYY-test` of the `descartes-underwriting/devops-technical-test-data` repository.
|
||||
|
||||
The execution of the script should be carried out with a github-action / gitlab-pipeline or any other tool automating git workflow on your git project.
|
||||
|
||||
It is highly recommended to use a scheduling tool to execute the back up process.
|
||||
|
||||
### Data
|
||||
|
||||
The backup should store files in separate folders.
|
||||
|
||||
The backup file structure should be based on the sha1 of the `descartes-underwriting/devops-technical-test-data`.
|
||||
|
||||
Starting from the initial commit [282180fe7e5d9cbf297f2f0ef813cffe60ce2328](https://github.com/descartes-underwriting/devops-technical-test-data/commit/282180fe7e5d9cbf297f2f0ef813cffe60ce2328), all the history should be backup.
|
||||
|
||||
## File structure example
|
||||
|
||||
For the following commits on the `descartes-underwriting/devops-technical-test-data`:
|
||||
|
||||
| SHA | OPERATION |
|
||||
|-----|-----------|
|
||||
| Commit_N | create readme.md |
|
||||
| Commit_N+1 | create doc.txt |
|
||||
| Commit_N+2 | create data/test/test.txt |
|
||||
| Commit_N+3 | append text to ./doc.txt |
|
||||
| Commit_N+4 | create test/project/project1.txt |
|
||||
|
||||
The `candidate/descartes-backup-project` repository should have
|
||||
|
||||
```bash
|
||||
$ tree .
|
||||
.
|
||||
├── .gitworkflow
|
||||
│ └── workflows
|
||||
│ └── my-lovely-workflow.yml
|
||||
├── data
|
||||
│ ├── N
|
||||
│ │ └── readme.md
|
||||
│ ├── N+1
|
||||
│ │ └── doc.txt
|
||||
│ ├── N+2
|
||||
│ │ └── data
|
||||
│ │ └── test
|
||||
│ │ └── test.txt
|
||||
│ ├── N+3
|
||||
│ │ └── doc.txt
|
||||
│ └── N+4
|
||||
│ └── test
|
||||
│ └── project
|
||||
│ └── project1.txt
|
||||
└── script
|
||||
└── my-beautiful-script.best-language
|
||||
```
|
Loading…
Reference in New Issue
Block a user