We are using Hudson now for several months as Continous Integration System. This short article describes how we have configured a hudson project for a symfony 1.4 project. I am assuming that the reader is already used to Hudson and knows how a normal project has to be configured.

PHPUnit is the test framework of our choice (surprise, surprise) and we are using the sfPHPUnit2Plugin for all our projects. If you do not now this plugin you may first read another post where the usage and features are described in detail.

All requirements in short:

* Hudson has to be installed
* Hudson plugin xUnit Plugin has to be installed
* the symfony project needs the sfPHPUnit2Plugin
* PHPUnit has to be installed on your test server

Ok, here the configuration steps of the hudson project:

1. Configure your project

Configure standard settings for a hudson project like source-code management settings or email notifications. Please check the official docs if you do not know how to handle this.

2. Add a shell build step

Building a symfony project in a test environment is pretty easy. With the help of some shell commands the project is completely configured and ready for testing. Those shell commands may be entered in the build step section of the hudson project. Defining the correct commands is the main part during the configuration process.

Our configuration looks like this:

1. cd $WORKSPACE/trunk
2. sh _deployment/install_test.sh
3. php symfony cc
4. php symfony phpunit:test-all –configuration –options=”–log-
5. junit=build/testresult_$BUILD_NUMBER.xml” cd build
6. ln -s -f testresult_$BUILD_NUMBER.xml currentTestResult.xml

1. Jump in the project root of the project
2. Install the project on the test server with the help of a internal shell script. This step includes for example the generation of the databases.yml.
3. Clear the symfony cache (always a good choice)
4. Run all PHPUnit tests including unit and functional tests. The test result is written in a jUnit compatible logfile (needed for the xUnit Plugin).
5. Jump in the build directory, which is internally used by Hudson
6. Symlink the latest testresult

3. Configure Post-Build-Action

After the xUnit Plugin is installed correctly, an additional PHPUnit Pattern field should be displayed in the post build action section. In this field has to be entered:

1 trunk/build/currentTestResult.xml

The options “Fail the build if test results were not updated this run” and “Delete temporary JUnit file” should be both checked.

The xUnit Plugin takes the currentTestResult.xml file, which was previously created with the help of the sfPHPUnit2Plugin and analyzes it. When everything works fine, you should be able to review the created test reports.

Here some screenshots how this result could look like.

Build history:

Trend graph of the test results:

You can find the original post here : http://dev.esl.eu/blog/category/symfony/

With the amount of plugins published in the symfony site, many great plugins get lost in the maze. With this series of posts, we would like to bring some attention to plugins we use every day or that we think are essential for any symfony developer.

sfSyncContentPlugin

Deploying symfony applications is always a key part of developing and maintaining websites that run on symfony. It is always a recommended practice to do development on a local environment or dedicated development server. It is also recommended to have a QA/staging server that is as close as possible to your production server. Using this well proven method you can spot problems and bugs before everybody else sees or experiences them, you know, those bugs that “only” happen in production, don’t tell me that it never happened to you, I won’t believe you.

Anyway, making changes in a live site is not only not recommended, it should never be done!

When developing and testing symfony applications, a lot of times you need to have a copy of the live data. Or you may have a staging server where you make changes before pushing them to a live site in a production server. symfony already provides a way to deploy code changes to a remote server, but what about uploaded and data files? And database content?

Since we discovered and started using it, we can’t live without thesfSyncContentPlugin plugin by Tom Boutell and Alex Gilbert, also developers ofApostrophe CMS. This plugin helps with all the tasks and needs described above. Using it is quite simple. All you need to do is define your servers in config/properties.ini like this:

[qa]
  host=qa.example.com
  port=22
  user=user
  dir=/var/www/mysite

[prod]
  host=www.example.com
  port=22
  user=user
  dir=/var/www/mysite

[staging]
  host=staging.example.com
  port=22
  user=user
  dir=/var/www/mysite

