50 research outputs found
Analyzing Gerrit Code Review Parameters with Bicho
Code review is becoming a common practice in large scale software development projects. In the case of free, open source software projects, many of them are selecting Gerrit as the system to support the code review process. Therefore, the analysis of the information produced by Gerrit allows for the detailed tracking of the code review process in those projects. In this paper, we present an approach to retrieve and analyze that information based on extending Bicho, a tool designed to retrieve information from issue tracking systems. The details of the retrieval process, the model used to map code review abstractions to issue tracking abstractions, and the structure of the retrieved information are described in detail. In addition, some results of using this approach in a real world scenario, the OpenStack Gerrit code review system, are presented
Gitana: a SQL-based Git Repository Inspector
International audienceSoftware development projects are notoriously complex and difficult to deal with. Several support tools such as issue tracking, code review and Source Control Management (SCM) systems have been introduced in the past decades to ease development activities. While such tools efficiently track the evolution of a given aspect of the project (e.g., bug reports), they provide just a partial view of the project and often lack of advanced querying mechanisms limiting themselves to command line or simple GUI support. This is particularly true for projects that rely on Git, the most popular SCM system today. In this paper, we propose a conceptual schema for Git and an approach that, given a Git repository, exports its data to a relational database in order to (1) promote data integration with other existing SCM tools and (2) enable writing queries on Git data using standard SQL syntax. To ensure efficiency, our approach comes with an incremental propagation mechanism that refreshes the database content with the latest modifications. We have implemented our approach in Gitana, an open-source tool available on GitHub
Metrics for Gerrit code reviews
Code reviews are a widely accepted best practice in modern software development. To enable easier and more agile code reviews, tools like Gerrit have been developed. Gerrit provides a framework for conducting reviews without physical meetings or mailing lists. In large software projects, tens or even hundreds of code changes are uploaded daily and following the code review process becomes increasingly hard for managers and developers themselves.
To make monitoring the review process easier, this thesis introduces review metrics for Gerrit code review. The metrics can be used, for example, to follow the amount of code changes and how long each activity within the review process take.
The metrics were implemented in a case company and data was collected from few different projects. The metrics were crafted based on measurement goals that were defined after conducting desk research on existing metrics and code review practices and after interviewing developers and managers.
The most notable benefits of the metrics are the ability to recognize the most time consuming areas of Gerrit code reviews and the simplicity to monitor the total amount of open changes. The review and code change quality can also be measured with the metrics by calculating the amount of positive and negative reviews given and received by developers.
By collecting data with the metrics new best practices for Gerrit code reviews can be established. With the help of the metrics, weaknesses are identified and the process can be optimized. Metrics can also be used to motivate developers for better performance when the metrics are publicly available for developers to see their own performance
Recommended from our members
Improving the quality of bug data in software repositories
This thesis was submitted for the award of Doctor of Philosophy and was awarded by Brunel University London.Context : Researchers have increasingly recognised the benefit of mining software repositories
to extract information. Thus, integrating a version control tool (VC tool) and bug tracking
tool (BT tool) in mining software repositories as well as synchronising missing bug tracking
data (BT data) and version control log (VC log) becomes of paramount importance, in order
to improve the quality of bug data in software repositories. In this way, researchers can do
good quality research for software project benefit especially in open source software projects
where information is limited in distributed development. Thus, shared data to track the issues
of the project are not common. BT data often appears not to be mirrored when considering
what developers logged as their actions, resulting in reduced traceability of defects in the
development logs (VC logs). VC system (Version control system) data can be enhanced with data from bug tracking system (BT system), because VC logs reports about past software development activities.
When these VC logs and BT data are used together, researchers can have a more complete
picture of a bug’s life cycle, evolution and maintenance. However, current BT system and
VC systems provide insufficient support for cross-analysis of both V Clogs and BT data for
researchers in empirical software engineering research: prediction of software faults, software
reliability, traceability, software quality, effort and cost estimation, bug prediction, and bug
fixing.
Aims and objectives: The aim of the thesis is to design and implement a tool chain to
support the integration of a VC tool and a BT tool, as well as to synchronise the missing VC
logs and BT data of open-source software projects automatically. The syncing process, using
Bicho (BT tool) and CVSAnalY (VC tool), will be demonstrated and evaluated on a sample
of 344 open source software (OSS) projects.
Method: The tool chain was implemented and its performance evaluated semi-automatically.
The SZZ algorithm approach was used to detect and trace BT data and VC logs. In its formulation, the algorithm looks for the terms "Bugs," or "Fixed" (case-insensitive) along with the ’#’ sign, that shows the ID of a bug in the VC system and BT system respectively. In i addition, the SZZ algorithm was dissected in its formulation and precision and recall analysed for the use of “fix”, “bug” or “# + digit” (e.g., #1234), was detected was detected when tracking possible bug IDs from the VC logs of the sample OSS projects.
Results: The results of this analysis indicate that use of “# + digit” (e.g., #1234) is more
precise for bug traceability than the use of the “bug” and “fix” keywords. Such keywords are
indeed present in the VC logs, but they are less useful when trying to connect the development
actions with the bug traces – that is, their recall is high. Overall, the results indicate that
VC log and BT data retrieved and stored by automatic tools can be tracked and recovered
with better accuracy using only a part of the SZZ algorithm. In addition, the results indicate
80-95% of all the missing BT data and VC logs for the 344 OSS projects has been synchronised
into Bicho and CVSAnalY database respectively.
Conclusion: The presented tool chain will eliminate and avoid repetitive activities in
traceability tasks, as well as software maintenance and evolution. This thesis provides a
solution towards the automation and traceability of BT data of software projects (in particular,
OSS projects) using VC logs to complement and track missing bug data.
Synchronising involves completing the missing data of bug repositories with the logs de
tailing the actions of developers. Synchronising benefit various branches of empirical software
engineering research: prediction of software faults, software reliability, traceability, software
quality, effort and cost estimation, bug prediction ,and bug fixing
Scientific Opinion addressing the state of the science on risk assessment of plant protection products for in-soil organisms
Following a request from EFSA, the Panel on Plant Protection Products and their Residues developed an opinion on the science behind the risk assessment of plant protection products for in-soil organisms. The current risk assessment scheme is reviewed, taking into account new regulatory frameworks and scientific developments. Proposals are made for specific protection goals for in-soil organisms being key drivers for relevant ecosystem services in agricultural landscapes such as nutrient cycling, soil structure, pest control and biodiversity. Considering the time-scales and biological processes related to the dispersal of the majority of in-soil organisms compared to terrestrial non-target arthropods living above soil, the Panel proposes that in-soil environmental risk assessments are made at in- and off-field scale considering field boundary levels. A new testing strategy which takes into account the relevant exposure routes for in-soil organisms and the potential direct and indirect effects is proposed. In order to address species recovery and long-term impacts of PPPs, the use of population models is also proposed
METROPOLITAN ENCHANTMENT AND DISENCHANTMENT. METROPOLITAN ANTHROPOLOGY FOR THE CONTEMPORARY LIVING MAP CONSTRUCTION
We can no longer interpret the contemporary metropolis as we did in the last century. The thought of civil economy regarding the contemporary Metropolis conflicts more or less radically with the merely acquisitive dimension of the behaviour of its citizens. What is needed is therefore a new capacity for
imagining the economic-productive future of the city: hybrid social enterprises, economically sustainable, structured and capable of using technologies, could be a solution for producing value and distributing it fairly and inclusively.
Metropolitan Urbanity is another issue to establish. Metropolis needs new spaces where inclusion can occur, and where a repository of the imagery can be recreated. What is the ontology behind the technique of metropolitan planning and management, its vision and its symbols? Competitiveness,
speed, and meritocracy are political words, not technical ones. Metropolitan Urbanity is the characteristic of a polis that expresses itself in its public places. Today, however, public places are private ones that are destined for public use. The Common Good has always had a space of representation in the city, which was the public space. Today, the Green-Grey Infrastructure is the metropolitan city's monument that communicates a value for future generations and must therefore be recognised and imagined; it is the production of the metropolitan symbolic imagery, the new magic of the city
Cervantes y los mares
En este Cervantes y los Mares, se encuentra el lector con la magistral narrativa de viajes y marítima que Cervantes desarrolló en su Persiles, terminado poco antes de morir. Encuentra asimismo el estudio de su poesía del mar, el modo como reescribió a la vez la antigua novela bizantina junto con el barroco de su tiempo, las retóricas del amor, las artes de la escena y las visuales. Y todo ello, en la voz de sus habilísimos narradores. Aquí, podrá también ahondar en la presencia de la ciudad de Lisboa y de sus gentes en la obra de Cervantes, en tiempos de Felipe II, cuando Portugal fue parte de la monarquía Española, acercarse a las relaciones entre la Península Ibérica y el Mediterráneo y a la dolorida historia de los Cautivos. Y, por fin, conocer las «tierras de promisión» soñadas por aquellos nuestros antepasados
En los 400 años del «Persiles». In memoriam José María Casasayas
UID/HIS/04666/2019
UID/HIS/04666/2013En este Cervantes y los Mares, se encuentra el lector con la magistral narrativa de viajes y marítima que Cervantes desarrolló en su Persiles, terminado poco antes de morir. Encuentra asimismo el estudio de su poesía del mar, el modo como reescribió a la vez la antigua novela bizantina junto con el barroco de su tiempo, las retóricas del amor, las artes de la escena y las visuales. Y todo ello, en la voz de sus habilísimos narradores. Aquí, podrá también ahondar en la presencia de la ciudad de Lisboa y de sus gentes en la obra de Cervantes, en tiempos de Felipe II, cuando Portugal fue parte de la monarquía Española, acercarse a las relaciones entre la Península Ibérica y el Mediterráneo y a la dolorida historia de los Cautivos. Y, por fin, conocer las «tierras de promisión» soñadas por aquellos nuestros antepasadospublishersversionpublishe