Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Setup test nodes to run Tribler 24/7 #5857

Closed
xoriole opened this issue Dec 15, 2020 · 3 comments
Closed

Setup test nodes to run Tribler 24/7 #5857

xoriole opened this issue Dec 15, 2020 · 3 comments
Assignees
@xoriole
Milestone
Next-next release

Comments

@xoriole
Copy link
Contributor

xoriole commented Dec 15, 2020

Setup test nodes to run Tribler 24/7

Why?

  • To find out if there are issues on normal Tribler network.
  • To find out if there are crashes on the release candidate or past stable versions and report them.

Where to setup?

  • Proxmox or Zulu

Tribler version:

  • last stable (eg. 7.6.1)
  • new candidate (eg. 7.7/ devel)

Requirements:

  • Sentry should be configured to report crashes
  • Alert developers if a crash is found
@xoriole xoriole added this to the 7.7.0 December milestone Dec 15, 2020
@drew2a
Copy link
Contributor

drew2a commented Dec 15, 2020

There is one more improvement to Sentry, that should be done:

  1. We should add a value to the config to allow sending crash reports without confirmations.

@xoriole xoriole self-assigned this Dec 22, 2020
This was referenced Dec 22, 2020
Merged
Merged
@xoriole
Copy link
Contributor Author

xoriole commented Jan 6, 2021

Update: Jenkins jobs running the old and newer versions are setup here:

  1. https://jenkins-ci.tribler.org/job/Deployment-Tests/job/long-runner-new-release/
  2. https://jenkins-ci.tribler.org/job/Deployment-Tests/job/long-runner-old-release/

The newer version installer is obtained via jenkins build and the last stable installer is obtained via Github release URL.

@xoriole xoriole mentioned this issue Jan 8, 2021
Merged
@xoriole
Copy link
Contributor Author

xoriole commented Jan 11, 2021

With the above jenkins jobs setup and running, I consider this issue as resolved.

@xoriole xoriole closed this as completed Jan 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@xoriole xoriole

Labels
None yet
Milestone
Next-next release
Development

No branches or pull requests
2 participants
@xoriole @drew2a