Academic literature on the topic 'GitLab'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'GitLab.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "GitLab"

1

Arefeen, Mohammed Shamsul, and Michael Schiller. "Continuous Integration Using Gitlab." Undergraduate Research in Natural and Clinical Science and Technology (URNCST) Journal 3, no. 8 (September 11, 2019): 1–6. http://dx.doi.org/10.26685/urncst.152.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Burr, Chris, and Ben Couturier. "A gateway between GitLab CI and DIRAC." EPJ Web of Conferences 245 (2020): 05026. http://dx.doi.org/10.1051/epjconf/202024505026.

Full text
Abstract:
GitLab’s Continuous Integration has proven to be an efficient tool to manage the lifecycle of experimental software. This has sparked interest in uses that exceed simple unit tests, and therefore require more resources, such as production data configuration and physics data analysis. The default GitLab CI runner software is not appropriate for such tasks, and we show that it is possible to use the GitLab API and modern container orchestration technologies to build a custom CI runner that integrates with DIRAC, the middleware used by the LHCb experiment to run its job on the Worldwide LHC Computing Grid. This system allows for excellent utilisation of computing resources while also providing additional flexibility for defining jobs and providing authentication.
APA, Harvard, Vancouver, ISO, and other styles
3

Kaczmarek, Paweł. "GitLab - NARZĘDZIE ZESPOŁOWEJ PRACY PROGRAMISTÓW." ELEKTRONIKA - KONSTRUKCJE, TECHNOLOGIE, ZASTOSOWANIA 1, no. 6 (June 5, 2019): 27–30. http://dx.doi.org/10.15199/13.2019.6.5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

de Lannoy, Carlos, Judith Risse, and Dick de Ridder. "poreTally: run and publish de novo nanopore assembler benchmarks." Bioinformatics 35, no. 15 (December 24, 2018): 2663–64. http://dx.doi.org/10.1093/bioinformatics/bty1045.

Full text
Abstract:
Abstract Summary Nanopore sequencing is a novel development in nucleic acid analysis. As such, nanopore-sequencing hardware and software are updated frequently and extensively, which quickly renders peer-reviewed publications on analysis pipeline benchmarking efforts outdated. To provide the user community with a faster, more flexible alternative to peer-reviewed benchmark papers for de novo assembly tool performance we constructed poreTally, a comprehensive benchmarking tool. poreTally automatically assembles a given read set using several often-used assembly pipelines, analyzes the resulting assemblies for correctness and continuity, and finally generates a quality report, which can immediately be published on Github/Gitlab. Availability and implementation poreTally is available on Github at https://github.com/ cvdelannoy/poreTally, under an MIT license. Supplementary information Supplementary data are available at Bioinformatics online.
APA, Harvard, Vancouver, ISO, and other styles
5

Cuhadar Donszelmann, Tulay, Walter Lampl, and Graeme A. Stewart. "ART ATLAS Release Tester using the Grid." EPJ Web of Conferences 245 (2020): 05015. http://dx.doi.org/10.1051/epjconf/202024505015.

Full text
Abstract:
The ART (ATLAS Release Tester) system is designed to run test jobs on the Grid after a nightly release of the ATLAS offline software has been built. The choice was taken to exploit the Grid as a backend as it offers a huge resource pool, suitable for a deep set of integration tests, and running the tests could be delegated to the highly scalable ATLAS production system (PanDA). The challenge of enabling the Grid as a test environment is met through the use of the CVMFS file system for the software and input data files. Test jobs are submitted to the Grid by the GitLab Continuous Integration (gitlab-ci) system, which itself is triggered at end of a release build. Jobs can be adorned with special headers that inform the system how to run the specific test, allowing many options to be customised. The gitlab-ci system waits for exit status and output files are copied back from the Grid to an EOS area accessible by users. All gitlab-ci jobs run in ART’s virtual machines, using docker images for their ATLAS setup. ART jobs can be tracked by using the PanDA system. ART can also be used to run short test jobs locally. It uses the same ART command-line interface, where the backend is replaced to access a local machine for job submission rather than the Grid. This allows developers to ensure their tests work correctly before adding them to the system. In both the Grid and local machine options, running and result copying are completely parallelized. ART is written in python, complete with its own local and Grid tests to give approximately 90% code coverage of the ART tool itself. ART has been in production for one year and fully replaces and augments the former ATLAS testing system.
APA, Harvard, Vancouver, ISO, and other styles
6