Make sure to use SSH keys to authenticate to your remote servers, so you don’t get asked again and again for passwords. Then just run the following symfony tasks:

# Migrate files and DB from development to qa
./symfony project:sync-content frontend dev to qa@qa

# Migrate files and DB to production (always make a backup of production before doing this!)
./symfony project:sync-content frontend dev to prod@prod

# Migrate files and DB from QA into development
./symfony project:sync-content frontend dev from prod@prod

Files and DB content are copied accordingly, almost magically. It saves so much time, but please make sure you understand and check the order that you apply in the symfony task. With the power this plugin provides, is very easy, by mistake, to overwrite production data, so again, always make a backup!

hi, we all knows tht symfony 1.2 is released . today i want to write about some symfony 1.2 features.

Features
The admin generator will be rewritten from scratch to leverage the new form framework. The main goal is to provide a more customizable and a more flexible admin generator.

The Propel plugin and the Doctrine plugin will be bundled with symfony 1.2. So, as of symfony 1.2, the core team will officially support Doctrine as a first class citizen.

The development of secure applications has always been quite easy with symfony thanks to the use of the ORM, the output escaper, and the CSRF protection. Symfony 1.2 will go one step further by providing native input filtering. We will base this feature on the new filter extension bundled with PHP 5.2.

The framework must simplify the life of the developer on repetitive and boring activities. As most applications send emails, the Swift library, one of the most feature-full and flexible solution for sending emails in PHP, will be integrated into the core.

The JavaScript world evolves very quickly, with lot of great frameworks available (prototype, jQuery, Dojo, mootools, and YUI). all the JavaScript stuff available into a plugin.
The project:deploy task was just a proof of concept. So, it is time to start a discussion on the features we need for a proper deployment task.

The routing is now cached, so you can expect a significant performance boost when you got plenty of routes in your app. Also, the routing class is no more a singleton so you can now extend and reference it easily to fit your needs,

you can download symfony 1.1 from below given  links .

sf_sandbox_1_1.tgz

sf_sandbox_1_1.zip

you can upgrade your existing symfony project into symfony1.2.

Last week, the NetBeans team announced that the next version of their IDE (6.8) will have native support for symfony! That’s a great news for all of us. They have a dedicated page in their Wiki about symfony support in NetBeans, and the NetBeans 6.8 nightly builds already have some basic support for symfony, like the ability to run a task. To learn more, read Tomas Mysik’s blog post about what is already available. That’s exiting, and I think we need to help them building a great IDE for symfony. I highly encourage you to download a 6.8 build, test it with your own projects, and give them feedback.

content from.. http://www.symfony-project.org/blog/2009/07/08/symfony-support-in-netbeans-6-8

take a quick look at some useful symfony plugins . useful for your symfony project. if any query or change then post comment on it.

1. sfSimpleCMSPlugin
2. sfGuardPlugin
3. sfDoctrinePlugin
4. sfPropelActAsNestedSetBehaviorPlugin
5. sfMediaLibraryPlugin
6. sfSimpleBlogPlugin
7. sfSimpleForumPlugin
8. sfFeed2Plugin
9. sfgWidgetsPlugin
10. sfThumbnailPlugin
11. sfUJSPlugin
12. sfControlPanelPlugin
13. sfFormValidationPlugin
14. sfMogileFSPlugin
15. sfLightboxPlugin
16. sfCaptchaPlugin
17. sfNiftyPlugin
18. sfPrototypeWindowPlugin
19. sfPropelLoadbalancerPlugin
20. sfSavvyPlugin
21. sfYzClientSideValidationPlugin

from ,

sanjay

Symfony 2.0 is a major step forward for the symfony project. This new version introduces new concepts and new components, and make the framework even more decoupled and flexible than before. As an added bonus, the framework is also more lightweight and much faster. This session will give you a feeling of the power of Symfony 2.0 by introducing the main new components of the framework.

It’s realy good and nice one framework of PHP5.So let’s begin toward it.