As part of the work around GDPR compliance we also wanted to allow users to delete their own user profile(s) without having to reach out to support. This is now possible via the Personal Settings view:
Just like everyone else, we’ve been making sure that we’re GDPR compliant and today we released a few updates related to that.
- There’s a new documentation article specifically on GDPR, what data we capture, what we use it for, and how to exercise your rights as a user.
- When you go to the Codeship UI you will be asked to opt in to capture data on how you use Codeship. If you’re okay with it, it’ll greatly help us improve Codeship and will allow us to help you better in the future as well
- If you want to opt out later (or opt in) the setting is available on your Personal Settings page
- We’ve also turned off all tracking that wasn’t related to learning about how our users use Codeship, so no more Facebook, Twitter, etc.
As always let us know if you have any comments, concerns, or questions
Notification on Stopped Build
A small change to our notification module was released today: when you select to be notified about failed builds, we now include stopped builds as part of that notification.
Previously, there we no notifications for stopped builds.
Deprecation Notice: Python 3.3
Python 3.3 was EOL'ed September last year and is no longer available for us to install. We will be completely removing Python 3.3 from Codeship Basic on June 18th, 2018.
Manual Build Step Approvals
We just released a brand new feature that has been requested by many of you: the ability to require manual intervention inside a build on Codeship.
Starting today, you can require a manual approval for builds to be run on Codeship Pro. With the addition of manual approval, it’s now easier to keep your deployment environments secure and control who has access to deploy, and when deployments can happen.
To read more about how to use the new feature, head over to the blog post
New for all Codeship Pro builds
Related builds are now folded into one visual element, so if you restart a build, it'll show up as part of a build group. Like this:
Codeship Basic Build VM
Today we updated two packages to newer versions:
- Updated Firefox to 60.0
- Updated nvm to 0.33.11
Codeship API v2 update
We've made a small improvement to the API in that we're also returning the branch name as part of a build's payload.
Codeship Basic Build VM
This last week have seen a few package updates for Codeship Basic:
- Updated ChromeDriver to 2.38
- Updated geckodriver to 0.20.1
We also added support for Node.js 10
Jet Version 2.5.1 Released
Fixes a bug where Jet was not cleaning up containers and networks for services that had a failing healthcheck.
Deletion of Old Codeship Basic Deployment Templates
Some time ago we deprecated a list of deployment templates that was either using old, unsupported scripts or methods, or were simply targeting services that no longer exist (or is in the process of shutting down).
Today we fully removed the code behind the following deployment templates (we checked, on one's been using them for months, so this shouldn't really impact you):
- Engine Yard
No published changelogs yet.
Surely Codeship will start publishing changelogs very soon.
Check out our other public changelogs: Buffer, Mention, Respond by Buffer, JSFiddle, Olark, Droplr, Piwik Pro, Prott, Ustream, ViralSweep, StartupThreads, Userlike, Unixstickers, Survicate, Envoy, Gmelius, CodeTree