Protasevich, Yu A., O. A. Zmeev, and D. A. Sokolov. "Tools for organizing teachers-students interaction using version control systems." Informatics and education, no. 4 (June 27, 2021): 36–46. http://dx.doi.org/10.32517/0234-0453-2021-36-4-36-46.

Full text
Abstract:
The article describes an approach to organizing the teacher-students interaction in programming courses using the Git version control system. In order to select the most suitable and affordable system for educational needs a comparative analysis of different Git repository management systems was carried out. Based on the experience of various educational institutions that use version control systems in their courses, the advantages and disadvantages of using these systems in teaching were identified. Taking into account the existing problems, a software solution was developed based on the GitLab system. As part of this solution, a method is proposed for organizing the work of a teacher and students in disciplines that use version control systems. This approach implies using both GitLab and additional system, which serves as a manager for Git repositories and is designed to facilitate the work of the teacher and administrator by automating the tasks they perform. The main purpose of the article is a detailed description of this approach: limiting permissions to both teachers and students, GitLab organization and functionality, a list of use cases for each user. The article also presents common workflows of the additional system, its main entities and their relationships and an overview of the features that the system provides.
APA, Harvard, Vancouver, ISO, and other styles
7

Сердечный, Алексей Леонидович, Игорь Васильевич Герасимов, Олег Юрьевич Макаров, Юрий Геннадьевич Пастернак, Николай Михайлович Тихомиров, Андрей Олегович Калашников, and Андрей Петрович Преображенский. "THE TECHNOLOGY OF DETECTION INFORMATION ABOUT VULNERABILITY IN THIRD-PARTY OPEN SOURCE SOFTWARE." ИНФОРМАЦИЯ И БЕЗОПАСНОСТЬ, no. 3(-) (December 1, 2020): 347–64. http://dx.doi.org/10.36622/vstu.2020.23.3.003.

Full text
Abstract:
В статье приведены результаты разработки технологии выявления сведений об уязвимостях сторонних компонентов программного обеспечения (ПО), позволяющей своевременно обнаруживать проблемы безопасности, связанные с использованием заимствованных компонентов с открытым исходным кодом. Технология отличается процедурами оперативного обнаружения, ранжирования и подтверждения достоверности первоисточников сообщений о таких проблемах. Разработанная технология основана на проведении сбора и семантического анализа сведений об ошибках и средствах (алгоритмах) эксплуатации уязвимостей ПО, содержащихся в сообщениях, публикуемых на информационных ресурсах разработчиков ПО с открытым исходным кодом. Технология включает процедуру подтверждения сведений о наиболее опасных уязвимостях с последующей оценкой рисков для подтверждённых уязвимостей. В статье также приводятся результаты реализации предлагаемой технологии в виде средства сбора и интерактивного анализа сообщений о ошибках в ПО с открытым исходным кодом, размещаемым на платформах для совместной разработки GitHub и GitLab. Технология выявления сведений об уязвимостях сторонних компонентов позволяет повысить защищённость ПО, использующего в своём составе общедоступные компоненты с открытым исходным кодом. The article presents the results of the development the technology of detection information about vulnerability in third-party open source software, which allows timely detection of security problems associated with the use of borrowed components provided with open source code. The technology is characterized by procedures for rapid detection, ranking, and confirmation of the authenticity sources of primary reports about such problems. The technology is based on collecting and mining information about bugs, vulnerabilities and exploits contained in messages that published in sources of open source software developers. The technology includes a procedure for confirming information about the most dangerous vulnerabilities, followed by a risk assessment for confirmed vulnerabilities. The article also presents the results of implementing the proposed technology as a tool for collecting and interactively analyzing bug messages in open source software hosted on the GitHub and GitLab collaborative version control platforms. The technology for detecting information about vulnerabilities of third-party components allows you to increase the security of software that uses publicly available open source components.
APA, Harvard, Vancouver, ISO, and other styles
8

Kamoun, Choumouss, Julien Roméjon, Henri de Soyres, Apolline Gallois, Elodie Girard, and Philippe Hupé. "biogitflow: development workflow protocols for bioinformatics pipelines with git and GitLab." F1000Research 9 (June 22, 2020): 632. http://dx.doi.org/10.12688/f1000research.24714.1.

Full text
Abstract:
The use of a bioinformatics pipeline as a tool to support diagnostic and theranostic decisions in the healthcare process requires the definition of detailed development workflow guidelines. Therefore, we implemented protocols that describe step-by-step all the command lines and actions that the developers have to follow. Our protocols capitalized on two powerful and widely used tools: git and GitLab. They address two use cases: a nominal mode to develop a new feature in the bioinformatics pipeline and a hotfix mode to correct a bug that occurred in the production environment. The protocols are available as a comprehensive documentation at https://biogitflow.readthedocs.io and the main concepts, steps and principles are presented in this report.
APA, Harvard, Vancouver, ISO, and other styles
9

