After you've deployed an agent, you are ready to define a CI build that compiles your Java app with Maven whenever your team checks in code.
Upload your code
If you don't have any code, you can download our Hello world Java web app.
Create the definition
Create the build definition.
Specify the code you want to build and select the continuous integration (CI) trigger.
If your project builds with Maven, add the Maven build step. Otherwise add the build step your team uses.
Provide the path to your Maven POM file.
Select the continuous integration (CI) trigger and specify the code you want to build.
Save the definition.
Queue your new definition to make sure it works.
Your team now has a CI build to validate every change checked into your codebase!
What code is in the sample app?
|-- .gitignore `-- helloworld |-- .classpath |-- .project |-- pom.xml `-- src `-- main `-- webapp |-- WEB-INF | `-- web.xml `-- index.jsp
The pom.xml file enables you to build with Maven. The .gitignore file keeps build artifacts on your dev machine from getting into your Git repo.
Can I deploy my app to Azure?
What other kinds of apps can I build?
What other kinds of build steps are available?
How do we protect our codebase from build breaks?
Git: Improve code quality with branch policies with an option to require that code builds before it can be merged to a branch. This option is not available for GitHub repos.
TFVC: Use gated check-in.
How do I modify other parts of my build definition?
Specify your build steps to run tests, scripts, and a wide range of other processes.
Specify build options such as specifying how completed builds are named, building multiple configurations, creating work items on failure.
Specify the repository to pick the source of the build and modify options such as how the agent workspace is cleaned.
Set build triggers to modify how your CI builds run and to specify scheduled builds.
Specify build retention policies to automatically delete old builds.
I selected parallel multi-configuration, but only one build is running at a time.
If you're using Team Services, you might need more concurrent pipelines. See Concurrent build and release pipelines in Visual Studio Team Services.
How do I see what has changed in my build definition?
Do I need an agent?
You need at least one agent to run your build or release. Get an agent.
I can't select a default agent queue and I can't queue my build or release. How do I fix this?