#continuous delivery

[screwdriver-cd]

New bug fixes and features - April 2025

New Features

UI

Introduced a Glimmer component for managing pipeline secrets in the new UI to enhance user experience and functionality. See PR.

Introduced a new Glimmer component to manage API tokens, allowing users to create and manage them more efficiently. See PR.

PR Desync: a feature in the UI to detect and notify users of desynced pull requests in the database due to prolonged pipeline inactivity, providing a convenient resync button. See PR.

Support for reverting overridden secrets and improved ambiguity in secret deletion messaging in the new UI. See PR.

Introduced a new navigation bar for switching between secrets and tokens in the new UI. See PR.

Default status sorting added to the event jobs table, with sorting based on build color and then alphabetically by stage and job name. As depicted below, the failed build is sorted at the top. See PR.

API

Added feature to trigger jobs when a pull_request closed webhook event is received in Screwdriver. See PR and guide. 

Added feature to set event status when a build is updated, tracking overall execution status for an event. See PR.

Added a DELETING state to the pipeline to prevent updates during pipeline deletion, addressing remaining pipeline data post-deletion issue. See PR.

Implemented a feature flag to control log payload logging, aiding log volume management. See PR.

Pipeline admin user list now updated based on SD user permissions table. See PR.

Bug Fixes

UI

Implemented a fix to allow navbar to be displayed when the hamburger menu is expanded on small devices. See PR.

Fixes issues with edit secret modal in new landing page by setting secret value properly for API request and returning full response when “allow in pr” field is changed. See PR.

Ensures that the workflow graph maintains the toggle state of downstream triggers when switching between different pipeline events. See PR.

Event rail reloading logic in the new pipeline landing page was adjusted to align with the vertical collection component. See PR.

Fixes an issue where cacheKey was incorrectly removed during data reloading in the pipeline workflow, ensuring the latest commit SHA is correctly reset. See PR.

Pipeline header updating issue resolved by adding necessary tracking to update properly when a pipeline changes. See PR.

Pipeline root directory now included and displayed alongside branch name in new UI. See PR. 

API

Added a check for adminUserIds for backward compatibility in situations where old pipelines have a null adminUserIds column due to inability of MySQL 5 version to set default values in TEXT fields. See PR.

Fix for triggering the next build on the child event when some builds are restarted before all builds are completed. See PR. 

Compatibility List

In order to have these improvements, you will need these minimum versions:

API - v8.0.26

UI - v1.0.1272

Store - v7.0.0

Queue-Service - v5.0.1

Launcher - v6.0.221

Build Cluster Worker - v5.0.1

Contributors

Thanks to the following contributors for making this feature possible. 

Akinori

Keisuke

Ming

Pritam

Sagar

Vonny

Yuki

Yuta

Jithin

Questions and Suggestions

We’d love to hear from you. If you have any questions, please feel free to reach out here. You can also visit us on Github and Slack.

Author

Vonny Jap, Senior Manager, Software Dev Engineering, Yahoo

[crazybouquetgentlemen]

Top it consulting firms in usa

[lostconsultants]

Accelerating Success: The Empowering Force of Continuous Delivery

A few years ago, I was part of a software development team struggling with long, stressful release cycles. Every deployment was fraught with anxiety, and we frequently spent sleepless nights fixing bugs that slipped through rushed testing. The client was frustrated with the delays, and our team morale was plummeting. We knew there had to be a better way allowing us to deploy changes confidently…

[nous-infosystems]

Efficiency Meets Quality: The Power of Tricentis Implementation in Continuous Testing

Tricentis Implementation: Accelerate and Automate Continuous Testing

Current organizations strive to deliver high-quality applications at an accelerated pace. This requires efficient and effective software testing practices to ensure optimal performance and functionality. Tricentis implementation is revolutionizing the testing process by offering a comprehensive solution to accelerate and automate continuous testing, enabling organizations to achieve their software delivery goals seamlessly. This blog post will delve into Tricentis implementation and explore its benefits for agile software development.

Tricentis implementation introduces a smart and impactful analysis of software changes through intelligent test automation. With its advanced features like innovative impact analysis, regression testing, and model-based test automation, Tricentis empowers organizations to identify the impact of changes and efficiently plan their testing efforts. By automating the creation and execution of test cases, Tricentis streamlines the testing process, saving time and effort compared to traditional manual testing methods.

The Tricentis continuous testing platform is designed to integrate testing seamlessly into the agile and DevOps processes. It enables organizations to optimize and accelerate their software testing by providing real-time feedback on quality and performance. With Tricentis, teams can efficiently conduct end-to-end data integrity testing, ensuring that applications perform flawlessly across various platforms and environments. This reduces the risk of issues arising during production and enhances overall customer satisfaction.

