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

Create Zenodo JSON file #1031

Merged
merged 27 commits into from
Feb 16, 2020
Merged

Create Zenodo JSON file #1031

merged 27 commits into from
Feb 16, 2020

Conversation

epassaro
Copy link
Member

@epassaro epassaro commented Feb 12, 2020

Last update: 13/2/2020

  • The pipeline consist of two jobs: one creates .zenodo.json file by running a notebook, and the other upload a new GitHub release. The Zenodo webhook automatically makes a release in their site using .zenodo.json from master as author list.

  • At the moment the second job is commented and not executed. Once un-commented, the second job will run only if the first job is succesful (see the parameter: dependsOn: zenodo_json).

  • The first job is incomplete. To complete we need:

    a) Fetch the gather_data.ipynb notebook from tardis_zenodo private repo. We are using a copy of the notebook stored in Gist and downloaded via wget as a temporary workaround.

    b) Push the generated .zenodo.json to the master branch.

  • During the first job the gather_data.ipynb notebook is executed twice:

    1. The first run is with --allow-errors flag and renders the notebook with errors/exceptions. The rendered notebook is saved as an Azure Artifact. This step usually never fails and is useful to debug errors very quickly.

    2. The second run is done without the flag. If there's any error/exception the entire pipeline will fail.

@wkerzendorf wkerzendorf merged commit 536482d into tardis-sn:master Feb 16, 2020
atharva-2001 pushed a commit to atharva-2001/tardis that referenced this pull request Oct 1, 2021
* Add new job to release-version.yml

* Add new job to release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Split step in smaller steps

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml

* Update release-version.yml
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.

2 participants