InstallerExpert replied the topic: Re: Wise for Windows Installer – Continuous integration
A lot of users have used WFWI in automated build processes.
The automation interface (via the wfwi.document object) also allows you a great deal of flexibility in directly editing the tables of your WSI using vbscript (for example), and then saving and compiling the end result.

Give it a try and if you encounter any specific issues then post here with details, including your version of Wise tools.

The post Wise for Windows Installer – Continuous integration appeared first on scmGalaxy.

I am creating a checklists of questionnaire for the project mgmt to know the fact whether their project is CI or CC. I have got here few points which can be asked to Dev mgr to findout if they are CC or CI.

Please add your inputs as well if I am missing anything here….

How much code coverage do you have with your tests?
How long does it take to run your builds?
What is your average code complexity?
How much code duplication do you have?
Are you labeling your builds in your version control repository?
Where do you store your deployed software?
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post Is it Continuous Compilation Or Continuous Integration? appeared first on scmGalaxy.

• Supports pull request and branch build flow
• Run tests in parallel
• Great API and command line tool
• Open Source tool
• Multi-language support
• Easy to sync GitHub projects
• Pull request build flow
• Branch build flow
• Notifications by Slack, HipChat, Emails and more
• Deploy to S3 and Heroku

• Open source tool
• Supports Cross platform
• Manual triggers to customise and save good versions of Apps
• Value Stream Map allows you to track a change from commit to deploy at a glance.
• Test reporting
• compare builds feature for both files and commit messages – across any two arbitrary builds
• Allow to set multiple servers to keep your data available in the case of an emergency
• GitHub Integration

• Free plan even for a business account
• Rest API — you have an access to projects, build and artifacts
• You can trigger SSH mode to access container
• Integrated with Github & Bitbucket
• It’s easy, lightweight and fast to start
• Compatible with Ubuntu and Mac OS X
• Compatible with AWS, Azure, Heroku, Docker, dedicated server

• Fully integrated with GitLab
• Supports platforms like Unix, Windows, OSX, and any other platform that supports Go
• Tests run distributed on separate machines of which you can add as many as you want
• GitLab CI offers the same great experience as GitLab. Familiar, easy to use, and beautiful.
• Easy to use
• Each build can be split in multiple jobs that run in parallel on multiple machines
• There are multiple executors and you can reproduce tests locally

• Easy to start and Use
• Fully customizable hosted CI platform
• You can sign up with GitHub, GitLab & Bitbucket
• Flexible Pricing
• ParallelCI feature
• Open source tool but for support you need to pay
• Docker Supported (by upgrading)

The post Top 5 Cloud Based Continuous Integration Tools appeared first on scmGalaxy.

• Earlier finding & addressing of Bugs – By implementing continuous integration you can do frequent testings which helps to find bugs and error quickly before they ruin your whole efforts later.

• Improve software quality – Early finding issues in the codes, developers can act on them early before they grow into larger problems later,  which ultimately improves the quality of the software.

• Reduce the time it takes to validate – CI immensely reduce the waiting time to find out if your code’s going to work or not.

• Release new software updates – Doing frequently and numbers of time automated build and test of codes helps teams to deliver the new updates to the user more often and faster.

• Open Source
• Easy installation
• Easy configuration
• Rich plugin ecosystem
• Extensibility
• Distributed builds
• Platform: Cross-platform

• Free and Paid
• Gated Commits (prevents developers from breaking sources in a version control system by running the build remotely for local changes prior to commit)
• Build Grid. Allows running multiple builds and tests under different platforms and environments simultaneously
• Integrated code coverage, inspections and duplicates search
• Integration with IDEs: Eclipse, IntelliJ IDEA, Visual Studio
• Platforms supported: Java, .NET and Ruby
• Supports cloud integration

• Open source
• Supports pull request and branch build flow
• Parallel test runs
• Easily synchronize with GitHub
• Flexible plans for every size project
• Platforms: Hosted
• Supports Many Languages like Node js, php, Xcode, python and many more.

• Trial-ware
• Supports many languages like Python, C#, HTML, Java and various others
• Work in any environment like Visual Studio, Xcode, Eclipse, or any Git client
• Extensible tool can work effectively for all shapes and sizes

