View Issue Details

IDProjectCategoryView StatusLast Update
0006728Talerdeployment and operationspublic2021-08-24 14:23
ReporterFlorian Dold Assigned ToFlorian Dold Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit (master) 
Target Version0.8Fixed in Version0.8 
Summary0006728: set up wallet CI pipeline for WebExtension build
DescriptionThe Mozilla reviewers consistently had some issues building the wallet.

To make it easier to show how to reproduce the build, we should set up a (gitlab.com) CI pipeline where a Docker container builds the WebExtension .zip
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

sebasjm

2021-01-30 23:02

developer   ~0017472

I managed to configure the gitlab repository to publish the webextension, you can check and download from here
https://gitlab.com/sebasjm/wallet-core/-/packages/1078595

I when further and made some changes into the project to publish the npm packages, check here
https://gitlab.com/sebasjm/wallet-core/-/packages
In order to do that, all the packages.json needs to have a scope. It should be @gnu-taler but I used @sebasjm for this repo. 
More information here:
https://docs.gitlab.com/ee/user/packages/npm_registry/#authenticate-to-the-package-registry

sebasjm

2021-02-01 21:01

developer   ~0017486

I've pushed all the changes, into wallet-core main branch.
I have been testing with dev/sebasjm/ci-npm-publish so I expect everything to work smoothly.

Right now packages are in gitlab free repository, to access them a setup is needed.
```
npm config set @gnu-taler:registry https://gitlab.com/api/v4/packages/npm/
```
and then
```
npx @gnu-taler/taler-wallet-cli
```
should work.


I we want to publish the npm packages into npm registry we should create an account, create an api token and make the proper changes into the CI.

Issue History

Date ModifiedUsernameFieldChange
2021-01-30 10:30Florian DoldNew Issue
2021-01-30 22:55Christian GrothoffSeverityminor => feature
2021-01-30 23:02sebasjmNote Added: 0017472
2021-02-01 21:01sebasjmNote Added: 0017486
2021-02-03 22:39Christian GrothoffAssigned To => sebasjm
2021-02-03 22:39Christian GrothoffStatusnew => assigned
2021-02-03 22:39Christian GrothoffCategoryother => deployment and operations
2021-02-03 22:39Christian GrothoffProduct Version => git (master)
2021-02-03 22:39Christian GrothoffTarget Version => 0.9
2021-03-03 19:12sebasjmAssigned Tosebasjm => Florian Dold
2021-03-03 19:12sebasjmStatusassigned => informing
2021-03-03 19:12sebasjmResolutionopen => fixed
2021-07-30 11:56Christian GrothoffFixed in Version => 0.8
2021-07-30 11:59Christian GrothoffTarget Version0.9 => 0.8.1
2021-07-30 12:02Christian GrothoffTarget Version0.8.1 => 0.8
2021-08-24 14:23Christian GrothoffStatusinforming => closed