Skip to content

Use temporary folders for ITs with native broker #37

@678098

Description

@678098

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

For native broker currently we have some ENV vars being set in the code, but these variables do not do anything right now, because we use static config. Here:

Map<String, String> env = pb.environment();
env.put("BMQ_PREFIX", envPath);
env.put("BMQ_STORAGE", storagePath.toString());
logger.info("BlazingMQ Broker storage directory: {}", storagePath);
outputFile = new File(tmpFolder.resolve("output").toString());
// Common environment vars
env.put("BMQ_PORT", String.valueOf(sessionOptions.brokerUri().getPort()));
env.put("BMQ_HOSTTAGS_FILE", "/bb/bin/bbcpu.lst");
env.put("PYTHONPATH", envPath + "/python");

This means that currently we can use params listed in static config only, so storage path, logs path, broker port are the same for each launched broker. The last means that native IT brokers could only be launched on a default 30114 port, and no parallel ITs execution possible.

We create a TMP folder which should contain storage, logs etc, but we are not able to use it with a static config:

Expected Behavior

Native brokers in ITs should be able to use TMP folders and non-default parameters.

Steps To Reproduce

Launch ITs with -Dit.brokerDir=/path/to/native/broker

BlazingMQ Java SDK Version

0.0.10

Anything else?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-TestingArea: TestingbugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions