jakub
14a6f45be4
ci: use Nix dev shell from flake for CI builds
...
Provides a more predicable build environment for CI.
Depends on: https://github.com/status-im/status-jenkins-lib/pull/60
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2023-04-04 16:36:30 +02:00
Richard Ramos
3b3e3b6968
chore: use go 1.19 on CI
2023-04-03 10:43:01 -04:00
jakub
349e22bbe8
nix: add Nix flake to build node and library
...
This way we can build node or the library locally using:
```sh
nix build
nix build .#node
nix build .#library
```
Or just start a shell with Go `1.19.x` using:
```
nix develop
```
Which simply has the same environment as the build shell for the node.
One known snag is that there is currently no simple way to keep `vendorSha256`
updated to match the contents of `go.mod` and `go.sum`. For more details see:
https://discourse.nixos.org/t/how-should-i-build-a-go-package-from-local-source/19490/8
One way around this would be to have our own `vendor` folder, but that's
also a pretty ugly solution that requires manual updating.
Resolves:
https://github.com/waku-org/go-waku/issues/256
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2023-03-05 15:04:07 +01:00
Richard Ramos
62e1f59d4f
chore: setup linux ci for .deb
2022-12-06 15:48:48 -04:00
Richard Ramos
c8fc0404d1
chore: rename status-im/go-waku to waku-org/go-waku
2022-11-09 16:03:40 -04:00
jakub
d4018d3f55
ci: separate discord notification into a function
...
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2022-10-19 09:50:27 +02:00
jakub
8f783aac25
ci: add username and email to build notifications
...
Makes it easier to identify who to talk to about a deployment.
This depends on the following plugin being installed:
https://plugins.jenkins.io/build-user-vars-plugin/
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2022-10-19 09:50:26 +02:00
jakub
1e09904523
ci: add diff link for previously deployed commit
...
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2022-09-28 17:03:52 +02:00
jakub
5b42c98780
ci: add Discord notification for successful builds
...
This way teams can track what deployments happen when.
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2022-09-27 19:24:49 +02:00
Richard Ramos
cd79be4812
fix: jenkinscript ( #304 )
...
* chore: add jenkinsfile for tests
* chore: remove old jenkinsfile
* fix: lint
* fix: update cc-test-reporter
2022-09-12 10:13:38 -04:00
Richard Ramos
31ce4ed389
chore: release ( #255 )
...
* feat: ios build
* chore: build .deb and .rpm
* chore: use gcc-10
* fix: go tools and mobile versions
2022-06-19 17:50:37 -04:00
Anthony Laibe
a6ae4b7140
feat: upload code coverage to code climate
2021-11-09 13:13:49 +01:00
Richard Ramos
74fab9e50d
chore: add codeclimate code coverage support ( #126 )
2021-11-02 09:55:28 -04:00
Anthony Laibe
94e8b9cf86
test: build example in jenkins
...
Add command for generating coverage
2021-11-01 20:40:39 +01:00
jakub
5a7be16f32
ci: add Jenkinsfile for building Docker images
...
By pushing to `deploy-test` tag we can update the `go-waku.test` fleet.
Job: https://ci.status.im/job/go-waku/job/deploy-test/
Signed-off-by: Jakub Sokołowski <jakub@status.im >
2021-10-27 10:40:33 +02:00
jakub
Richard Ramos