Kamoun, Choumouss, Julien Roméjon, Henri de Soyres, Apolline Gallois, Elodie Girard, and Philippe Hupé. "biogitflow: development workflow protocols for bioinformatics pipelines with git and GitLab." F1000Research 9 (December 8, 2020): 632. http://dx.doi.org/10.12688/f1000research.24714.2.

Full text
Abstract:
The use of a bioinformatics pipeline as a tool to support diagnostic and theranostic decisions in the healthcare process requires the definition of detailed development workflow guidelines. Therefore, we implemented protocols that describe step-by-step all the command lines and actions that the developers have to follow. Our protocols capitalized on two powerful and widely used tools: git and GitLab. They address two use cases: a nominal mode to develop a new feature in the bioinformatics pipeline and a hotfix mode to correct a bug that occurred in the production environment. The protocols are available as a comprehensive documentation at https://biogitflow.readthedocs.io and the main concepts, steps and principles are presented in this report.
APA, Harvard, Vancouver, ISO, and other styles
10

Kamoun, Choumouss, Julien Roméjon, Henri de Soyres, Apolline Gallois, Elodie Girard, and Philippe Hupé. "biogitflow: development workflow protocols for bioinformatics pipelines with git and GitLab." F1000Research 9 (February 19, 2021): 632. http://dx.doi.org/10.12688/f1000research.24714.3.

Full text
Abstract:
The use of a bioinformatics pipeline as a tool to support diagnostic and theranostic decisions in the healthcare process requires the definition of detailed development workflow guidelines. Therefore, we implemented protocols that describe step-by-step all the command lines and actions that the developers have to follow. Our protocols capitalized on the two powerful and widely used tools git and GitLab, and are based on gitflow, a well-established workflow in the software engineering community. They address two use cases: a nominal mode to develop a new feature in the bioinformatics pipeline and a hotfix mode to correct a bug that occurred in the production environment. The protocols are available as a comprehensive documentation at https://biogitflow.readthedocs.io and the main concepts, steps and principles are presented in this report.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "GitLab"

1

Bergman, Adam. "Automatic Detection of Source Code Plagiarism in Programming Courses." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104883.

Full text
Abstract:
Source code plagiarism is an ongoing problem in programming courses at higher academic institutions. For this reason, different automated source code plagiarism detection tools have been developed. However, they require several manual steps before the submissions can be compared. Linnaeus University uses GitLab to handle their students’ code-related assignments but lacks an integrated workflow for checking submissions against plagiarism. Instead, Linnaeus University’s plagiarism-checking process is done manually, which is a challenging and time-consuming process. This thesis is a case study on Linnaeus University, focusing on integrating one of the plagiarism detection tools with GitLab using Continuous integration pipelines. The objectives have been to collect students’ submissions, communicate with the plagiarism tool, and visually present the results within GitLab. The prototype has been evaluated by a set of manually created submissions with different levels of plagiarism to ensure that the detection tool differentiates plagiarized and non-plagiarized submissions. Teachers at Linnaeus University have tested the workflow and reasoned whether the prototype fulfills their requirements.
APA, Harvard, Vancouver, ISO, and other styles
2

Hamnede, Elisabet. "A new approach for medical device product documentation." Thesis, Mittuniversitetet, Avdelningen för informationssystem och -teknologi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-31055.

Full text
Abstract:
Hardware and software developers rely on different tools for document management, product data management (PDM) and software configuration management (SCM). As more and more products include components of both types there is a growing demand for one collaborative system. This becomes even more critical in the medical sector, where a device is under regulatory demands for document management to even be allowed in to the market. Combined systems become more complex and are generally based on PDM-principles rather than SCM. Current development of SCM tends instead towards simpler systems focused on pure version control (VCS) that are easy to use and economically available to small- and medium sized enterprises (SME), which is not the case with generic PDM-systems or combined systems. This study explored the possibility to extend the usage of such a VCS and include hardware documentation as well as software. The aim was to further our understanding of the SME perspective on product documentation for the medical device field. The method was a case study, collaboration with a SME development company. The scope was to explore possible usage of a chosen VCS (GitLab) and to compare it with a generic PDM-system and with existing manual system. The results showed that for several of the hardware document types there are special made Git-solutions to find within the open source community. However, none of the ones tested in the study was deemed good enough with respect to functionality and reliability. Instead the case study used direct storage of the files in their binary format and focused on testing different VCS functions and on how to organize in order to best gain the advantages of using the system. The conclusions showed that hardware documents can be stored in the same iterative manner as software but with limited Git functionality. Compared with a PDM system GitLab can offer the same level of revision control and communication around the specifications but lacks classification of parts and detailed product structures. GitLab offers better iteration history than both a PDMsystem and the existing manual system does. But not being able to use full Git functionality the organization needs a collaboration strategy to handle the decentralized storage. If the collaboration strategy matches the organization development practices, GitLab is a useful alternative for medical device documentation.
APA, Harvard, Vancouver, ISO, and other styles
3

