Cannot deploy software in production

Document ID : KB000009321
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:

After adding a new state and data view to the project, we could no longer promote packages because of dependency violations in the new state. 

Cause:

The basic reason for this is that, when you create a new working view in Harvest, it is only populated with any baseline versions that existed at the beginning of the project.  Versions from any of the packages in your project are not "visible" there until the package has been promoted to the new state.

Resolution:

There are 2 ways to resolve this problem.

  1. You can configure your new state to share a working view with an existing state.  This way, everything that is "visible" in the state with the shared working view will now also be "visible" in the new state.
  2. Promote every package in your project that is currently in the later states to the new state, then promote them back to their current state.  This will manually "populate" the new working view.
Additional Information:

It is recommended to only make such changes to your project's lifecycle when creating a new project.  After the project has been in use, you should not make changes to the states or their working views in order to avoid such side effects.