• Paid and Free trial
• Cross platform
• Allow to Import data from Jenkins
• Works with JIRA and Bitbucket
• Works with others tools like CodeDeply, Ducker, Maven, Git, SVN, Mercurial, Ant, AWS, Amazon S3 buckets
• Support many languages
• Can run multiple builds parerally
• customization of triggers and variables
• Very fast and easy to use

• Licensing plans
• Hosted service
• Server virtualization
• Integrated with middle-ware
• Clear visibility: what is deployed where and who changed what
• Configuration and security differences across environments
• Orchestration of changes across servers, tiers and components
• Automated provisioning, updating, and de-provisioning of cloud environments
• Automated, consistent deployments and rollbacks of applications

• Availability: Free with paid support
• Platform: Windows, Linux, Mac
• Pipeline Concept
• Parallel execution of the tasks
• Support Many languages
• Easily compare builds
• Clearly visualize workflow
• Promote trusted artifacts
• Plugins availability

• Platform: Hosted
• Availability: Free and paid with trial
• Easy to learn
• GitLab CI is fully integrated with GitLab
• Docker support
• Pipeline Concept
• Supports multi-languages – Java, PHP, Ruby, C etc..
• Parallel builds
• Autoscaling
• Build artifacts

• Availability: Free and paid with trial
• Platform: Cross platform
• Supported languages includes Java, Ruby/Rails, Python, Node.js, PHP, Haskell, and Skala
• Supports Docker
• Flexible pricing model

• Availability: Free and paid
• Platform: Hosted
• ParallelCI feature
• Supported languages Go Ruby on Rails, Node.js, PHP, Java, Go, Dart etc..
• Flexible Pricing
• Docker Supported (by upgrading)
• Easy to setup, fast and reliable

The post Top 10 Continuous Integration Tools | List of Best CI Tools | scmGalaxy appeared first on scmGalaxy.

How to enroll for this training?

The post DevOps Courses and Training | DevOps Training | Online | Classroom appeared first on scmGalaxy.

Introduction

• Introduction
• Why Shell Scripting?
• Linux Internal
• What to Expect From This Course?
• Prerequisites

Git fundamental

• Introduction of git
• Git setup
• Basic operations in git
• Github
• Summary

A First Look At Shell Scripts

• Introduction
• Creating A Shell Script
• Demo: A Note-Taking Script
• Calling The Script
• The Shebang
• Naming Your Script
• Demo: The type Command
• Summary

Variables

• Introduction
• Demo: Variables
• Using Variables in A Script
• Using Variables: Good Habits
• Reading Input
• Debugging your Script
• Summary

If, Then, Else

• Introduction
• Demo: The If Statement
• The If Statement
• Return codes
• The Conditional Expression
• Demo: The Conditional Expression
• The Conditional Expression 2
• Arithmetic Tests
• Demo: Arithmetic Tests
• The If Statement Revisited
• And, Or, Not
• Summary

Input and Output

• Introduction
• Output: echo and printf
• Input: read revisited
• Standard Streams and Redirection
• Demo: Redirection
• Summary

Control Flow

• Introduction
• While and Until
• The Classic For Statement
• The C-Style For Statement
• Break and Continue
• The Case Statement
• && and ||
• Summary

Variables 2

• Introduction
• Integer Variables
• Arithmetic Expressions
• Arithmetic Expressions 2
• Read-only Variables
• Exporting Variables
• Arrays
• Summary

Handling Script Parameters

• Introduction
• Special Variables
• Shift
• Getopts
• Getopts: Handling Errors
• Summary

Shell Functions

• Introduction
• Shell Functions
• Shell Functions 2
• Functions: Demo
• Some Miscellaneous Remarks
• Summary

Fun with Strings

• Introduction
• Removing Part Of A String
• Search and Replace
• Setting A Default Value
• Conditional Expression Patterns
• Regular Expressions in The Conditional Expression
• End of Options
• Summary

Many Ways to Run Your Script

• Introduction
• Running your Code
• Nohup and The Background
• Exec
• At and Cron
• Set and Shopt
• Summary

The post Shell Scripting (Bash) Training | Bash/Shell Scripting Course appeared first on scmGalaxy.

We have seen that build runners can be very handy. Even though most build runners can be replaced with an equivalent command using the command-line runner, build runners come with the convenience of easily setting up build steps, along with the necessary agent requirements and parameters.