Alessandrini, Aduer. "'il 730 online' di CAF ACLI e l'introduzione di una cultura DevOps." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2019. http://amslaurea.unibo.it/17699/.

Full text
Abstract:
In questo presente sempre più servizi che caratterizzano il nostro quotidiano (trasporti, utenze, commercio eccetera) stanno avendo una progressiva sostituzione della componente di interazione personale, in favore di una maggiore integrazione con la rete. Basti pensare a come grazie ad una connessione Internet, sia possibile monitorare in tempo reale il ritardo di un treno, o ordinare e ricevere a domicilio un piatto cucinato espressamente o vedere la sbarra del casello autostradale alzarsi perché il sistema ha riconosciuto la targa inserita poco prima tramite l'apposita app. In contesti come questi, in cui un processo che avviene nella realtà, viene monitorato e coordinato dall'utente finale remoto, sul software grava una grande responsabilità. Le software house per stare al passo con questa sfida, ed essere competitive sul mercato, devono produrre sistemi di qualità sempre maggiore, che sappiano dare soluzioni veramente utili agli utenti ed in tempi per loro accettabili. Questo può essere ottenuto adottando necessariamente metodiche di lavoro più sofisticate. L'approccio DevOps in particolare mira ad ottimizzare i processi aziendali che intercorrono tra le varie fasi dello sviluppo di un software, sostituendo le attività manuali con procedure automatizzate capaci di aumentare la velocità, il livello di garanzia e la riproducibilità delle medesime. Il lavoro presentato in questa tesi tratta di come questa metodologia sia stata introdotta nell'occasione dello sviluppo di un sistema di scambio di documenti fiscali commissionato dall'ente di scala nazionale CAF ACLI. L'obiettivo era quello di realizzare un servizio che desse la possibilità di operare senza recarsi presso uno sportello ma garantendo lo stesso livello di assistenza e garanzia del risultato che solo un esperto fiscale può dare. La metodica elaborata ha permesso di raggiungere un'alta qualità del prodotto e rapidità nei rilasci per essere reattivi alle richieste del cliente ed alle segnalazioni di bug.
APA, Harvard, Vancouver, ISO, and other styles
4

Ševčík, Radek. "Aplikace pro obsluhu měřicích zařízení v energetice." Master's thesis, Vysoké učení technické v Brně. Fakulta elektrotechniky a komunikačních technologií, 2019. http://www.nusl.cz/ntk/nusl-400873.

Full text
Abstract:
This thesis is focused on application development with ARM processor architecture and Linux operating system. It uses cloud hosting services to build, test and deploy applications with container-based virtualization. The application communicates with smart meters on serial buses. It stores measurements in a database. It provides access to devices and measurements in internet network.
APA, Harvard, Vancouver, ISO, and other styles
5

Sahlin, Daniel, and Christian Stjernberg. "GitHub Visualizations and their Usefulness for GitHub Users." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-280104.

