Update: Bitbucket Pull Requests

Posted on August 22, 2018

Pull Requests builds are useful in answering the question “What if this PR merged into target (base) branch”. Feature branch (other terms are source or head branch) build is not enough to answer this question, because while PR was developed some other commits could be made to the target (or base) branch.

During PR build AppVeyor merges PR with target (source or head) branch safely in transient build environment and runs required build scenario. Scenario itself can be altered in many ways for Pull Requests builds with project settings (like Pull Requests do not increment build number) and specific PR-related environment variables (like APPVEYOR_PULL_Requests_HEAD_REPO_BRANCH).

AppVeyor supports GitHub Pull Requests builds for years. Now we added Bitbucket Pull Requests support. For new projects it should work out-of-the box. For existing ones AppVeyor project webhook should be updated so the following Pull Requests events added: Created, Updated, Merged, Declined. To set this, navigate to your Bitbucket repository Settings tab, select Webhooks, find AppVeyor project webhook and press Edit.

If you do not need Bitbucket PR builds for new projects, uncheck those Webhook setting, so AppVeyor will not be notified of Bitbucket PR creations and changes.

Best regards,
AppVeyor team

Update: Artifacts retention policy

Posted on June 05, 2018

Since we announced an Artifacts retention policy on May 24th, we have heard your concerns and are making the following changes to the policy:

Best regards,
AppVeyor team

Updates to the AppVeyor Privacy Policy

Posted on May 25, 2018

As of May 25th, 2018, Appveyor Systems Inc. has updated its Privacy Policy to align with the General Data Protection Regulation (GDPR) that is in effect across the European Union.

For more information, please review our updated Privacy Policy.

Best regards,
AppVeyor team

Follow us on Twitter: @appveyor

Artifacts retention policy

Posted on May 24, 2018

Artifacts functionality has been working great for our customers since we introduced it in 2013, but we collected a huge amount of artifacts which are persisting in cloud storage.

Through talking to many customers we’ve identified that, after some period of time, storing old artifacts is unnecessary.

Indeed, once the app is deployed or a release package uploaded to external storage, its underlying artifact is usually no longer needed (except for those rare moments when some previous/stable release has to be re-deployed!)

To reduce AppVeyor hosting costs and eliminate any unnecessary waste of cloud resources we decided to introduce an artifacts retention policy.

The policy states that build artifacts and NuGet packages of paid accounts older than 6 months and free accounts older than 3 months will be permanently removed from AppVeyor artifact storage.

This policy will take effect on June 7, 2018.

If you have custom requirements please let us know and we’ll discuss your needs.

Best regards,
AppVeyor team

Follow us on Twitter: @appveyor

AppVeyor for Linux is generally available

Posted on May 15, 2018

Dear friends!

Just a short two months ago we announced the private beta of AppVeyor for Linux and we’ve been amazed by the amount of positive feedback we received and how high the demand was.

Thank you for your active participation! We managed to find and fix some issues, add missing pieces and make it ready for GA.

Starting today Ubuntu image will be available to all accounts, free and paid alike. The current working image users will see is based on Ubuntu 16.04 (Xenial Xerus) and a new one based on Ubuntu 18.04 (Bionic Beaver) will be added soon. We are committed to providing you the best and the latest Linux experience on our platform.

There is the Getting started with AppVeyor for Linux guide where you can also find a list of supported features and software pre-installed on the image.

Now AppVeyor is officially a multi platform CI service!

Enjoy your build!

Best regards,
AppVeyor team

Follow us on Twitter: @appveyor