Meta-Runners provide a straightforward way to create custom build runners. Meta-Runners can be thought of as a way to avoid duplications in build steps across build configurations.

In Chapter 3, Getting Your CI Up and Running, we created the deploy-to-test build configuration that deploys the Django application to Heroku. Using this build configuration as an example, we can see how we can extract a Meta-Runner Deploy To Heroku that can be used by any build configuration that wants to deploy to Heroku.

Recall that the deploy-to-test build configuration had a simple command-line runner that executed the following commands:

git remote add heroku git@heroku.com:django-ci-example.git  git push heroku master

To create a generic Meta-Runner out of this, we need to provide a way to push to any remote, rather than just git@heroku.com:django-ci-example.git.

As expected, we will do this by extracting the remote out into a build parameter. The command-line runner will have the following as the Custom Script to be run:

git remote add heroku %heroku.remote%  git push heroku master

We will provide the value for the %heroku.remote% parameter in the Build Parameters section of the build configuration.

Now we are ready to create a Meta-Runner from this build configuration. This can be done by clicking on the Extract Meta-Runner button in the right-hand side bar of the build configuration settings page. This brings up the Extract Meta-Runner dialog, which is shown in the following screenshot:

In the dialog, we give a name to the Meta-Runner. This is the name that will appear in the Runner Type field when configuring a build step for a build configuration.

Click on Extract to create the Meta-Runner. Once the Meta-Runner is created, we can see it listed in the Meta-Runners tab on the project administration page. We can also edit the Meta-Runner to fine-tune it as desired.

The following screenshot shows the edit page of the Deploy To Heroku Meta-Runner that we just created:

The Meta-Runner extracts all the parameters and steps defined in the build configuration. We can edit the Meta-Runner to have only the necessary parameters and steps.

Using Meta-Runners

We can now use the Meta-Runner that we created pretty much like a normal build runner. We will remove the existing build step in the deploy-to-test build configuration (from which we extracted the Meta-Runner) and add a Deploy To Heroku Meta-Runner-based build step.

Tip

We can also disable build steps if we don’t want to remove them while experimenting.

In the New Build Step page, for the Runner type field, the newly created Deploy To Heroku Meta-Runner is available, as shown in the following screenshot:

Once we choose the Deploy To Heroku Meta-Runner, we can see that the heroku.remote parameter is one of the fields to be configured. Since we created the Meta-Runner with the heroku.remote parameter with the value git@heroku.com:django-ci-example.git, that remote is available by default. The Deploy To Heroku runner configuration page is shown in the following screenshot:

Tip

It is possible to remove the value for parameters in the Meta-Runner XML so that no default values are present for the fields.

We can click on Save to add the build step. The new build step, based on the Deploy To Heroku Meta-Runner, will function in the same way as the previous build step based on the command-line runner.

Note

Of course, the value of Meta-Runners becomes more apparent when we create them out of multiple build steps. The same set of steps that may be repeated across multiple configurations can be extracted i

The post Going meta with Meta-Runners in TeamCity appeared first on scmGalaxy.

Upcoming Training Dates | Training Agenda | Training Calender | FAQ | Why scmGalaxy Online Training

Click Here

Mode – Online based
Email – info@scmgalaxy.com

Lab Setup Details – Prerequisites
Operating Systems – Windows 7 or Linux(RHEL 7.X or Ubantu)
JDK 1.7 or Higher
SCM Tool Clients Installed (SVN, GIT, Perforce)
Servlet container like GlassFish and Tomcat (If one wants to host Jenkins outside) – Optional

[If trainee is having any specific learning agenda to be addressed in this training apart from the table of Content as below; please email me @ info@scmgalaxy.com]

Table of Content

Continuous Integration with Jenkins

• What is Software Configuration Management
• What is Build and Release Engineering
• Introduction of Version Control Management?
  • Basic usage of Subversion
  • Basic usage of git
• Introduction of Build Management?
  • How to write ant script?
  • How to write Maven script?
  • How to write MSBuild Script?