Full text
Abstract:
The most popular versioning system is undoubtedly Git, for which GitHub with its 40 million users provides a central location at which Git repositories can be discovered and contributed to. With all of the metadata that Git repositories contain, GitHub also holds a significant amount of data in its 44 million repositories which can be accessed freely with the GitHub API. To make use of this data, this report set out to develop and evaluate visualizations of GitHub repositories to find out how well these visualizations help GitHub users understand their projects. The report also tried to determine if there were any specific GitHub metadata that the current tools do not visualize and whether it would be useful to visualize that data. The currently available tools were first gathered in an iterative search process, which yielded three results: GitHub Visualizer by Artem Zubkov, Gource and GitHub Visualizer by Aw Young Qingzhuo. These tools were then evaluated using carefully developed evaluation criteria based on previous research. The report then developed a new tool called GitViz, which visualized more metadata than the current tools, in the form of GitHub issues. GitViz was then subjected to human evaluation so that it could be determined whether it was useful or not. The results showed that while GitViz had some use in providing an overview of the file structure of repositories, there was no apparent practical use for the tool that was significant enough that users would go through the trouble of using it. Furthermore, the addition of GitHub issues did not seem to appeal to the user base. The report concludes that GitHub visualizations have the ability to give a shallow overview of a repository’s commit history and file structure, and that visualizations of other metadata such as issues only appeals to a minimal part of the user base.
Det mest populära versionshanteringssystemet är utan tvekan Git, för vilket GitHub med sina 40 miljoner användare ger en central plats där Git-repos kan utforskas och bidras till. Med all metadata som Git-repos innehåller, har GitHub också en betydande mängd data i sina 44 miljoner repos som kan nås fritt med GitHub API. För att utnyttja denna data har denna rapport utvecklat och utvärderat visualiseringar av GitHub-repos för att ta reda på hur pass väl dessa visualiseringar hjälper GitHub-användare att förstå sina projekt. Rapporten försökte också svara på om det fanns någon specifik GitHub-metadata som de nuvarande verktygen inte visualiserar som det skulle vara användbart att visualisera. De för närvarande tillgängliga verktygen samlades först in i en iterativ sökprocess, som gav tre resultat: GitHub Visualizer av Artem Zubkov, Gource och GitHub Visualizer av Aw Young Qingzhuo. Dessa verktyg utvärderades sedan med hjälp av noggrant utvecklade utvärderingskriterier baserade på tidigare forskning. Rapporten utvecklade sedan ett nytt verktyg som heter GitViz, som visualiserade mer metadata än de nuvarande verktygen, i form av GitHubissues. GitViz utsattes sedan för mänsklig evaluering så att det kunde avgöras om verktyget var användbart eller inte. Resultaten visade att även om GitViz erbjöd viss användbarhet genom att ge en översikt över filstrukturen i repos, fanns det ingen uppenbar praktisk användning för verktyget som var tillräckligt betydande för att användare skulle besvära sig med att använda det. Dessutom verkade tillägget av GitHub-issues inte tilltala användarna. Rapporten kom fram till slutsatsen att GitHub-visualiseringar har förmågan att ge en begränsad överblick över ett repos commit-historik och filstruktur, och att visualiseringar av andra metadata, som till exempel issues, bara tilltalar en minimal del av användarbasen.
APA, Harvard, Vancouver, ISO, and other styles
6

Robertsson, Annika, Cecilia Johansson, and Katja Nilsson. "Lotta och Gittan." Thesis, Halmstad University, School of Teacher Education (LUT), 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-1397.

Full text
Abstract:

Studera hur flickan konstrueras i de

båda barnböckerna för att sedan se hur

dessa speglar sig i 1970-talet respektive

2000-talets samhälles syn på barn. Studiens valda teori är genusvetenskap.

I analysen använder vi

Nikolajevas och Edströms metoder

om barnbokens struktur, dessa är

studiens analysverktyg. Med dessa

metoder tittar vi på flickans

konstruktion i de båda barnböckerna.

Flickans konstruktion i barnböckerna

återspeglas i hur samhällets syn är på

barn då boken är skriven.

Dessutom är det tydligt att flickans

konstruktion har förändrats från

1970-talet ti1l idag.

APA, Harvard, Vancouver, ISO, and other styles
7

Svensson, Linnéa. "Genuskonstruktioner i två bilderböcker : En analys av Pija Lindenbaums Gittan och gråvargarna och Gittan gömmer bort sig." Thesis, Örebro universitet, Institutionen för humaniora, utbildnings- och samhällsvetenskap, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-45429.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Valls, Ramounet. "Le droit coutumier gitan : approche catalane." Perpignan, 2007. http://www.theses.fr/2007PERP0786.

