Capture the Feature Flag

Meinicke, Jens; Hoyos, Juan; Vasilescu, Bogdan; Kästner, Christian

doi:10.1145/3379597.3387463

Cited by 8 publications

(1 citation statement)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Feature flagging, or toggle-driven development, allows teams to turn features on or off selectively (Meinicke et al, 2020). This facilitates phased rollouts and provides a safety net in case of problematic releases.…”

Section: Advanced CD Best Practicesmentioning

confidence: 99%

Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices

Thatikonda

2023

ejtas

View full text Add to dashboard Cite

Continuous Integration and Continuous Deployment (CI/CD) are pivotal in modern software development. Shifting from the classic waterfall models, the current age is dominated by Agile methodologies and DevOps practices. This article explores CI and CD's core principles, differences, and similarities. It touches upon essential techniques such as automation, ensuring consistency, and the importance of quick feedback mechanisms. Beyond these, the discussion extends to cutting-edge methods, infrastructure as code, potential security considerations, and monitoring within CI/CD environments. While CI/CD offers numerous benefits, it's essential to acknowledge its challenges, which necessitate attention and action. With an ever-evolving landscape featuring trends like AI/ML integration into CI/CD, businesses find themselves at a juncture where embracing and finetuning CI/CD is vital for competent software delivery.

show abstract

Section: Advanced CD Best Practicesmentioning

confidence: 99%

Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices

Thatikonda

2023

ejtas

View full text Add to dashboard Cite

show abstract

How the adoption of feature toggles correlates with branch merges and defects in open‐source projects?

2021

View full text Add to dashboard Cite

Branching has been widely adopted in version control to enable collaborative software development. However, the isolation caused by branches may impose challenges on the upcoming merging process. Recently, companies like Google, Microsoft, Facebook, and Spotify, among others, have adopted trunk-based development together with feature toggles. This strategy enables collaboration without the need for isolation through branches, potentially reducing the merging challenges. However, the literature lacks evidence about the benefits and limitations of feature toggles to collaborative software development.Objective/method: In this article, we study the effects of applying feature toggles on 949 open-source projects written in six different programming languages.We first identified the moment in which each project adopted a feature toggles framework. Then, we observed whether the adoption implied significant changes in the frequency or complexity of branch merges and the number of defects, and the average time to fix them. Finally, we compared the obtained results with results obtained from a set of control projects that do not use feature toggles frameworks. Results/conclusion:We could observe a reduction in the average merge effort and an increase in the average total time needed to fix defects after adopting feature toggles frameworks. However, we could not confirm that this increase was influenced by the use of feature toggles.

show abstract

Model to reduce DevOps pipeline execution time using SAST

Saurabh,

Kumar

2024

Int J Syst Assur Eng Manag

View full text Add to dashboard Cite

Static code analysis (SAST is a well-known concept) to identify security aws in the code to improve software product quality. A SAST tool called SonarQube which can scan source code of an application and identify the vulnerabilities present in software. It can also nd the RCA of the vulnerabilities found in software products. it helps in rehabilitating the securities aws found in analysis of the software products. SAST tools analyses upside-down for an application. It does not need s system to be in running state to perform analysis. The scan provides instant feedback to developers in terms of reducing security risks for an application. It helps to resolve issues which was present during development and helps developers to increase their knowledge. As a result, developers become competent about knowledge of security for software product. The sonar analysis report provides on demand access to all recommendations. The user can navigate to line-of-code which have vulnerabilities and they can do faster discovery and auditing. And hence the developers can write more code which is less vulnerable. This way they have more secure and quality product delivered. To conduct static analysis, the author(s) has used SonarQube as a tool, which compile and measure the code quality for the code kept in repositories. As Devops/DevSecOps standards, SonarQube is used to create different pipelines which normally increases the build pipeline execution time. In the proposed solution, the author(s) tried to reduce build pipeline execution time by conducting static analysis early Devops phases. Proposed solution uses GitHub open-source project written in C Sharp.Net language, Azure Devops, dotnet sonar scanner tool and SonarQube to conduct static analysis and testing. The authors(s) tried to enhance the software quality in early Devops phases which will be helpful in reducing the build time and cost.

show abstract

Capture the Feature Flag

Cited by 8 publications

References 10 publications

Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices

Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices

How the adoption of feature toggles correlates with branch merges and defects in open‐source projects?

Model to reduce DevOps pipeline execution time using SAST

Contact Info

Product

Resources

About