-
Notifications
You must be signed in to change notification settings - Fork 47
set up Jenkins for apps/wallet
#662
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
Conversation
🦋 Changeset detectedLatest commit: 71cfa2c The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
@felicio is attempting to deploy a commit to the Status Team on Vercel. A member of the Team first needs to authorize it. |
Jenkins BuildsClick to see older builds (27)
|
|
@markoburcul could you please enable builds for |
|
@markoburcul you should be able to push to this branch should you need to add any changes, otherwise please let me know. |
|
@felicio I am not able to find the branch after cloning the repo: |
|
@markoburcul it's a fork – https://github.com/felicio/status-web/tree/wallet-build. Please, lemme know if you cannot work with those for some reason. |
Why are you using forks? Why wouldn't we enable build for apps/wallet in the original repo? |
|
@markoburcul not everybody contributing will have a direct access nor you might want or need to necessarily share your branches upstream. This is the upstream/original repo, and we'd like to enable them. Even this PR, already built
|
|
We will not run PR jobs from external contributor forks in our CI. It is a major attack vector. Also, you are a core contributor, you can push branches directly to this repo, why are you working with a fork? |
|
@jakubgs so this #662 (comment) ran because I'm part of the org and will continue to be built? |
|
Yes, correct, the policy is that PRs from external contributors - meaning not in the org or added to the repo - need approval by contributors in order to allow PR CI jobs to run. |
|
This can be refactored to use just one Jenkinsfile for both components. I can do that, but since this is using a branch from a fork I can't contribute to it currently. Why not just push a branch directly to this repo? |
|
Talk summary
|
d5ce1fe to
7b5b6aa
Compare
Signed-off-by: Jakub Sokołowski <[email protected]>
|
There you go, I pushed a commit to this PR that refactors the Jenkinsfile to be usable for any app in the
For now I made the choices only One problem that exists tho is that:
Could we not consolidate those paths to be the same? |
|
https://ci.status.im/job/status-web/job/prs/job/linux/job/wallet/job/PR-662/3/console |
|
Thanks @jakubgs.
For now pushed 955cbbe. Could you please approve the PR if agreed?
Builds in |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Jenkinsfile looks good to me, though not sure what the other changes are about.

closes https://github.com/status-im/status-website/issues/1563