Full text
Abstract:
L'objet de cette étude est de mettre en relief l'originalité du mode de vie gitan catalan, conditionné par les coutumes devant être respectées par toutes les personnes revendiquant leur appartenance à ce peuple. En effet, si à priori l'on aurait pu penser que cette société est organisée de façon anarchique, l'enquête réalisée au sein de ce peuple a permis de démontrer que dans la réalité, tel n'est pas le cas. Les règles que les membres de ce peuple respectent depuis la nuit des temps ont pour objet essentiel de préserver la cohésion culturelle et sociale du groupe. Afin d'étayer cette démonstration, cette thèse est articulée en deux parties : La première partie concerne le droit coutumier intra communautaire, représenté essentiellement par le droit de la famille, ce peuple n'étant composé dans les faits que d'une multitude de familles revendiquant une identité commune. La deuxième partie concerne le droit coutumier régissant les relations sociales extra familiales, représenté, d'une part par leurs relations dans le cadre de leurs professions, d'autre part dans leurs relations avec les institutions, telles que l'éducation nationale ou les institutions démocratiques de ce pays. Ainsi, pourrons- nous apporter une pierre supplémentaire à l'édifice de la tolérance et du respect mutuel
The purpose of this study is to highlight originality of lifestyle gipsy Catalan, conditioned by the customs must be respected by all the people claiming their affiliation to this society. Indeed, if at first glance one would think that this society is organized so anarchic, the survey carried out within this people has demonstrated that in reality, this is not the case. The rules that members of this people respect since the dawn of time have to essential object to preserve the cultural cohesion of the group. To support this demonstration, this thesis is articulated in two parts: The first part concerns the customary law intra Community, represented mainly by the family law, people are composed in the facts that a multitude of families claiming a common identity. The second part is the customary laws governing social relations extra allowance, represented, for in their relations within the framework of their professions, partly in their relations with the institutions, such as education or national democratic institutions of this country. For example, can we make a stone supplementary to the building of tolerance and mutual respect
APA, Harvard, Vancouver, ISO, and other styles
9

Grönlund, Mårten, and Jonathan Jefford-Baker. "Measuring correlation between commit frequency and popularity on GitHub." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-209819.

Full text
Abstract:
This thesis studies the correlation between the commit frequency and popularity of Github projects. Over 12 000 projects were retrieved using the Github API, resulting in a dataset containing 85 projects after filtering out projects that were deemed unfit. The analysis of the projects consisted of calculating the Pearson Correlation Coefficient using the frequency of commits and popularity as variables. Different time intervals were studied along with several metrics of popularity based upon the project’s metadata retrieved from Github. The results varied for the different time intervals and metrics of popularity but none of the measurements resulted in a correlation coefficient which indicated a strong or moderate correlation. Therefore this study reached the conclusion of no existing correlation between commit frequency and popularity. Although no correlation was found, several potential measures of improvement for further research were discovered.
Denna studie undersöker korrelationen mellan frekvensen av commits och popularitet hos Github projekt. Över 12 000 projekt utvanns genom Github API:et vilket resulterade i en datamängd innehållandes 85 projekt efter att gallringen av oönskade projekt ägt rum. Analysen av projekten bestod av att beräkna Pearsons korrelationskoefficient med frekvensen av commits och popularitet som variabler. Baserat på projektens metadata från Github undersöktes olika tidsintervall kombinerat med flera mått på popularitet. Resultaten varierade för de olika tidsintervallen och popularitetsmåtten men ingen av mätningarna resulterade i en korrelationskoefficient som indikerade en stark eller medelstark korrelation. Således fastställde denna studie slutsatsen att ingen korrelation existerade mellan frekvensen av commits och popularitet. Trots att ingen korrelation hittades, upptäcktes däremot flera potentiella förbättringsåtgärder för vidare forskning
APA, Harvard, Vancouver, ISO, and other styles
10

Glittum, Marius Nedal, and Even Stene. "Promoting reflection in agile software development teams using GitHub data." Thesis, Norges teknisk-naturvitenskapelige universitet, Institutt for datateknikk og informasjonsvitenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-23231.

Full text
Abstract:
Agile software development teams work with several different artifacts ona daily basis, and by interacting with these artifacts users are involvedin work related experiences. By revisiting these experiences and reflectingupon them, users can evaluate and improve how they solve everyday workingtasks. Boud et.al defines reflection as a process where the experience is revis-ited, feelings are re-attended and the experience is re-evaluated[Boud et al.,1985]. Furthermore work and reflection on work are shown to be stronglyconnected[Schön, 1983][Chaiklin and Lave, 1993]. Reflecting on work ex-periences give a better understanding of the experience itself, allowing forconclusions and lessons learned to be made. Reflection transforms experi-ence into knowledge which can be applied to solve challenges in the everydayworking environment.The main focus of this thesis was to develop a technological tool to collectproject artifacts and connect these to work experiences, in order to enhancereflection both individually and collaboratively in agile software developmentteams. The tool was developed using a daily delivery cycle. Design choiceswere made on the basis of available theory, literature and related tools con-cerning reflection and agile development. Three evaluations were conducted;A usability study, an expert review with an expert in the field of agile soft-ware development and a focus group evaluation consisting of eight softwaredevelopers working in an agile team.The work conducted resulted in a Grails web-application, where usersconnect their daily experiences with project artifacts collected from a Version-control system. These daily reflection notes can be used both individuallyand collaboratively in a team as preparation for agile retrospective sessions.The tool continuously collects work-related project artifacts and presentsthese in order for users to revisit their work that day. The application aimsto trigger reflection on user experiences and storing the outcome in notes forlater use and sharing.This thesis, the developed tool and its evaluation contributes with an in-creased understanding of how reflection in agile software development teamscan be improved, by connecting experiences with work related project arti-facts.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "GitLab"

