Hi , we run 2014 enterprise and still use msdb for pkgs. We still use VS 2013 to develop those pkgs.
I sat in on a meeting yesterday where we saw that for whatever reason, when opening a package in our production tfs branch with sql config enabled in the pkg and plumbed starting from an environment variable (variable contains connection to master db where sql configs reside) on the build machine to a normal sql based ssis config architecture, VS actually updates the xml connector info based on what the sql config table contains. in our case it changes aliases. Presumably just on the local copy unless checked in.
If you've done this before you'll recognize that the way we deploy packages is by opening them in vs, copying their name, then going to file->save copy of packagename as->follow the prompts.
Is there a way to deploy using our mix of technologies without opening the package? Perhaps thru a script?
We will look at a manifest approach but it sounds like all other pkgs have to be unchecked in order for that approach to deploy one pkg.
In my mind allowing anything to change code that has already been tested is a no no. And keeping aliases in the deployed xml code seems strategic anyway.