• Introduction of Release Management?
• Benefit of Continuous Integration?
• Different Continuous Integration Tools?
• Focus on Jenkins
• Installation and Setup of Jenkinks
• Configure a Job to Build the Project using SVN /GIT and ANT/Maven
• Using Build Script (Ant, Maven and MSBuild) with Jenkins
• Authentication and Authorization in Jenkins
• Lab and Assignment
• Nodes Setup in Jenkins
• Labels, Tags and Notification using Jenkins
• Empowered with Plugins in Jenkins
• 20 Popular Plugins and Their Usage
• Integrating Jenkins with Junit for automated testing
• Integrating Jenkins with HP-QC for automated testing
• Integrating Jenkins with Cobertura for test Coverage
• Integrating Jenkins with Sonar for static code analysis
• Release and Deployments using Jenkins and Nexus
• Advance Jenkins
  • Jenkins Scripting
  • Jenkins Command line
• Reporting and Dashboard using Jenkins
• Lab and Assignment

Build and Release Training In Bangalore | Build and Release Training in India | Build and Release Training in Hyderabad | Build and Release Training in Delhi | Build and Release Training in Pune | Build and Release Trainer In Bangalore | Build and Release Trainer in India | Build and Release Trainer in Hyderabad | Build and Release Trainer in Delhi | Build and Release Trainer in Pune

The post Build and Release Course Training with Jenkins / Maven /Ant/ SVN & Git appeared first on scmGalaxy.

Upcoming Training Dates | Training Agenda | Training Calender | FAQ | Why scmGalaxy Online Training

Click Here

Mode – Online

Lab Setup Details OR Prerequisites for personal Laptop

Operating Systems – Windows 7 or Linux (RHEL 7.X or Ubantu)
JDK 1.7 or Higher,
SCM Tool Client and server Installed (SVN, GIT, Perforce)

Send us an email to info@scmgalaxy.com with the confirmed payment receipt for acknowledgement

Free Lunch would be serve to all Participants.
Registration is based on First Come basis and only confirmed registration would be considered.

1. What is Software Configuration Management
2. What is Build and Release Engineering
3. Introduction of Version Control Management?
4. Basic usage of Subversion
5. Basic usage of git
6. Introduction of Build Management?
7. How to write ant script?
8. How to write Maven script?
9. How to write MSBuild Script?
10. Introduction of Release Management?
11. Benefit of Continuous Integration?
12. Different Continuous Integration Tools?
13. Focus on Jenkins
14. Installation and Setup of Jenkinks
15. Configure a Job to Build the Project using SVN /GIT and ANT/Maven
16. Using Build Script (Ant, Maven and MSBuild) with Jenkins
17. Authentication and Authorization in Jenkins
18. Lab and Assignment
19. Nodes Setup in Jenkins
20. Labels, Tags and Notification using Jenkins
21. Empowered with Plugins in Jenkins
22. 20 Popular Plugins and Their Usage
23. Integrating Jenkins with Junit for automated testing
24. Integrating Jenkins with HP-QC for automated testing
25. Integrating Jenkins with Cobertura for test Coverage
26. Integrating Jenkins with Sonar for static code analysis
27. Release and Deployments using Jenkins and Nexus
28. Advance Jenkins
29. Jenkins Scripting
30. Jenkins Command line
31. Reporting and Dashboard using Jenkins
32. Lab and Assignment

Build and Release Training In Bangalore | Build and Release Training in India | Build and Release Training in Hyderabad | Build and Release Training in Delhi | Build and Release Training in Pune | Build and Release Trainer In Bangalore | Build and Release Trainer in India | Build and Release Trainer in Hyderabad | Build and Release Trainer in Delhi | Build and Release Trainer in Pune

The post Build and Release Training in Bangalore appeared first on scmGalaxy.

Continuous integration techniques with MSBuild, TeamCity, NUnit, NCover, FxCop, and Microsoft Web Deploy

scmGalaxy is a community initiatives based on Software configuration management that helps community members to optimize their software development process, Software Development Life Cycle optimization, Agile Methodologies and improve productivity across all aspects of Java development, including Build Scripts, Testing, Issue Tracking, Continuous Integration, Code Quality and more. scmGalaxy group that helps organisations optimize their software development process. We provide consulting, training and mentoring services in Agile Development Practices such as Version Management, Continuous Integration, Build Management, Test-Driven Development, Acceptance-Test Driven Development, Build Automation, Code Quality Practices and Automated Testing.