1

Thottakara, Augustine. The Gita and the Gitas. Bangalore: Published by Dharmaram Publications for Jeevass Publications, Aluva, 2014.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Steinert, Marlis G. Gitler. Moskva: Ėterna, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gitlin, Michael. Michael Gitlin. Mannheim: Die Kunsthalle, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Pervushin, Anton. Okkulʹtnyi Gitler. Moskva: I︠A︡uza, 2006.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Vorobʹevskiĭ, I︠U︡riĭ. Neizvestnyĭ Gitler. Moskva: ĖKSMO, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tagore, Rabindranath. Gitali =: (song lyrics). Dhaka: University Press, 1985.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Haack, Phil, and Sarah Guthals. GitHub for Dummies. Hoboken, New Jersey, United States of America: John Wiley & Sons, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Tilroe, Anna. De blauwe gitaar. Amsterdam: Querido, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Cherchillʹ i Gitler. Moskva: AST, 2015.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Flamenco gitan. Paris: CNRS, 2008.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "GitLab"

1

Vesselov, Sarrah, and Taurie Davis. "A GitLab Case Study." In Building Design Systems, 111–31. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-4514-9_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Wang, Jing, Xiangxin Meng, Huimin Wang, and Hailong Sun. "An Online Developer Profiling Tool Based on Analysis of GitLab Repositories." In Computer Supported Cooperative Work and Social Computing, 408–17. Singapore: Springer Singapore, 2019. http://dx.doi.org/10.1007/978-981-15-1377-0_32.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ekuban, Audrey Beatrice, Alexander Mikroyannidis, Allan Third, and John Domingue. "Using GitLab Interactions to Predict Student Success When Working as Part of a Team." In Educating Engineers for Future Industrial Revolutions, 127–38. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-68198-2_11.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Chacon, Scott, and Ben Straub. "Github." In Pro Git, 131–80. Berkeley, CA: Apress, 2014. http://dx.doi.org/10.1007/978-1-4842-0076-6_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Kral, Christian. "GitHub-Tutorial." In Modelica - Objektorientierte Modellbildung von Drehfeldmaschinen, 295–317. München: Carl Hanser Verlag GmbH & Co. KG, 2018. http://dx.doi.org/10.3139/9783446457331.007.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tsitoara, Mariot. "GitHub Primer." In Beginning Git and GitHub, 95–104. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5313-7_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Tsitoara, Mariot. "More with GitHub." In Beginning Git and GitHub, 253–67. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5313-7_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Winnie, Doug. "Setting Up GitHub." In Essential Java for AP CompSci, 9–11. Berkeley, CA: Apress, 2021. http://dx.doi.org/10.1007/978-1-4842-6183-5_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Tsitoara, Mariot. "Quick Start with GitHub." In Beginning Git and GitHub, 105–18. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5313-7_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Tsitoara, Mariot. "Git and GitHub Workflow." In Beginning Git and GitHub, 281–84. Berkeley, CA: Apress, 2019. http://dx.doi.org/10.1007/978-1-4842-5313-7_19.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "GitLab"

1

