Issue with Build Forge "Save Environment" check box behavior
![]()
Hi all,
We have a problem with the way the Save Environment check box behaves in BF 7.1.3. In Version 7.0, it only affected variables that did not have a default value. In 7.1, it affects all variables. For example, we have a variable SKIP_DEPLOYMENT that has two possible values: YES and NO, with NO being the default. This variable is stored in an environment that is shared by all projects. If a user is testing a project and sets this value to YES and also checks the Save Environment check box, all subsequent projects execute with SKIP_DEPLOYMENT set to YES, unless all users verify the correct values of all variables, which they are not in the habit of doing, because they are used to all variables having their default value unless they change them. Can this behavior be changed? A default value isn't useful at all if it can be overridden by a user checking the Save Environment check box. Note that disallowing access to this check box (using the Edit Environment Variables setting under Permissions) is not an option. Thanks, Jozef |
4 answers
![]()
Just for the record: this was confirmed to be a bug. The PMR is 21783,004,000
"ISSUE: If your change the value for any variable in the environment and click "Save Environment", upon executing the project again those same values will appear instead of the default value: 7.1.3.5: REPRODUCED the issue 7.1.3.5-iFix01: REPRODUCED the issue 8.0.0.1 - Perl: COULD NOT reproduce the issue (reverts to default value) 8.0.0.1 - Java: COULD NOT reproduce the issue (reverts to default value) I have submitted a defect against 7.1.3.5. You can also consider upgrading to 8.0x." "The defect for this issue against the 7.1.3.x release stream has been accepted. It is scheduled for the 7.1.3.6 release. Once that version is available, I will retest to confirm that the issue no longer occurs and notify you that it is available for download." |
![]()
Hello,
The only solution to this would be to create a sub group of an access group and add the users you don't want to be able to save environments, and remove the permission "edit environment variables" from the sub group. Although, this as you mentioned is not an option. Why is that not an option for you?
Aside from creating an environment variable with a default and a pulldown option and having users only change the pull down option before starting the job. Would allow users to change variables without effecting the default. This is a compromise and also not what you are looking for.
These are the only two options available.
|
![]()
Hello,
Just wanted to update this question with the answer. The save check box environment box purpose is to save the environment and change the defaults. It is the functionality of the check box in the 7.1 releases. There is a permission to remove so that this can not be done. But it is the expected behavior. If you would like additional changes or features. Please submit an RFE to the Build Forge RFE community. Thanks!
RFE link
Thanks!
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.