We provide job oriented training in the area of Configuration management, Build and Release Engineering. Candidates with engineering or software background and looking to either start or change their career to Build and Release Engineering, would benefit most from this training. Instructor-led training course offered in India, Bangalore, Delhi, Pune, Mumbai and Hydrabad. Instructor is an expert in Software configuration management, Build and release engineering with more than 15 years industry experience in india.The Goal of the course make the training attendants equip with all the concepts of build and release engineering.

Contact us at info@scmGalaxy.com | Call – +91 700 483 5930 | Skype – scmGalaxy

Course Objectives
To bring your team up to speed with agile development, We can also run the from Continuous Integration to Continuous Delivery with autoamted course within your premises.

Course Schedule
This course is an intensive 1-day & 2-day workshop with a mixture of teaching and lab exercises. Currently, this course is offered exclusively as an on-site course. Please contact us for more details.

Audience
This is a hands-on, practical course designed to teach specialised skills for real-world development situations. It is thus primarily aimed at a SCM Engineer, Build/Release Engineer and developer audience.

Approach
The course is modular and flexible – depending on specific student needs and requests. Through our trainings, you benefit from the wide experience and architectural expertise of our team. We bring that experience to you in an highly interactive, intensely hands-on setting.

Assumptions
We assume participants have a reasonable understanding of Development in any language as well as a basic understanding of the Software Development Life Cycle.

Lab Work
All our courses are above all practical in nature. We believe that the best way to learn is by doing. So the course contains approximately 80% lab work.

Learning Resources
Each registrant will receive a copy of the student notes and lab solutions, a certificate of completion, and a CD containing all the tools covered in the course and CD containing all the tools covered in the course.

Contact Us
This course is provided on-site, and can be tailored to your particular requirements. If you would like our trainings delivered at your premises, or for any additional information please contact us. Please email us at info@scmGalaxy.com

Course outline

The basic course program is outlined here:

A Gentle Introduction

• Overview
• Levels of Code Confidence
• CI as an Enabler
• Benefits of Continuous Integration
• Summary

Minimum Requirements

• Overview
• The Check-In Dance
• Continuous Integration Do’s and Don’ts
• Summary

Building a Solution

• Building a Solution
• Overview
• Hello, Continuous Integration
• Recommended Solution Layout
• The Software
• Building on the CI Servera
• Build Failure Notifications
• Receiving a Build Failure Notification
• Summary

Build Scripts

• Build Scripts
• Overview
• Why Do We Need a Build Script?
• Decision Point: How to Add Build Steps
• Recommendation: Do Not Modify csproj/vbproj
• Recommendation: Do Not Script csc.exe/vbc.exe
• Recommendation: Script Everything, but Compile with MSBuild
• Why the Command Line?
• Hello, MSBuild
• Defining Targets
• Running from the Command Line
• Compiling the Solution
• Setting the Default Target
• Eliminating Duplication
• Switching Between Debug and Release
• Scripting Other Tasks
• Using Custom Tasks
• Handling Non-Fatal Command Failures
• Depending on Multiple Targets
• Running on the CI Server
• Summary

Integrating External Tools

• Integrating External Tools
• Overview
• External Tools
• Test Runners
• Integrating NUnit via Exec Task
• Failing the Build with Exit Codes
• Running Tests on the Build Server
• Displaying Test Reports
• Coverage
• 100% Coverage Myth
• Integrating Coverage
• Integrating NCover via Custom MSBuild Tasks
• Failing the Build on Low Coverage
• Running Coverage on the Build Server
• Static Code Analysis
• Integrating FxCop
• Failing the Build by Analyzing XML Output
• Summary

Deployment Automation

• Overview
• Packaging/Deployment Options
• Server Preparation
• Deployment Pipeline
• Continuous Deployment
• Adding Packaging to the Build Script
• Finding Microsoft Web Deploy on a Developer Machine
• Packaging from the Command Line
• Packaging on the Build Server
• Installing Microsoft Web Deploy on the Web Server
• Adding Deployment to the Build Script
• Integrating Deployment into the Pipeline
• Demonstrating Continuous Deployment
• Summary

The post Continuous Integration Training | Continuous Integration Course | Online | Classroom | India appeared first on scmGalaxy.

Click Here

scmGalaxy is a community initiatives based on Software configuration management that helps community members to optimize their software development process, Software Development Life Cycle optimization, Agile Methodologies and improve productivity across all aspects of Java development, including Build Scripts, Testing, Issue Tracking, Continuous Integration, Code Quality and more. scmGalaxy group that helps organisations optimize their software development process. We provide consulting, training and mentoring services in Agile Development Practices such as Version Management, Continuous Integration, Build Management, Test-Driven Development, Acceptance-Test Driven Development, Build Automation, Code Quality Practices and Automated Testing.

We provide job oriented training in the area of Configuration management, Build and Release Engineering. Candidates with engineering or software background and looking to either start or change their career to Build and Release Engineering, would benefit most from this training. Instructor-led training course offered in India, Bangalore, Delhi, Pune, Mumbai and Hydrabad. Instructor is an expert in Software configuration management, Build and release engineering with more than 15 years industry experience in india.The Goal of the course make the training attendants equip with all the concepts of build and release engineering.

Contact us

• Mail – info@scmGalaxy.com
• Call – +91 700 483 5930
• WhatsApp – +91 700 483 5930
• Skype – scmGalaxy

Course Objectives
To bring your team up to speed with agile development, We can also run the from Continuous Integration to Continuous Delivery with autoamted course within your premises.

Course Schedule
This course is an intensive 1-day & 2-day workshop with a mixture of teaching and lab exercises. Currently, this course is offered exclusively as an on-site course. Please contact us for more details.

Audience
This is a hands-on, practical course designed to teach specialised skills for real-world development situations. It is thus primarily aimed at a SCM Engineer, Build/Release Engineer and developer audience.

Approach
The course is modular and flexible – depending on specific student needs and requests. Through our trainings, you benefit from the wide experience and architectural expertise of our team. We bring that experience to you in an highly interactive, intensely hands-on setting.

The Working With Continuous Integration training course provides the learning and hands-on experience required to jump start a software development team’s adoption of continuous integration. Using a project-centric blended learning model, the students will examine common testing strategies, learn the fundamental concepts of continuous integration, set up a continuous integration environment, and incorporate continuous integration into their project’s SCM environment.

The Working With Continuous Integration can be delivered using Bamboo, Jenkins, AnthillPro, TeamCity and BuildForge.

If you need help setting up a CI environment, consider extending this course with two days of expert-led consulting.

In the Working With Continuous Integration training course, you’ll learn:

• Introduction to Continuous Integration
• What Is CI?
• Why CI?
• CI Philosophy
• Advantages of CI Within Software Development
• How to Implement CI
• Setting Up a CI Environment
• CI Tools
• Automated Builds
• Automated Tests
• Committing Code
• Creating a Full-featured CI Environment
• Components of a Full-featured Environment
• Requirements of a CI Environment
• Organizational Impact and Buy-in
• Developer Philosophy
• DB Integration
• Automated DB Integration
• Continuous DB Integration
• Continuous Testing
• Automated Unit, Integration, System and Functional Tests
• Writing Tests for Defects
• Integration of Automated Testing With CI
• Continuous Quality
• Code Inspection vs. Code Testing
• Automated Code Analysis
• Code Analysis Tools
• Continuous Deployment
• Philosophy
• Release and Labeling Strategies
• Continuous Improvement
• The Feedback Loop
• The Metrics Loop
• The Improvement Cycle
• Best Practices
• Best of Breed Tools
• Best Practices for Quality Software
• Best Practices for CI
• Rolling Out CI Within Your Organization
• Defining and Measuring Metrics and Reporting
• Defining Proper Metrics
• Measuring and Reporting
• Implementing a Change Strategy to Achieve Desired Metrics

The post Continuous Integration Training | Continuous Integration Course | Trainer | Online | Classroom appeared first on scmGalaxy.

Selected AnthillPro Interview Questions

• Building Procedures in AnthillPro
• Deploying Procedures with AnthillPro
• Using AnthillPro for Audit
• Process of Integrating with Defect & Feature Tracking
• Process of Integrating with Static Code Analysis

The post Selected AnthillPro Interview Questions appeared first on scmGalaxy.

With Visual Studio 2010 RC released recently, we jumped on the release and began to code with VS2010.  One issue that popped up was that now all builds were targeting MSBuild 4.0.

That doesn’t seem to be a big problem until our CruiseControl CI server kicked in, downloaded our updated code and failed building the upgraded projects.

Fortunately there is a very quick solution to this little problem.  There are a couple of requirements.