Sommaruga, Lorenzo, and Patrick Ceppi. "PROGRAMMING COURSE TEACHING USING GITLAB." In 10th International Conference on Education and New Learning Technologies. IATED, 2018. http://dx.doi.org/10.21125/edulearn.2018.2286.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Than, Phyu Phyu, and Myat Pwint Phyu. "Continuous integration for Laravel applications with GitLab." In AISS 2019: 2019 International Conference on Advanced Information Science and System. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3373477.3373479.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Vicente, André, and Jorge Bernardino. "Evaluating GitLab, OpenProject, and Redmine using QSOS Methodology." In 15th International Conference on Web Information Systems and Technologies. SCITEPRESS - Science and Technology Publications, 2019. http://dx.doi.org/10.5220/0008364603800387.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Cortes Rios, Julio Cesar, Kamilla Kopec-Harding, Sukru Eraslan, Christopher Page, Robert Haines, Caroline Jay, and Suzanne M. Embury. "A Methodology for Using GitLab for Software Engineering Learning Analytics." In 2019 IEEE/ACM 12th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE). IEEE, 2019. http://dx.doi.org/10.1109/chase.2019.00009.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Vassallo, Carmine, Sebastian Proksch, Anna Jancso, Harald C. Gall, and Massimiliano Di Penta. "Configuration smells in continuous delivery pipelines: a linter and a six-month study on GitLab." In ESEC/FSE '20: 28th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3368089.3409709.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Gorsky, S. A. "Continuous integration, delivery, and deployment for scientific workflows in Orlando Tools." In The International Workshop on Information, Computation, and Control Systems for Distributed Environments. Crossref, 2020. http://dx.doi.org/10.47350/iccs-de.2020.11.

Full text
Abstract:
The paper addresses issues of continuous integration in the development of scientific applications based on workflows (special case of distributed applied software packages) for heterogeneous computing environments. The preparation and carrying out of scientific computational experiments are often accompanied by intensive software modification. Thus, there is a need for the following stages: building, testing, debugging, and installation new versions of software in heterogeneous nodes of environment. These stages may take longer time overheads than computations themselves. The solution to this challenge lies in the use of tools for continuous integration of software. However, such tools require deep integration with the tools for the workflow development because of scientific workflow specifics. To this end, the paper describes the combination of the authors Orlando Tools framework for the development and use packages with the GitLab system that is widely used for continuous integration. Such combination significantly reduces the complexity of software continuous when developing and using packages.
APA, Harvard, Vancouver, ISO, and other styles
7

Johnson, Andrea E. "To GitHub or Not to GitHub?" In SIGCSE '21: The 52nd ACM Technical Symposium on Computer Science Education. New York, NY, USA: ACM, 2021. http://dx.doi.org/10.1145/3408877.3439658.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

López, Rosario, Juan Félix San-Juan, Iván Pérez, and Paula Garcia Ozcoz. "GITHUB AND GITHUB CLASSROOM AS AN EDUCATIONAL RESOURCE." In 12th annual International Conference of Education, Research and Innovation. IATED, 2019. http://dx.doi.org/10.21125/iceri.2019.0657.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Diniz, Joao P., Daniel Cruz, Fabio Ferreira, Cleiton Tavares, and Eduardo Figueiredo. "GitHub Label Embeddings." In 2020 IEEE 20th International Working Conference on Source Code Analysis and Manipulation (SCAM). IEEE, 2020. http://dx.doi.org/10.1109/scam51674.2020.00033.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Bleiel, Nicky. "Collaborating in GitHub." In 2016 IEEE Professional Communication Society (ProComm). IEEE, 2016. http://dx.doi.org/10.1109/ipcc.2016.7740497.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "GitLab"

1

Junghans, Christoph. ASC/NGC Gitlab Tutorial. Office of Scientific and Technical Information (OSTI), June 2016. http://dx.doi.org/10.2172/1257109.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Cooper, A., and P. Hoffman. Working Group GitHub Administration. RFC Editor, August 2020. http://dx.doi.org/10.17487/rfc8875.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Thomson, M., and B. Stark. Working Group GitHub Usage Guidance. RFC Editor, August 2020. http://dx.doi.org/10.17487/rfc8874.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Walker, Alex, Brian MacKenna, Peter Inglesby, Christopher Rentsch, Helen Curtis, Caroline Morton, Jessica Morley, et al. Clinical coding of long COVID in English primary care: a federated analysis of 58 million patient records in situ using OpenSAFELY. OpenSAFELY, 2021. http://dx.doi.org/10.53764/rpt.3917ab5ac5.

Full text
Abstract:
This OpenSAFELY report is a routine update of our peer-review paper published in the British Journal of General Practice on the Clinical coding of long COVID in English primary care: a federated analysis of 58 million patient records in situ using OpenSAFELY. It is a routine update of the analysis described in the paper. The data requires careful interpretation and there are a number of caveats. Please read the full detail about our methods and discussionis and the full analytical methods on this routine report are available on GitHub. OpenSAFELY is a new secure analytics platform for electronic patient records built on behalf of NHS England to deliver urgent academic and operational research during the pandemic. You can read more about OpenSAFELY on our website.
APA, Harvard, Vancouver, ISO, and other styles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography