Add Row
Add Element
cropper
update

[Company Name]

Agility Engineers
update
Add Element
  • Home
  • Categories
    • SAFe
    • Agile
    • DevOps
    • Product Management
    • LeSS
    • Scaling Frameworks
    • Scrum Masters
    • Product Owners
    • Developers
    • Testing
    • Agile Roles
    • Agile Testing
    • SRE
    • OKRs
    • Agile Coaching
    • OCM
    • Transformations
    • Agile Training
    • Cultural Foundations
    • Case Studies
    • Metrics That Matter
    • Agile-DevOps Synergy
    • Leadership Spotlights
    • Team Playbooks
    • Agile - vs - Traditional
Welcome To Our Blog!
Click Subscribe To Get Access To The Industries Latest Tips, Trends And Special Offers.
  • All Posts
  • Agile Training
  • SAFe
  • Agile
  • DevOps
  • Product Management
  • Agile Roles
  • Agile Testing
  • SRE
  • OKRs
  • Agile Coaching
  • OCM
  • Transformations
  • Testing
  • Developers
  • Product Owners
  • Scrum Masters
  • Scaling Frameworks
  • LeSS
  • Cultural Foundations
  • Case Studies
  • Metrics That Matter
  • Agile-DevOps Synergy
  • Leadership Spotlights
  • Team Playbooks
  • Agile - vs - Traditional
October 29.2025
2 Minutes Read

Discover How Variable-Sharing Transforms Bitbucket CI/CD Workflows

Abstract vector art of coding window and circuit: variable-sharing in Bitbucket Pipelines.

Enhancing Workflow Flexibility with Atlassian's New Feature

Atlassian has introduced a significant improvement to its Bitbucket Pipelines: the ability to share variables between parent and child pipelines. This change addresses a major pain point for development teams, allowing for a more sophisticated orchestration of workflows. Previously, while users could trigger child pipelines from a parent step, passing information seamlessly was a challenge. The new variable-sharing feature bridges this gap, enabling developers to define variables in the parent pipeline and pass them directly to child pipelines.

Understanding the New Variable-Sharing Mechanism

With the introduction of this feature, users can easily define an input-variables section in their pipeline YAML file. For example:

pipelines: custom: a-parent-pipeline: - variables: - name: parent_pipeline_variable default: "value_1" allowed-values: - "value_1" - "value_2" - step: name: 'Child pipeline' type: pipeline custom: a-child-pipeline input-variables: var_1: $parent_pipeline_variable var_2: $repository_variable_name

This structured approach makes pipelines not only more efficient but also more maintainable, allowing teams to organize tasks in a parallel and modular manner.

Key Benefits of the New Feature

  • Efficiency: Share up to 20 variables between a parent and child pipeline to streamline operations.
  • Security Considerations: While it's crucial to understand that these variables should not include sensitive data, as they will be logged in plaintext, the design prioritizes a safer workflow without compromising on flexibility.
  • Modular Pipelines: This modular structure allows independent running of child pipelines, reducing total build times and enhancing overall efficiency.

Setting Up Parent/Child Pipelines

To implement this feature, developers must follow basic steps to configure their Bitbucket repository effectively. First, define child pipelines in their bitbucket-pipelines.yml files clearly, ensuring they are named descriptively, such as my-child-pipeline. From there, reference the child pipeline in the parent pipeline, instructing Bitbucket to execute it at the designated point in the process.

Conclusion: Unlock the Full Potential of Your CI/CD Workflows

This upgrade from Atlassian is set to transform how teams manage their CI/CD processes within Bitbucket, boosting productivity and streamlining workflows. Embrace the transition to more flexible and modular pipeline configurations. For teams looking to optimize their processes or those just starting, exploring the benefits of this new variable-sharing feature is essential.

Team Playbooks

50 Views

0 Comments

Write A Comment

*
*
Related Posts All Posts
01.18.2026

