We've been using `statusteam` Docker Hub org for a while now which was
never intended for public use, and we should be using `wakuorg` instead.
I've also updated references to `statusteam` in documentation and scripts.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
We are checking if `JOB_NAME` contains a token `race` to set the default
value for `RACE` parameter which decides which tests run.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
Changes:
* Rename `BRANCH` to `GIT_REF` to indicate tags can be used.
* Default to `stable` for `IMAGE_TAG` on release builds.
* Use `GIT_REF` for specific Docker image tag instead of commit.
* Adjust some comments and descriptions.
Resolves:
https://github.com/waku-org/go-waku/issues/516
Signed-off-by: Jakub Sokołowski <jakub@status.im>
Using `$HOME/go` is bad and you should feel bad.
Also, adding `/usr/loca/go/bin` is a terrible idea.
And `GOCACHE` is poisoning stuff for linter.
Signed-off-by: Jakub Sokołowski <jakub@status.im>
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>
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>
Jakub Sokołowski
harsh-98
Richard Ramos
Prem Chaitanya Prathi
Anthony Laibe