Featured Upcoming Event
In this upcoming DPE webcast (July 14, 2022, 10:00 - 11:00 AM PDT), we talk to Gautam Korlam and Ty Smith from the Developer Productivity and Experience team at Uber. We’ll explore the platform they built to improve the productivity of their engineers and ship new features with increased velocity and reliability to Uber users.
Key topics include:
- The size and structure of DPE and DevEx teams, as well as the development and product teams they support
- Programming language and tools used
- Data and metrics collected to evaluate developer productivity success
- Key productivity engineering wins
- Special projects like the, “remote cloud IDEs project”
- DPE moonshots
BEST PRACTICES
In the course of engineering new solutions that improve developer productivity by speeding up builds and tests, Gradle will introduce new DPE concepts and new enabling technologies. In a recent blog post, we introduce and explore the concepts and technologies associated with performance consistency and performance continuity.
Performance consistency refers to the ability to achieve minimum variation in build and test feedback cycle times at minimum cost regardless of the change that triggers the build. It can be achieved by deploying performance acceleration solutions to improve feedback cycle time consistency, as well as average cycle time.
Performance continuity refers to the ability to sustain improvements in average build and test time over a period of months, as inputs continuously change and the number of lines of code, repositories, and dependencies grow. It can be achieved by leveraging the build performance analytic and profiling information available in the Gradle Enterprise performance continuity solution.
Check out the blog post to learn more about the benefits of achieving elevated states of both performance consistency and performance continuity.
IDEAS & INSIGHTS
Here are the top 10 Build Scan™ capabilities you can utilize to fix Gradle, Maven or Bazel build and test problems by more efficiently identifying the root cause:
- Compare scans to pinpoint a failure root cause.
- Collaborate effectively by sharing any detail of a Build Scan using a deep link.
- Leverage an enhanced console log.
- Discover dependency-related failures.
- Detect and correct deprecations.
- Use the plugins list view to assist in debugging.
- Expand Build Scan data with custom values & tags.
- Utilize switch and infrastructure data.
- View the details of a failed test method, including stack trace/output and trend data.
- Get a timeline view of your build and filter by build action outcome.
We recently published a playlist of one-to-two minute videos that explain how to use all of the key features of Gradle Enterprise Build Scan listed above (except Build Comparison but you can view that explainer video on our website). When you’re ready, get started using the FREE Build Scan service.
|