Tricentis Tosca, a flagship product of Tricentis, is a versatile and powerful testing tool that caters to diverse software testing needs. It offers an intelligent test automation suite, enabling organizations to efficiently create and execute automated tests. With Tricentis Tosca's intuitive user interface, teams can design and manage UI tests effortlessly, ensuring maximum test coverage and accuracy. Its native testing capabilities for mobile apps further enhance the testing process, allowing organizations to deliver robust applications across multiple platforms.

One of the key advantages of Tricentis implementation is its ability to optimize and accelerate the testing process in agile and DevOps environments. By integrating seamlessly with CI/CD pipelines, Tricentis enables organizations to achieve faster software delivery cycles without compromising quality. It supports efficient test data management, allowing teams to generate and manage test data effectively, further enhancing the testing process's speed and reliability.

With Tricentis implementation, organizations can leverage the power of real-time analytics and reporting to gain actionable insights into their testing efforts. Tricentis provides comprehensive dashboards and reports with visibility into test coverage, execution results, and quality metrics. This enables teams to make data-driven decisions, identify bottlenecks, and continuously improve their testing processes for optimal results.

Conclusion

Tricentis implementation is revolutionizing the way organizations approach software testing. By accelerating and automating continuous testing, Tricentis empowers agile and DevOps teams to deliver high-quality applications at an accelerated pace. With its intelligent test automation capabilities, comprehensive testing tools like Tricentis Tosca, and seamless integration with CI/CD pipelines, Tricentis implementation is a game-changer for organizations aiming to achieve faster software delivery cycles without compromising quality.

[virtualizationhowto]

DevOps Best Practices in 2024

DevOps Best Practices in 2024 @vexpert #devops #devops2024 #devopstools #agiledevelopment #iac #terraform #continuousintegration #continuousdelivery #devsecops #ai #generativeai #virtualization #homeserver #homelab #vhtforums #learneveryday

Devops is a hug part of modern development processes in production environments. DevOps operations teams are part of the broader interaction between development and operations teams to create modern software apps that follow modern workflows. Let’s take a look at DevOps best practices in 2024 for the DevOps team and see why these are important, especially now as part of the DevOps trends we see…

[opsmxspinnaker]

After weeks of industry rumors and leaks to the press, on January 11 Harness announced that it had purchased the assets of Armory. Harness says this news “Powers [the] Future of Software Delivery” but what was (and was not) announced suggests otherwise. I’d like to share my take on what is happening and what it means to Armory Customers based on technology acquisitions I’ve seen over the last two decades. 

[automationqa]

Mastering CI/CD magic! 🚀✨ Uncover the streamlined steps behind Continuous Integration and Continuous Deployment.

Elevate your software delivery game with precision and speed. 🛠️💻

[nikparihar]

CI/CD practices have revolutionized the software development process by automating key aspects of building, testing, and deploying software, resulting in faster development cycles

[needienerdynoodle]

Structuring YAML Pipelines and nested variables in Azure DevOps

When managing pipelines for large and complex repositories with multiple ‘Platforms’, each containing multiple apps and services, then the folder structure and variable strategy can be complicated. However, if this is done right, then the payoff for template reuse is dramatic. Here, I outline my approach on the pipeline folder and YAML structure only. The variable structure allows for a full set…

[screwdriver-cd]

New bug fixes and features - Q1 2025

The Screwdriver team is pleased to announce our newest release which brings in new features and bug fixes across various components.

New Features

UI

The new Pipeline landing page is now generally available. Once users opt in, they will be redirected to the new experience.

The expand and collapse feature has been added to pipeline stages. The stage's completion status is now reflected in its border.

The display of multiple banners has been modified from a stacked format to a paginated layout

API

Relax permission check to allow admins from other SCMs to update pipeline

Added APIs to create and delete buildCluster annotations, enabling Screwdriver admins to move jobs to specific clusters

New endpoint to update buildcluster of a pipeline

Improve pipeline searches by adding the 'scmUri' query parameter

Introduced a 'not equal' filter for pipeline events creator in the pipeline events list API

Changes to banner to include scope and scopeId

Bug Fixes

UI

Pipeline header updating issue resolved by adding necessary tracking to the pipeline header component, allowing proper updates when a pipeline changes, see PR

Pipeline root directory now included and displayed with branch name in new landing page, with additional CSS styling cleanup, see PR

Corrected the aggressive logic in the new landing page that was preventing jobs included in a stage from being started/restarted, now allowing these jobs to be started/restarted as needed, see PR

