Skip to main content

Deploy Your Components in Less Time - Winter15


You can now deploy components to production by skipping the execution of all Apex tests for components that have been validated within the last four days. With Quick Deploy, you no longer have to wait for all tests to run for your deployment to complete in production.

As part of a deployment to production, all Apex tests are run in the production organization. If the organization contains a large number of Apex tests, the execution of all tests can be time-consuming and can delay your deployment. To reduce deployment time to production, you can perform a quick deployment by skipping the execution of all tests. Quick deployments are available only for validations with test runs that have passed in the last four days (96 hours) and that meet the code coverage requirements: the overall code coverage in the organization must be at least 75%, and Apex triggers must have some coverage.

You can start a quick deployment only through the Salesforce user interface. Quick Deploy is available for change sets and Metadata API-based deployments that appear in the user interface.

Looks like Salesforce is recognising that deployment is turning to be a pain, so a nice step in making deployment easier. It's still in pilot though.

Comments

  1. Do you realize there's a 12 word phrase you can speak to your partner... that will trigger deep feelings of love and impulsive appeal for you buried within his heart?

    That's because deep inside these 12 words is a "secret signal" that fuels a man's impulse to love, admire and protect you with all his heart...

    12 Words Who Trigger A Man's Desire Response

    This impulse is so hardwired into a man's brain that it will make him try harder than ever before to make your relationship the best part of both of your lives.

    Matter of fact, fueling this all-powerful impulse is absolutely essential to having the best ever relationship with your man that as soon as you send your man one of the "Secret Signals"...

    ...You will soon find him expose his mind and soul to you in a way he's never expressed before and he will recognize you as the only woman in the world who has ever truly appealed to him.

    ReplyDelete

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client ser

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object.  Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations