Previously, I explained how to implement a fully automated branch per task cycle with Bamboo to merge branches when certain conditions were met. Now, I will explain how to implement the same solution with TeamCity.

What I'm going to explain now is how to configure TeamCity to monitor Plastic SCM branches and directly merge them to main when certain conditions are met (when a certain value is assigned to an attribute or even certain status in the associated issue tracker).

In the example, I'm going to keep using Jira as issue tracker, but nothing prevents you from connect to any other issue tracking system.

Cycle described

Plastic finds changes super-fast. We expect Pending changes to refresh in under two seconds and three to four seconds for bigger projects that have more than 90,000 files in a workspace. Note: The first time that you open it, it will take longer because of some caching and disk monitoring setup.

If your Pending changes is not performing that fast, there is something wrong.

Back in release, we added a performance warning in Pending changes when it detects that finding changes is slow. The warning includes a link to the documentation with performance recommendations:

This blogpost explains how to troubleshoot beyond the basics for what might be slowing down your Pending changes view.

I'm writing this for the core users like you because we want to share with you what we are working on and what we are busy with, so you can be on the same page as us. I engage in conversations with hardcore Plastic SCM users like you weekly, if not daily, and I find myself sharing some of our ideas on a one-to-one basis. But, I think having a blogpost putting it all together and sharing the global vision can really help create even better interactions with all of you.

So, here it goes, this is what we have in the backlog for 2018.

Plastic SCM 2018 backlog

From app to games is a series of posts here in the Plastic SCM blog where we are going to share some ideas and challenges faced by an app developer when creating some games. We are going to start by creating games for the web, but later we are going to develop for game engines as well, such as Unity, GameMaker and others. In this first post, we are going to design and start the creation of an anagram game using a top trending web library named ReactJS.

Welcome to React
Game developers are close to 25% of Plastic SCM users today. That's why we went again to the Game Developers Conference in San Francisco, March 21st-23rd, to meet many customers, and of course many new interested ones.
Plastic SCM at GDC

If you have been using Plastic for a while, you probably know what "merge-to" is and when it is useful. Well, we just made it better; it now supports full conflict resolution! With GUI support for Linux, OS X and Windows available.

Merge-to feature

Super quick intro to merge-to

Regular merges happen like this: you switch your workspace to the destination (where you want the merge to go) and then you merge from source (what you want to merge from).

Internally we tend to call it "merge-from".

Merge contributors

Well then, what is merge-to?

UPDATE 2018/04/04: We included a link to a webinar about DevOps with Atlassian Bamboo, Plastic SCM and Jira

To implement a full DevOps strategy, it is crucial to fully automate the testing and merging of each task branch. Automation is the way to achieve faster delivery of tasks required to fully implement DevOps.

I explained a recommended DevOps cycle and how to implement it with Atlassian Bamboo and Plastic in two previous blogposts.

Now, I'm going to cover how to fine tune the process by introducing Jira into the equation. What if Bamboo requires a given Jira task status to test and merge the associated task? What if the testing and merging process is reflected back onto the Jira task status? This is exactly what we released in and what I'm going to explain in detail in this post.

How pieces fit