CodeShip changelog codeship.com

The “build groups” feature, that shows restarted builds grouped together in a single build element, has now been rolled out to all users on CodeShip Basic!

When you restart a build, you will see the previous build run status nested underneath the current build run.

We are making a light design refresh to the build items on your project pages and your personal dashboards. These should be a little cleaner and a little easier on the eyes now.

We keep improving our recent Manual Approval feature, and this time we've added a new environment variable that you can use to check if a build has been approved or not.

On all builds running as a result of a manual approval, we now set the environment variable CI_BUILD_APPROVED to true.

This means that you can write conditional scripts to avoid steps re-running on builds triggered as a result of manual approvals:

if [[ "${CI_BUILD_APPROVED}" == "true" ]]
then
    echo "This only happens after approval is given"
else
    echo "And this only happens before approval is given"
fi

New packages have been added to the CodeShip Basic build VM:

• NodeJS 11 was added
• Ruby 2.5.3 was added
• PHP versions were bumped:
  • 7.1.23 -> 7.1.24
  • 7.2.11 -> 7.2.12

Another week, more updates:

• Ruby 2.5.3 was added
• ChromeDriver was updated from 2.41 -> 2.43

Today we updated a couple of packages:

• PHP packages were updated
  • 7.1.22 -> 7.1.23
  • 7.2.10 -> 7.2.11
• Ruby packages were added
  • 2.3.8
  • 2.4.5
  • 2.5.2
• Java was updated
  • 8u181 -> 8u191

Don’t want all your branches to trigger a build? Now you can control what gets build with the new exclude/include filter option

The new feature allows you to either specify the branches you don’t want us to build, or just the ones you want us to build. Note though that you have to specify exact branch names.

We’ve just finished up a short period of house cleaning. It may not all be visible, but it all adds up to a better CodeShip.

Among the updates are:

• Better error-handling for GitLab CE/EE and GitHub Enterprise
• More strictly enforced handling of minimum versions of self-hosted SCMs
• New look and vastly improved performance for teams management

Read more about each of these in the blog post

We have made two small updates to our permissions today: Managers are now able to approve builds, and everyone can restart builds.

Since launching the manual approval we've received feedback on what could improve that feature, and the one that stands out is that restricting approval to only owners is not flexible enough, so we've expanded the permission to users with Manager roles as well.

We've also heard that quite a few of you are using the contributor role for regular team members, and not allowing them to restart builds creates an overhead of them requesting build restarts etc. From today, all types of users are able to restart builds.

We’re happy to announce that today we updated our Slack notifications to be more readable and also have a link to the commit SHA that triggered this build: We find the commit link especially useful and have enjoyed being able to jump straight to the commit from the notifications, skipping a number of clicks!