NET you get bytecode/DLLs or whatever as an end result but with PHP you do not.ĭoes that make my question any clearer? I realise that many people using TeamCity will be working with Java etc. I am using PHP which is not a compiled language, so my deployable files will be the same. You can download all build artifacts in a single. You can download artifacts from multiple places in TeamCity's UI: the Projects page, the Build Configuration page or the Artifacts tab of the Build Results page. "Artifacts are files and folders, such as installers, WAR files, log files, etc., produced by a build. My understanding is that the artifacts are the results of builds and are therefore deployable files. Hi, yes that is exactly what I'm suggesting. The artifacts folder always contains the entire code base! But I cannot see a way to make TeamCity behave like this. In my experience it is common practice to release incremental updates to projects, whereby only the altered/new files are released to an existing deployment, rather than updating the whole code base. So each TeamCity build would relate directly to the corresponding changelist and would only contain changed files. What I want is for only the changed files listed in each changelist to be bundled into the artifacts folder when I trigger TeamCity. So a given changelist may not be limited to just one module.
Some bugs/dev projects affect files across multiple modules.
When that bit of work is finished we can then checkin the changelist to SVN. Within PHPStorm we then manage each project by assigning it to its own subversion changelist identified by the same reference number. When a new bug or dev project is worked on, we give it a reference number which is used to identify those particular code changes. For instance there's a document manager module, an application process module and a user admin module. The PHP web application I'm supporting consist of a few hundred files, each broken down into modules/areas of functionality and organised like such on disk. Thank you for your comments and suggestions but building like that won't work for me.
0 kommentar(er)
