We upgraded from v220.127.116.116 to v18.104.22.1684 and hadn’t made any project-level config changes, and we hadn’t made any modifications to the roles that v22.214.171.1244 assigned to our machines.
After the upgrade (and no config changes), we deployed a project and noticed instances where variables with a machine-level constraint were not assigned as we would have expected, and they were not assigned as they had been in deployments prior to our upgrade.
In one instance (project variables and the deployment log attached), we’d intended our variable “EnvironmentName” to be applied specifically to a subset of machines, and not to be defined for all other machines. The deployment log indicates that the variable has been applied to a machine we had not specified.
Is it possible the machine-level constraint is being ignored?
When we added a role-level constraint, to accompany the machine-level constraint, we were pleased that in deployments of a subsequent Release, the variable was not applied to machines we had not specified.
We thought we would need to apply this change (adding a role-level constraint) to the variables that had had only machine-level constraints, in order to ensure the variables would be assigned consistent with the pre-upgrade deployments. So that’s what we did.
Does our approach sound reasonable? Are there other cases we might have overlooked?