If you prefer to mimic traditional SCM system behavior, you can set a preference to auto-complete change sets after each check-in.
如果您喜欢模仿传统的SCM系统,您可以在每一次检入之后,设置一个对自动完成变更集的引用。
Configuration Management is going to be critical 「fulcrum」 in leveraging a balanced and effective set of SCM processes and criteria for agile development methods.
配置管理在利用平衡且有效的SCM过程集方面成为关键的「支柱」并且也是敏捷开发方法的标準。
SCM deals with version control, workspace management, software integration, software builds, software deployment, and release processes.
SCM涉及到版本控制、工作空间管理、软件集成、软件构造、软件部署和发布过程。
For support or further information, please contact the SCM product vendor directly.
关于支持或进一步信息,请直接与SCM产品供应商联系。
An organizational SCM framework will need to be established, and its implementation should be in some way configurable so as to meet the needs of different projects.
需要建立一个组织的SCM框架,并且应该以某种可配置的方式来实现,以便满足不同项目的需求。
But it's worth noting that even larger projects could learn something by implementing a more lightweight and well-designed SCM process such as the one described here.
但值得注意的是甚至是较大的项目也可以通过实现更轻量级的且精心设计的SCM过程,例如这里所介绍的,来得到一些东西。
For traceability and failover recovery, after placing the portal artifacts into the deployment area, you should also save them into your SCM as a new version.
为了提供可跟蹤性和故障转移恢复,在将门户构件放入部署区域后,还应该将其作为新版本保存到SCM中。
In connecting all of these resources, SCM is always about servicing resource integration by managing flows on both the demand and supply side.
衔接了所有这些资源后,供应链管理总是通过管理需求与供应流程促进资源的整合。
Cost to migrate data to a new SCM tool.
将数据迁移到新的SCM工具中的成本。
When changes are made to files in the repository by a different developer, the SCM can identify conflicts from your changes and either automatically merge them or notify you of the conflict.
其他开发人员更改了存储库中的这些文件后,SCM会标识出这些变更与您所做的变更之间存在的沖突,然后自动将其合并或通知您存在沖突。
Again, the source code should normally be obtained from the SCM tool.
这一次,还是可以从SCM工具中正常得到源代码。
Tight integration with the SCM is crucial to manage change and to enable frequent builds.
与SCM的紧密集成对管理变更并进行频繁构建是至关重要的。
If you took a single agile project in isolation, its SCM requirements could almost certainly be met by a relatively simple toolset.
如果您孤立地看一个单个的敏捷项目,那么它的SCM需求几乎肯定地可以由相当简单的工具集来满足。
So teams can quickly initiate SCM processes and focus on development work instead of development infrastructure.
因此团队可以很快地开始SCM流程,关注于开发工作而不是开发架构。
When conflicts at the element level occur, the SCM system can no longer merge automatically.
当元素层次的沖突发生时,SCM系统就不会进行自动的合并。
This enterprise context often is the strongest factor in deciding which SCM toolset is chosen and which additional aspects of governance the chosen toolset will need to support.
该企业环境常常是决定选择哪个SCM工具集并且所选工具集需要支持哪些额外的管理方面的最大的因素。