Project

Profile

Help

Task #3872

closed

Add a new test environment in Travis with remote PostgreSQL and Redis instances

Added by tchellomello over 5 years ago. Updated about 5 years ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Dev Environment, Pulp 2
Sprint:
Quarter:

Description

This issue is inspired on https://pulp.plan.io/issues/3861 where we had some issues to connect a PulpWorker to a remote Redis server instance.

The idea of this issue is to open a discussion if we judge it will be important to have a test environment within Travis tests that will configure a remote PostgreSQL and Redis.

Please if you think this is a good idea, I can work on that and submit a PR.

mmello

Actions #1

Updated by daviddavis over 5 years ago

I probably don't think this is worthwhile. This code doesn't change very much—we mostly just configure psycopg and rq and let them do the heavy lifting to connect to pg and redis. Also, spinning up remote psql/redis instances (I'm imagining via containers?) would add time/resources to our test suite.

Actions #2

Updated by dkliban@redhat.com over 5 years ago

  • Tracker changed from Issue to Task
  • % Done set to 0

Here is an idea for how we could accomplish this:

Instead of deploying Pulp on the machine running the job, deploy each of Pulp's services in a separate container. Then run pulp-smash tests against the containers serving the REST API and Content app.

We should probably wait to do this until the installer is ready to be used for this.

Actions #3

Updated by bmbouter about 5 years ago

  • Status changed from NEW to CLOSED - WONTFIX
Actions #4

Updated by bmbouter about 5 years ago

  • Tags Pulp 2 added

Also available in: Atom PDF