Quick start

No matter whether IGA is run locally on your computer or as a GitHub Action, in both cases it must be provided with a personal access token (PAT) for your InvenioRDM server. Getting one is the next step.

flowchart TD; node1(Step 1: Install IGA)-->node2(Step 2: Get token from InvenioRDM); node2-->node3{Local or \nGitHub Action?}; node3-->|Local| node4(Step 3: Configure local IGA); node3-->|GitHub| node5(Step 3: Configure GitHub Action); style node1 fill:white, stroke:blue; style node2 fill:white, stroke:blue; style node3 fill:white, stroke:orange; style node4 fill:white, stroke:blue; style node5 fill:white, stroke:blue; click node1 "installation.html" _self; click node2 "#getting-an-inveniordm-token" _self; click node4 "#configuring-a-local-iga" _self; click node5 "#configuring-a-github-action" _self;

Getting an InvenioRDM token

1. Log in to your InvenioRDM account

2. Go to the Applications page in your account profile

3. Click the New token button next to “Personal access tokens”

   

4. On the page that is shown after you click that button, name your token (the name does not matter) and click the Create button

   

5. After InvenioRDM creates and shows you the token, copy it to a safe location because InvenioRDM will not show it again

Configuring IGA for local use

To send a GitHub release to your InvenioRDM server, IGA needs this information:

1. (Required) The identity of the GitHub release to be archived

2. (Required) The address of the destination InvenioRDM server

3. (Required) A personal access token for InvenioRDM (from above)

4. (Optional) A personal access token for GitHub

The identity of the GitHub release is always given as an argument to IGA on the command line; the remaining values can be provided either via command-line options or environment variables. One approach is to set environment variables in shell scripts or your interactive shell. Here is an example using Bash shell syntax, with fake token values:

export INVENIO_SERVER=https://data.caltech.edu
export INVENIO_TOKEN=qKLoOH0KYf4D98PGYQGnC09hiuqw3Y1SZllYnonRVzGJbWz2
export GITHUB_TOKEN=ghp_wQXp6sy3AsKyyEo4l9esHNxOdo6T34Zsthz

Once these are set, use of IGA can be as simple as providing a URL for a release in GitHub. For example, the following command creates a draft record (the -d option is short for --draft) for a certain project in GitHub and tells IGA to open (the -o option is short for --open) the newly-created InvenioRDM entry in a web browser:

iga -d -o https://github.com/mhucka/taupe/releases/tag/v1.2.0

More options are described in the section on detailed usage information.

Configuring a GitHub Action

After doing the GitHub Action installation steps and obtaining an InvenioRDM token, one more step is needed: the token must be stored as a “secret” in your GitHub repository.

1. Go to the Settings page of your GitHub repository

   

2. In the left-hand sidebar, find Secrets and variables in the Security section, click on it to reveal Actions underneath, then click on Actions

   

3. In the next page, click the green New repository secret button

   

   . Alternatively, if you are part of a GitHub organization you can add a secret for all organizational repositories by clicking the gray “Manage organization secrets” button.

4. Name the variable INVENIO_TOKEN and paste in your InvenioRDM token

5. Finish by clicking the green Add secret button

Testing the workflow

After setting up the workflow and storing the InvenioRDM token in your repository on GitHub, it’s a good idea to run the workflow manually to test that it works as expected.

1. Go to the Actions tab in your repository and click on the name of the workflow in the sidebar on the left

   

2. Click the Run workflow button in the right-hand side of the blue strip

3. In the pull-down, click the checkbox for “Mark the record as a draft”

   

4. Click the green Run workflow button near the bottom

5. Refresh the web page and a new line will be shown named after your workflow file

   

6. Click that line to see the IGA workflow progress and results

Running the workflow when releasing software

Once the personal access token from InvenioRDM is stored as a GitHub secret, the workflow should run automatically every time a new release is made on GitHub – no further action should be needed. You can check the results (and look for errors if something went wrong) by going to the Actions tab in your GitHub repository.

After the first release

Once you’ve made the first release of your software on InvenioRDM, you might want to add the record you created as a ‘parent’. This will enable automatic versioning, so all your software versions will be listed in one place and users will be notified about newer versions of the software. Grab the record id at the end of your InvenioRDM record (e.g. 6qhkm-7n074) and add it to your iga.yml file in the parent_record field.