如何在 Rational Team Concert 中将 php 源代码发布到本地 Web 服务器？
我将在不久的将来在工作中使用 RTC。我的问题是：团队成员将要处理的文件放在哪里？我知道每个程序员都会处理项目文件，并将更改推送到主存储库。我们有一个本地网络服务器，我们可以在其中测试我们的工作（php）。那么，我们是否必须配置 RTC 才能将文件发布到 Web 服务器？或者RTC服务器必须安装在网络服务器中才能保存文件？
I'll be using RTC in the near future here at work. My question is: where does it put the files the team members will be working on? I understand that each programmer will work on the projects files and they will push the changes to the main repository. We have a local web server where we test our work (php). So, do we have to configure RTC to publish the files to the web server? or the RTC server must be installed in the webserver so it can save the files?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们使用 Rational Team Concert 几乎完全按照您的描述，并且它运行得非常出色。我的网络开发人员小团队在网站源代码上进行协作，并根据其准备情况将其交付到两个不同的流：生产流和登台流。然后我们定义了两个构建，用于检查源代码、移动一些内容并通过 SCP 将文件推送到 Web 服务器。因此，只需单击几下，我们就可以启动临时构建，并在大约两分钟内完成，每个人都可以看到临时服务器上的更改。当代码准备好进入黄金时段时，变更集将被交付到生产流，并启动生产构建，该构建被配置为将文件复制到生产 Web 服务器。
但即使在运行临时或生产构建之前，我们任何人都可以使用 Eclipse PDE 和 Web Tools 附加组件在 RTC 中简单地配置本地 Web 服务器，并在开发时查看在本地主机中运行的站点。
我们所有的工作都是在 Rational Team Concert 中完成的，从规划、错误跟踪、源代码控制到构建。它非常适合网站管理。
We use Rational Team Concert almost exactly as you describe, and it works brilliantly. My small team of web developers collaborates on website source code and delivers it to two different streams depending on its readiness: production-stream and staging-stream. Then we have defined two builds that check out the source code, move some things around, and push the files to the web servers via SCP. So, with a few clicks we kick off a staging build, watch it finish in about two minutes and everyone can see the changes on the staging server. When the code is ready for prime-time, the change sets are delivered to production-stream and the production build is kicked off, which is configured to copy the files to the production web server.
But even before a staging or production build is run, any of us can simply configure a local web server in RTC using the Eclipse PDE and Web Tools add-ons and see the site running in localhost as we develop.
All our work is done within Rational Team Concert, from planning, to bug tracking, to source control, to builds. It's very well-suited for website management.
您的理解是正确的 - 您在本地处理文件，当您签入时它们会上传到服务器。请记住，RTC 术语中的签入实际上意味着将文件备份到服务器，它是一个与其他人共享文件的 Deliver 命令（值得快速浏览一下 jazz.net 上解释 SCM 如何工作的文章） 。
发布到 PHP 服务器的一种方法是将该部分作为构建的一部分，或者单独构建（RTC 也可以处理 - 与您最喜欢的构建工具结合使用）。构建会将文件复制到 php 服务器。将其作为构建的优点是您将确切地知道正在复制的文件的版本，并且您将能够在将来的任何时候重现此副本。
您不需要在php服务器上安装RTC服务器。
如果您对 RTC 有疑问，还可以尝试在 http://jazz.net/ 的论坛上发帖。
希望有帮助。
Your understanding is correct - you work on files locally, and they get uploaded on to the server when you checkin. Bear in mind that checkin in RTC terms really means back-up your files to the server, it is a Deliver command that shares the files with others (it is worth a quick look at the articles on jazz.net that explains how SCM works).
One way to pubish to your php server is to make that part of a build, or a build in its own right (which RTC also handles - in conjunction with your favourite build tool). The build would copy the files to the php server. The advantage of doing this as a build is you will know exactly what versions of your files are being copied, and you will be able to reproduce this copy at any point in the future.
You do not need to install the RTC server on the php server.
You can also try posting on the forums on http://jazz.net/ if you have questions on RTC.
Hope that helps.
另一种选择是使用命令行界面接受工作区中的所有更改并使用 cron 作业运行它。
要处理丢弃的更改集，您可能需要使用类似的方法：
在您最初将工作区加载到 Web 服务器上之后。
Another alternative would be to use the command line interface to accept all changes into a workspace and run that with a cron job.
To handle discarded change sets, you'd probably want to use something like:
after you had initially loaded the workspace on your web server.