Fixed missing stages border when accessing pipeline from Collection by directly requesting stage data from the backend, see PR

Enhanced UI consistency by applying standardized CSS styling to the modal button within the build detail page, aligning it with the appearance of the workflow graph tooltip start modal, see PR

Ensured the start all children pipelines API call requests the entire error object, allowing more detailed analysis of the API call and returned status code, see PR

Fix: Remote trigger's pipeline name now uses 'remoteName' instead of 'displayName' to avoid confusion. See PR

Fix: Build status determination was updated by relaxing the build meta warning object check and included warning statuses in the event card warning count. See PR

Fix: The edges from stages to upstreams are now properly drawn by providing a solution for insufficient horizontal spacing between stages. See PR

Fix: The post body for PR events was improved by correctly including the job prefix in the `startFrom` value when restarting a PR job. See PR

Fix: Column name in event job display changed from 'HISTORY' to 'STATUS' for accuracy in new landing page. See PR

Fix: Long branch names on the search page are now truncated. See PR

Fix: API fetch updated to ignore scheduler events for configured pipeline. See PR

Fix: The new landing page now correctly reloads the workflow graph when starting a new event. See PR

Fix: Overflow handling for long messages added to prevent text overflow in event card. See PR

Fix: Pipeline data removed from route models due to direct injection into components. See PR

Fix: The maximum node depth issue was fixed, addressing problems with 0-based counted node depth and empty arrays for pipelines with detached jobs only. See PR

Fix: The creation of a sparse array with empty slots which caused downstream calculations to break was fixed. See PR

Fix: Parameters drop down issue resolved in new landing page by adjusting dropdown spacing and removing additional scroll logic. See PR

Fix: Build warning determination logic was fixed to correctly display warning status. See PR

Fix: Node depth calculation in workflow graph was improved by introducing 'Topological sort' for more accurate depth assignments. See PR

Fix: An issue preventing the use of anchor tags within the navigation banner was fixed. See PR

Fix: Job restart is now disabled for jobs with no builds in the new landing page. See PR

API

Upgrade of Node.js v22 and dependencies

Addressed a bug in build triggering in certain cases of restarts, ensuring the next build is correctly triggered from the latest child event, see PR

Fixed an issue where an external trigger couldn't trigger a pipeline stage due to a misinterpretation of the event associated with the pipeline the job belongs to, see PR

Avoided creation of empty events when changed file names match the source directory, see PR

ParentBuildId now set just before execution to ensure correct metadata capture from parent builds, especially when they finish simultaneously, see PR

Converted the 'isActive' parameter from string to boolean for MySQL on banner list endpoint to ensure proper banner list retrieval, see PR

Included a webhook executor to the admin group before retrieving the pipeline token. This resolved the 'Pipeline has no admin' error during the webhook process, see PR

The metadata from the job that directly precedes the virtual job is now prioritized over the event metadata, see PR

Proper handling of virtual jobs in remote triggers, see PR

Fixed duplicate build issue by preventing the build status from updating to RUNNING if a build with the same ID is already running, see PR

Virtual builds now marked as completed when triggered by webhook, resolving a regression introduced in a previous update, see PR

Compatibility List

In order to have these improvements, you will need these minimum versions:

API - v8.0.16

UI - v1.0.1241

Store - v7.0.0

Queue-Service - v5.0.1

Launcher - v6.0.221

Build Cluster Worker - v5.0.1

Contributors

Thanks to the following contributors for making this feature possible. 

Akinori

Keisuke

Ming

Pritam

Sagar

Vonny

Yuki

Yuta

Teppei Minegishi

Questions and Suggestions

We’d love to hear from you. If you have any questions, please feel free to reach out here. You can also visit us on Github and Slack.

Author

Vonny Jap, Senior Manager, Software Dev Engineering, Yahoo

[advisedskills]

The Role of Agile Release Management in Continuous Delivery

🚀 Embracing the #Software Revolution with #AgileReleaseManagement (ARM)!

The digital landscape is transforming before our eyes, and ARM is at its forefront.

Discover how @advisedskills breaks it all down in our latest article.

Dive in now and be part of the revolution! 🌐 https://www.advisedskills.com/about/news/393-the-role-of-agile-release-management-in-continuous-delivery

[cinamun]

100% Certainty | Next

[pjs-everyday]

“can we leave now” lookin’ ass lmao >> read below to see how he got THE hero gala fit ❤️‍🔥

lol The Bakugo’s adopted this 30 yr old man just to dress him up 🤓❤️‍🔥

[beezter]

some random sketches. the brainrot only gets worse now that i have to wait between episodes