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.

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

Feature - Provide a way to apply global properties settings to local instances of jmeter easily #35

Open
Ardesco opened this issue Feb 7, 2012 · 1 comment

Comments

@Ardesco
Copy link
Contributor

Ardesco commented Feb 7, 2012

Currently you need to specify global properties for remote JMeter instances and local properties for all local instances. It would be useful to implement a way to enable the properties to be set for both local and global instances without having to duplicate them all in the POM.

Possible implementations.

  • Add a a new map that allows you to specify global(i.e. remote) and local properties.
  • Add a boolean flag to enable global(remote) properties to be set locally as well.
  • Add a boolean flag to enable local properties to be set globaly as well.
  • One or more of the above

We need to define precedence as well, will global(remote) properties flagged to be applied locally overwrite local properties that have been defined, or vice versa.

@afranken
Copy link
Contributor

I'd opt for option 3 "Add a boolean flag to enable local properties to be set globaly as well.", this could even be the default.

If a property is set in both maps, the global one should have precedence, though.

i.e.

local settings
a=1
b=1

global settings
b=2

Should result in
local.properties
a=1
b=1

global.properties
a=1
b=2

@Ardesco Ardesco added this to the 2.0.0 milestone Mar 3, 2016
@Ardesco Ardesco modified the milestones: 2.0.0, 2.1.0 Jul 5, 2016
@Ardesco Ardesco added the ready label Feb 15, 2017
@pmouawad pmouawad modified the milestones: 2.3.0, 2.2.0 May 1, 2017
@pmouawad pmouawad modified the milestones: 2.3.0, 2.4.0 Oct 10, 2017
@pmouawad pmouawad added this to the 2.8.0 milestone Feb 11, 2018
@pmouawad pmouawad added this to Low priority in ISSUE TRACKING Aug 3, 2018
@pmouawad pmouawad modified the milestones: 2.8.0, 2.9.0 Oct 4, 2018
@pmouawad pmouawad modified the milestones: 2.8.1, 2.8.2 Nov 11, 2018
@pmouawad pmouawad modified the milestones: 2.8.2, 2.8.3 Dec 27, 2018
@pmouawad pmouawad modified the milestones: 2.8.3, 2.8.4 Jan 15, 2019
@pmouawad pmouawad modified the milestones: 2.8.4, 2.8.5 Jan 29, 2019
@pmouawad pmouawad modified the milestones: 2.8.6, 2.8.7 Feb 19, 2019
@pmouawad pmouawad modified the milestones: 2.9.0, 2.9.1 Apr 2, 2019
@pmouawad pmouawad modified the milestones: 3.0.0, 3.1.0 May 6, 2019
@Ardesco Ardesco removed this from the 3.1.0 milestone Apr 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
ISSUE TRACKING
  
Low priority
Development

No branches or pull requests

3 participants