1. You need to have VS2010 RC installed somewhere
2. You need to download the .Net Framework 4.0 (I recommend the full version and not just the Client Profile, it ensures you don’t miss anything)

To fix, do the following:

1. download and install the .Net Framework 4.0 on the CI server (then restart the server)
2. on the computer where VS2010 RC is installed go to the following path:
%programfiles%\MSBuild\Microsoft\VisualStudio
3. copy the v10.0 folder located in that directory into the CI server at the same path (or wherever our MSbuild path is on the CI server)
4. Once that is done, edit the ccnet.config file at the tag and change it to the new .Net 4.0 Framework installed (you should only need to change the section “\v3.5\” to “\v4.0.xxxxx\”

Hope this helps

The post Running MSBuild 4.0 and MSBuild 3.5 on Continuous Integration appeared first on scmGalaxy.

Bamboo – A Continues Integration Server

Continuous integration (CI) brings faster feedback to your development process, preventing bugs from piling up and reducing the risk of project delays.

Bamboo enables development teams of any size to adopt CI in minutes, easily integrate it with their work day and scale their build farm using elastic resources in the Amazon EC2 cloud.

Continuous integration (CI) brings faster feedback to your development process, preventing bugs from piling up and reducing the risk of project delays.

Bamboo enables development teams of any size to adopt CI in minutes, easily integrate it with their work day and scale their build farm using elastic resources in the Amazon EC2 cloud.

Bamboo makes every stage of continuous integration adoption easy, intuitive and pain-free.

Set up your first CI build in minutes
Integrate/ Collaboration CI with your current tools and workflow
Scale your build farm on-premises or in the cloud!
Analyse and improve your build performance
Extend Bamboo with plugins and the REST API
Full feature list and system requirements

Integrate/ Collaboration

Bamboo lets you pick how and when you’re notified about builds and integrates easily with tools you’re already using, so your team will be able to work together to keep your builds green!

Notifications via email, RSS, IM or IDE pop-up:
With Bamboo each team member can choose how and when to be notified:

Email, RSS, IM or IDE pop-up notifications
Customised email templates (HTML or plain-text)

Choose which builds to be notified about:

All builds for a project
Specific build plans
Every time a build finishes, only when it fails X times, only when it hangs, or only when it times out

Priorities your build queue
When your build agents are busy, Bamboo builds go into a queue.

Need to see the results of a build ASAP? You can:

Escalate builds to the front of the queue with one click.
Stop in-progress builds.
Move lower-priority builds to the back of the line.

Apply labels and comments to build results
Why did a build fail? What did you fix to turn it green again? Which builds have been tested by your QA team? What builds are approved for release to customers? Bamboo let’s you provide content to your builds results using labels and comments.

• Apply labels and comments via your Web browser, IDE, or Bamboo’s unique 2-way IM system
• Subscribe to an RSS feed of all build results with certain labels (e.g. “QA_FAILED”, “PATCH”,etc.)

Run and fix builds from Eclipse and IntelliJ
Bamboo integrates with Eclipse and IntelliJ IDEA to bring build management and notification into the IDE:

• Run, label and comment builds
• Receive pop-up notifications for builds you care about
• Quickly identify failing tests and re-run them locally with just one click

Link builds to JIRA issues
Bamboo integrates with JIRA and allows you to easily:

• View all builds related to an issue
• View all issues related to a build, and mark them resolved
• Embed build status and summary gadgets into your JIRA project dashboards

View changes that triggered builds with FishEye
By integrating Bamboo with FishEye, you can quickly see what files were changed to trigger a build and what JIRA issue the changes were made for. Want to see exactly what changed? FishEye diffs are just a click away!

Run Clover Test Optimization and code coverage
Integrate Clover for Java Test Optimization and code coverage, and you’ll instantly get faster builds and better code quality insights!

• Clover Test Optimization can make your Java unit and functional tests run several times faster
• View method, branch and statement coverage
• See when and where coverage drops over time

Display results in Confluence dashboard portlets
Bamboo provides portlets that can easily be embedded on any Confluence page, so you can keep every project stakeholder up to date on project status.

• See pass/fail status, duration, and number of failed tests for recent runs of a build plan.
• View the latest status for all builds in a project.

Embed JavaScript widgets in any HTML page
Bamboo provides JavaScript widgets that can be embedded into any HTML page. With just a few lines of code, create custom pages that include:

• Latest build results
• Latest changes
• Last result of all builds in a project
• Plan summary graphs

Scale Your Build System

As your team runs more and more CI builds, you’ll want to add more computing power to maintain fast feedback on your build and test results.

Bamboo makes scaling your build system a snap with:

• Remote agents that run on-premises
• Elastic agents in the Amazon EC2 cloud.

Remote agents

Your Bamboo server can manage dozens of remote agents simultaneously, taking advantage of available computing power to provide the fastest feedback possible. With remote agents you can:

• Run multiple builds at once to reduce feedback times
• Test on different platform configurations

Elastic agents

Elastic agents are remote agents that run in the Amazon Elastic Compute Cloud (EC2). By using the cloud, you can instantly scale your build environment as your development cycles ebb and flow and build queues become longer. Bamboo makes it easy to customize and manage your elastic agents:

• Schedule agents to start and stop based on known peaks and valleys in your need for CI builds.
• Cut operational costs by taking advantage of EC2’s reserved instance pricing and availability zones.
• Customise agent images with different operating systems, installed software, and computing power to create the most flexible building and testing system possible.
• Reduce data transfer and startup times by using Amazon Elastic Block Storage (EBS) for persistence.

Every build agent (remote or local) has specific capabilities that are used to match the requirements of queued builds.

Bamboo’s web interface makes it easy to manage all your agents and view a log of recent activity for each agent.

Analyse and Improve Your Builds

Your team is running builds on every commit, comprehensive performance and functional tests are running every night, and your build farm has been scaled out. Wondering where and how you can make improvements? Bamboo makes it easy to see the performance of your builds and identify trouble spots and possible improvements.

• Find out why a build failed
• View build plan performance across time
• See what’s breaking most so you can investigate
• Compare several plans
• Compare team performance and drill into author details

What happened?
When your builds turn red, you want to fix them as fast as possible! Bamboo provides information to your team that makes root-cause analysis easier, so you can turn the build green again ASAP.

• Full stack traces for compilation failures
• Full stack traces for test failures
• Highlighting of newly failed tests
• Click-through to the failing code from within the IDE

Build plan summaries at a glance
Bamboo’s plan summary view presents a wealth of information about each build plan including:

• Results of the latest build
• Historical pass percentage and average build time
• Result, duration, and number of failed tests for recent builds
• Duration and failure trends across time

Find your trouble spots
Bamboo identifies problem areas within each build based on its performance history including:

• Most common failures
• Tests that take longest to fix
• Long-running tests

Compare your build plans
Which builds are turning red the most often? Which builds are taking longest to run? Bamboo reports provide useful information within a few clicks, for the exact set of plans you care about. Reports include:

• Success percentage
• Duration
• Activity
• of tests
• of failed tests
• Time to fix failures
• Clover code coverage

View the CI scorecard
Who’s submitting bullet-proof code? Who’s going to buy beer for breaking the most builds? Bamboo provides insightful reports for:

• Full Teams: # of builds triggered / failed / fixed
• Individuals: build history, last 10 triggered / failed / fixed
• Groups: Success percentage, # of failed / fixed builds

Extend Bamboo

Bamboo works great right out of the box, and it can be extended to fit your exact needs:

• Install 3rd party plugins from the Atlassian Plugin Exchange to add support for additional SCMs, test tools and more.
• Create your own Bamboo plugins. Get help from Atlassian and other Bamboo developers in the Bamboo Development Forum and then share your plugins on the Atlassian Plugin Exchange
• Use Bamboo’s comprehensive REST API to integrate Bamboo with other tools or automate common tasks.

System requirements and supported development tools

Build and agent management

Build result notifications

External tool integrations

Elastic Bamboo

Build analysis and reporting

Security and user management

Extending Bamboo

Reference:

Features:
http://www.atlassian.com/software/bamboo/features/
Bamboo: getting Started
http://confluence.atlassian.com/display/BAMBOO/Bamboo+101
Forum
http://forums.atlassian.com
Plugins
https://plugins.atlassian.com/search/by/bamboo
http://confluence.atlassian.com/display/BAMBOO/Bamboo+Plugin+Guide
Jira and Bamboo
http://www.atlassian.com/better-together/progress_report.jsp

The post Bamboo – A Continuous Integration Server – Complete Guide appeared first on scmGalaxy.