Unlocking Team Productivity: How AI Can Go Beyond Hype in Tech

Update Turning AI Hype into Reality: The Quest for Productivity The ongoing buzz surrounding artificial intelligence (AI) presents tech leaders with a paradox. While AI has the potential to redefine productivity, groundbreaking innovations often fall short of expectations. Many teams report feeling overwhelmed by grandiose claims that AI could transform their workflows, leading to forced adoption rather than meaningful integration. By understanding the importance of AI literacy and intentional focus, leaders can harness AI's power to address real challenges within their organizations. Real Productivity Gains: Why AI Needs to Augment, Not Replace AI's promise is tangible—when applied smartly, it can lead to substantial time savings. Atlassian’s research indicates that 68% of developers and 70% of managers claim they save at least 10 hours a week through AI tools. However, the ironical reality shows that these gains often get swallowed by poorly structured workflows, leading many to perceive AI as adding little value. Instead of focusing solely on code-related tasks, tech leaders should explore where bottlenecks exist throughout the entire production cycle and leverage AI as a collaborative asset rather than a mere coding assistant. Simple AI enhancements in coding may not cut through the rampant inefficiencies in team coordination and documentation. The Power of System-Level Improvements To effectively integrate AI, proactive leaders are shifting their focus to organizational friction points that hinder productivity. This includes reconstructing the way teams organize work—utilizing AI to streamline requirements, summarize key meetings, and automate mundane reporting tasks. For instance, the integration of tools such as Jira and Confluence creates a seamless workflow, freeing up developers to focus on more impactful decision-making. Overcoming Information Overload with AI One major challenge teams face today is information overload. Developers often spend a staggering amount of time sifting through fragmented data rather than coding. Organizations can tackle this issue by centralizing knowledge and using AI to manage and surface critical information efficiently. Practical examples, like Atlassian’s use of AI to automate the retrieval of vital data during meetings, can help alleviate frustration and streamline workflows. Leadership and AI Adoption: A Culture of Collaboration AI adoption is fundamentally a leadership challenge. When leaders actively engage with AI and demonstrate its practical applications in their day-to-day work, they set a standard that encourages team members to follow suit. The quantifiable benefits of employee buy-in—such as significant time savings and enhanced work quality—show that a culture that embraces AI fosters shared innovation and creativity. Conclusion: Take Action to Harness AI's Full Potential Transforming AI hype into measurable productivity begins with recognizing AI as a collaborative partner in the development process. Leaders must prioritize fostering an open environment where employees feel empowered to leverage AI, reducing chaos and enhancing both communication and workflow. By doing so, teams can shift from feeling underwhelmed to avoiding friction and creating significant momentum in productivity.

01.17.2026

How AI Transforms Software Engineers into Innovative Product Engineers

Update The Evolution of Software Development: AI's Impact In recent years, the landscape of software development has undergone a radical transformation due to the rise of artificial intelligence (AI). Traditionally, software engineers and product managers carved out distinct roles, with a linear process guiding project development. Engineers focused on coding while product managers translated customer needs into detailed specifications. However, AI has shifted this dynamic, compressing the time it takes to develop a product from idea to implementation, creating what experts now refer to as 'Product Engineering.' Understanding the Role of Product Engineers As development processes become more automated with AI tools, the role of software engineers is evolving from mere coders to Strategic problem-solvers—'Product Engineers.' These professionals no longer just build according to specifications but leverage customer insights to determine what to build, ensuring that features truly meet user needs. According to a recent Atlantic article, the essence of engineering work has transitioned from executing specs to understanding and defining what valuable features look like. This requires a deep comprehension of the problems faced by users. The Importance of Proactive Decision-Making The challenge facing modern software engineers is not just about efficiently shipping code; it’s about knowing what to produce in the first place. AI technologies, like GitHub Copilot and Amazon CodeWhisperer, highlight this new reality by suggesting features based on machine learning models, prompting engineers to navigate complex decisions around implementation and utility. This shift ensures that teams must not only review automated outputs but prioritize customer satisfaction and innovative solutions. Balancing Speed with Quality A critical risk in this new fast-paced, AI-augmented software development ecosystem is the possibility of shipping the wrong features quickly—an error that can be costly. Thus, developers must develop 'taste' and understanding. They need to ask crucial questions such as, "Does this feature adequately address the problem?" Speed becomes an illusion if it does not equate to producing value for holders. AI: Both a Tool and a Challenge Furthermore, quality assurance, testing, and debugging tasks are also being transformed by AI. While AI provides automated assistance in enhancing code quality, developers must be vigilant against potential pitfalls while fostering a collaborative environment that appreciates human creativity and critical thought. As AI takes over some aspects of the development lifecycle, engineers are challenged to redefine their roles—transforming from mere crafters of code to insightful architects of technology that aligns with customer requirements. Conclusion: Embracing a New Future The future of software development lies in a dynamic interplay between human creativity and AI capabilities. Engineers must adapt to these changes while maintaining oversight and understanding of the core problems to solve. As we move forward, embracing this duality will not only elevate product quality but also enhance customer satisfaction in a rapidly evolving digital landscape.

01.16.2026

Unlocking the Power of Atlassian Forge: Design Your Winning App

Update Creating Competitive Edge with Forge Apps The Atlassian Workplace Events team has recently gleaned invaluable insights from a vibrant competition, showcasing the potential for transformative app development using Forge. During the thrilling 2025 F1 season, thousands participated in events that combined excitement, strategy, and teamwork. The success of these competitions inspired a thoughtful endeavor to streamline their organization through innovative technology. Understanding User Needs is Key Successful app design begins with a deep understanding of the users and their needs. The insight to reverse-engineer user requirements to not just create a product but improve user experience is critical. By defining essential abstractions that underpin the app, like competitions and entries, developers can create applications that align with the core activities of their users, ensuring engagement and functionality. Harnessing Entity Scalability for Future Growth Strategizing for scalability is another vital aspect. The foresight to anticipate that each competition might generate around 1,000 entries highlights the need for a robust framework that accommodates growth over time, potentially requiring hundreds of thousands of database entries. This perspective not only contributes to a well-functioning app but also ensures sustainability as the user base expands. The Importance of Platform Constraints Building within clear platform bounds allows developers to mitigate risks and facilitates smoother functionality. By acknowledging inherent constraints such as technical capabilities and limits on invocation, developers can better align their solutions to the platform’s capabilities. This approach not only enhances operational efficiency but also builds a foundation for reliability and user trust. Lessons Learned from Codegeist Competitions The spirit of competition seen in the recent **Codegeist 2025** hackathon—where creativity and practical problem-solving took center stage—serves as a powerful reminder of the significance of real-world applications. Apps like SimpleDesk and Monkey SQL exemplify how Forge can eliminate redundancy and enhance productivity across teams. Their success stories underscore simple yet impactful solutions: a sentiment echoed across winning submissions at previous Codegeist events. The journey of designing a Forge app, like the one aimed at enhancing workplace competition, highlights the blend of creativity, strategy, and technical acumen required in the agile development landscape. Embracing user feedback, scaling wisely, and understanding platform capabilities are stepping stones toward evolving functional and innovative applications that meet the pressing needs of today’s dynamic work environments. Start Building Your Forge App Today! Whether you’re inspired by competition or the need to solve an everyday issue, the limitless potential of Forge invites developers to innovate. Tap into the resources provided by Atlassian and immerse yourself in a community eager to exchange ideas and foster growth. Begin your journey of creating apps that resonate and provide significant value in the agile ecosystem!

Terms of Service

Privacy Policy

Core Modal Title

Sorry, no results found

You Might Find These Articles Interesting

T
Please Check Your Email
We Will Be Following Up Shortly
*
*
*