The 'Plan summary' tab will report whether the build succeeded or not. You can specify a custom results location if your project directory doesn't use the conventional structure. Each of the builder tasks above has a section to tell Bamboo to expect test results and where to look for them. Your tests will be run when the builder task compiles the code. Now you can create a PHPUnit testing task: Select Add to add the PHPUnit capability.Select Add capability and complete the configuration using the following: You will need to add a server executable capability to run PHPUnit: PHPUnit provides also produces test results in the JUnit XML format required by Bamboo. This is a port of the popular Java JUnit testing framework to PHP. Unit testing for PHP is completed using the PHPUnit testing framework. The source code checkout taskĪ newly created plan has a default Source Code Checkout task that gets the source code from the source repository specified earlier. Repository atlassian_tutorial/hellworld (git)Įach plan needs to have at least one task specified. Choose a source repositoryīamboo needs to know where the source code repository is located, and needs access to the repo so that it can check out the code when it runs a build. See Linking to source code repositories for more details. Configure the plan detailsīamboo needs to know the Plan name, Plan key and a brief description of what the plan is for. See Configuring plans for more details.īuild Atlassian tutorials 3. We don't have a project yet, so select Project > New Project, and enter details for both the project and plan. Select Create > Create plan from the menu bar.
Log into your Bamboo instance as a user with permissions to create plans.In this example, you create both a new project and a new plan in that project. You can add a plan to an existing project or create a new project. You use a plan to identify the source code repository, specify the tasks to run in your build, and when to trigger a build. Create a new projectĪ Bamboo plan defines the details of your continuous integration workflow. If you prefer, you may use Composer or PEAR to download and install PHPUnit along with its dependencies, however these approaches are beyond the scope of this introduction. $ phpunit -version // double check it's installed completely $ mv phpunit.phar /usr/local/bin/phpunit // copy PHPUnit into your path $ chmod +x phpunit.phar // make PHPUnit executable
0 kommentar(er)
