July 5, 2016 at 11:30 am
Hey guys, I foresee the possibility of going to Project deployment on my team. The one big red flag that concerns me is that if one of the developers were still working on a package but another package needed to be deployed is there any way around not deploying the package that isn't ready?
July 5, 2016 at 11:49 am
dndaughtery (7/5/2016)
Hey guys, I foresee the possibility of going to Project deployment on my team. The one big red flag that concerns me is that if one of the developers were still working on a package but another package needed to be deployed is there any way around not deploying the package that isn't ready?
If you're using 2016, there is incremental deployment[/url], which may help. Some other possibilities:
1) Put it into a different project.
2) Deploy it, but avoid calling it.
3) Use an appropriate branching strategy with your VCS and deploy the branch which works.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply