Assignment proposal - scientific paper - #2952
Merged
ericcornelissen merged 1 commit intoAug 31, 2026
Merged
Conversation
Collaborator
|
This looks like an interesting paper for a presentation, looking forward 🙂 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Assignment Proposal
Title
What helped, and what did not? An Evaluation of the Strategies to Improve Continuous Integration
Names and KTH ID
Deadline
Category
Description
The paper 'What helped, and what did not? An Evaluation of the Strategies to Improve Continuous Integration' was published 2021 in ICSE.
When using Continuous Integration, always running every build and test can be expensive and time consuming. This paper evaluates different CI optimizations by comparing 14 variants of 10 techniques for build and test selection and prioritization. It compares these techniques on 100 open-source projects for over 80 000 builds in order to see how well they affect CI cost and time-to-feedback. We will explore these techniques, and discuss which are more effective for improving CI performance.
Relevance
This paper is relevant to DevOps and week 2 since it focuses directly on improving CI pipelines, which is an important part of DevOps. By improving the CI performance, developers can save both time and cost of always building and testing when it may not be necessary.