Hello Everybody,
We are checking our SSIS 2016 packages into TFS. We always make sure we can successfully build the project, too, which creates the *.ispac file for us locally. When it comes time to deployment, we manually pass that ISPAC over to the Operations group. The Operations person then logs onto the production SSIS server and double-clicks the ISPAC file in order to bring up the SSIS deployment wizard.
Sometimes this process doesn't work for us due to human error. Typically, that's a developer forgetting to check in the project they built into an ISPAC. That ISPAC gets deployed, but when the next developer makes changes to the same project, we reintroduce a bug that was fixed in the previous deployment.
Is there a way to force TFS to create the ISPAC for us? In this way, we could ensure that what gets checked in is what gets deployed (and likewise what doesn't get checked in doesn't get deployed).
Thanks,
Eric B.