After the last article where I’ve shown how to consume WSDL Webservices with NTLM authentication, I present a particularity about that method.
The difficulty occurs when there’s more than one WSDL operation with the same name (that is, there are overloaded methods). When you don’t need NTLM authentication, the solution is rather simple, but when you do need NTLM authentication you need to be a little creative.
To be able to consume SOAP web services with PHP you need to install the PHP-SOAP extension. However, the SoapClient class provided by that extension does not allow NTLM authentication.
Before we go into the solution I would like to thank Thomas Rabaix for his blog post on March ‘08 about the subject. Indeed, his post is the real source for all the solutions online. If you hadn’t read the article I suggest you to do so.
For the past weeks I’ve wrote a series of articles on how to create a continuous integration server which began with the article Tools for a Continuous Integration (CI) server for PHP projects.
You can automate much more than what I’ve shown in this series of articles, specially front-end processes or automated tests and I hope you got to a point where you can investigate and start to tweak the continuous integration process to match your needs.
In the previous article we’ve installed SonarQube and SonarQube Runner. Now that we have the tools, let’s analyse the Laravel 5 project that we’ve created in the second article of “How to set up a Continuous Integration Server for PHP projects”.
This series or articles begun with the article Tools for a Continuous Integration (CI) server for PHP projects and teaches you how to create a continuous integration server from the scratch.
One of the most neglected processes in Software Development is the ability to know how exactly is your project’s health. To do so you need a complex and periodic analysis to ensure your project’s maintenance is sustainable. There are several tools that help you to perform such analysis and among them is SonarQube.
In this article, which is part of the series “How to create a continuous integration server” and began with the article Tools for a Continuous Integration (CI) server, I’ll show you how to install and configure SonarQube and SonarQube Runner.
Following the previous article where you’ve installed TeamCity, you can now say that you have a Continuous Integration Server. But it doesn’t do much without an Agent or a Build Configuration.
What is this? A Build Configuration is a list of steps that will be executed. Think about merging all less files and compact all the files into a single minified .css file. Another step from the same configuration could be uglify Javascript files (or, following the same logic of the first step, parse CoffeeScript into Javascript).
TeamCity is a Continuous Integration aplication, developed by JetBrains that supports multiple programming languages (such as Java, .Net and PHP). Although it’s a commercial tool, there’s a freemium version that allows you to use it freely with up to 20 configuration builds and 3 build agents. If you have an open source project, you can apply to a free licence. Check the licencing page to know more about this.
Redmine is a project management software, developed using Ruby On Rails and multiplatform. It’s a flexible application with a growing community.
In this article, which is part of the series “How to setup a Continuous Integration Server for PHP projects”, we’ll show you how to install Redmine 2.6.1 on a Linux Mint 17.1 machine and how to integrate it with Git so you can see Git history within Redmine and how to close issues with commit messages.
In the second article of the series “How to set up a continuous integration server” we’ll install Git and SSH on a server running Linux Mint.
We’ll show you how to configure this services on a Windows machine so, in the end, you push your code from a Windows development machine to the Linux server.
Continuous integration is a software development practice where programmers integrate their source code changes frequently and whose goal is to detect errors as early as possible.
This is the first article for a series where we’ll show how to create a continuous integration server for PHP projects. In this first article we analyse the tools that we’re going to use.
