Changes And Updates

Wercker is a Docker-Native CI/CD Automation platform for Kubernetes & Microservice Deployments

Benno van den berg
Benno van den berg
November 8, 2013

Over the last couple of weeks we’ve been busy. In this post we’ll go over some of those changes.

GitHub pages ignored branch

GitHub has the option to host pages if they exists in a special branch namedgh-pages. It doesn’t make sense to start a build on the gh-pages branch, since it’s just content. So wercker now ignores the gh-pages branch for GitHub projects. In the near future it will be possible to use your own custom ignored branches.

CWD

Some steps require a different working directory than the wercker root. Some steps already had some support to change the working directory. Wercker now supports a special element named cwd in all steps. With this you’ll be able to change the working directory. This will either be an absolute path (starting with a slash) or a relative path (relative from $WERCKER_ROOT).

Non Wercker users

Our support for non wercker users has greatly improved. In the past, when user without a linked wercker account, pushed code to github or bitbucket, the interface would not show the gravatar of that user, or even would not auto-deploy. Now you’ll be able to see the avatar of the user and link directly to the user profile page. It’s also possible to do auto deploys.

Android API level 19

We’ve update the wercker android box to support api level 19, also known as Android 4.4 or KITKAT. The box now contains api level 17, 18 and 19 and also system image level 19 (android 4.4 emulator). You can use step setup-android-emulator to create and start the emulator.

User interface updates:

We’ve changed the behavior of the application list on two areas of wercker:

  • my apps page
  • profile pages

The application list is now sorted alphabetically, making it much easier to find that one application.

Don’t forget to send us your feedback! You can contact us via twitter and the feedback button on wercker or send us an email at pleasemailus@wercker.com.

Earn some stickers of your own!

Let us know about the applications you build with wercker. Don’t forget to tweet out a screenshot of your first green build with #wercker and we’ll send you some @wercker stickers.

Thanks for tuning in, and there will be more posts next week! Follow us on twitter as well to stay in the loop.