...
| Anchor | ||||
|---|---|---|---|---|
|
Setup a Gitlab account
a. If you don’t have a Gitlab account, please register at https://gitlab.com/
...
| Anchor | ||||
|---|---|---|---|---|
|
Upload tables to database via pipeline
a. Tables - You can use "csv" or "tsv" table formats, but not a mixture of them. (If you are using the "tsv" tables please see step 2 below)
...
3. To stop running the pipeline automatically, you need to add info about when you add or update on of these files. Otherwise, it will automatically run the pipeline. You should only run the pipeline when all files have been added; so in order to stop it running when you are not ready add [skip ci] to the comment.
b. tsv tables instead of csv tables
i. Need to change the delimiter in the db_temp.sql file
...
| Anchor | ||||
|---|---|---|---|---|
|
Correct the errors on csv files
a. If the csv files have formatting problem, it will not pass stage 1 (run_tests). Make sure all the table formats are compliance with the correct format. See Tables structure
...
| Anchor | ||||
|---|---|---|---|---|
|
Download the xml file and export it to archivist
a. If it passes, the XML file is available as an "artifact" (a zip files containing the generated XML) and this is available for 10 days. The xml can be viewed temporarily from temp archivist and will need to be loaded into archivist via import, if you have permissions to do so then add to archivist, if not, please ask Hayley Mills to import.
Updating your gitlab pipeline
Once setup you may need to re-fork or pull the latest version of the Gitlab pipeline to ensure you have the latest version.
...