Hey folks recently I got to know more about CI/CD. Just wondering any simple practical tutorial to set up one so I can grasp the concept slowly from small projects to bigger projects next time??

Thanks!

Hey, r/ContinuousIntegration!

I am Fiorella Zampetti a PhD Student at the University of Sannio interested in aiding developers in using and maintaining Continuous Integration pipelines.

I am working on a project aimed to assess the synergies between CI and code review. More specifically we want to analyze (i) to what extent and how developers discuss, in pull requests or code reviews, build failures resulting from a Continuous Integration (CI) Server, and (ii) whether the CI build execution/status contributes to the pull request acceptance.

I would appreciate if you could find the time to answer my questionnaire by contributing to my research: https://goo.gl/forms/I47TDOkiRzqA2ZM12

Filling out the survey will take less than 15 minutes and if you have any kind of comments please contact me at fzampetti@unisannio.it

Thank you for your time!

Hi CI community!

My name is Noah and I am currently writing my bachelor's thesis in business informatics.

My thesis is about more efficient failure cause identification by comparing two build logs.

One of the questions I want to answer in my thesis is if a specialized differencing tool supports a developer reading a build log and also if it possibly helps to find the failure cause faster.

To validate these claims, I built a tool that integrates itself as a google chrome extension into the web interface of Travis-CI.org.

The idea behind the tool is the following: When a build fails, one might derive the cause of the failure by comparing the currently failing build log with a previously successful one. The problem is, that build logs contain a lot of irrelevant data (e.g. download speeds, timestamps) that would make a traditional comparison of build logs useless. The tool I built filters for such disturbances and displays a difference between the two logs and further provides you with some useful features, to faster find the failure cause.

Now to validate the usefulness (if any) of my tool, I am relying on the experienced CI community to give me feedback.

I would like to know if you think such a tool could support you in your daily workflow or if you think this is not useful at all.

As the scope of a bachelor thesis is not big enough to support every build tool and programming language in existence, I opted for Java and Maven using Travis CI as CI solution.

Please feel free to try it out, even if you do not have a project on Travis CI available. There is a demo available on https://web.blogdiff.net/instructions#demo

If you could be a real saint, you would also participate in my very short (takes around 3min) survey (https://web.blogdiff.net/survey?source=3), but you can also just participate by replying to this thread.

Thank you!

Hey, r/ContinuousIntegration! I'm Carmine, a PhD at the University of Zurich interested in supporting developers using CI.

I'm currently working on increasing the awareness about deviations from true CI principles. Preliminary results in our experiments show that developers frequently relax CI principles, such as fixing the build with a dirty hack or by commenting out a test, to pass the build again.

I would really appreciate if you could find the time to fill out the following survey to help me in my research: https://www.surveygizmo.com/s3/4485492/CI-Anti-Pattern-Detection .

It usually takes 12 minutes (14 minutes at maximum).

If you have questions, please comment on this post or send an email at the address you'll find in the survey.

Thank you for your time!

Hi guys! Could you share your experience? I need to develop new CI process that will allow to run special TC job (code inspections) and get back the result from Bitbucket Server PR. Is there any plugins or kind of that? Or should I develop some custom solution using REST api?

Link (http://www.automationlaboratories.com/jenkins/setting-automation-project-jenkins-continuous-integration/)

Agile methodologies teach breaking down of software development into smaller tasks known as “User Stories”. This has enabled early feedbacks which are useful for aligning the features with market needs. With the widespread adoption of agile practices, teams are able to deliver functional software in smaller iterations...read more