Book Image

Git Version Control Cookbook - Second Edition

By : Kenneth Geisshirt, Emanuele Zattin(EUR), Aske Olsson, Rasmus Voss
Book Image

Git Version Control Cookbook - Second Edition

By: Kenneth Geisshirt, Emanuele Zattin(EUR), Aske Olsson, Rasmus Voss

Overview of this book

Git is one of the most popular tools for versioning. With over 100 practical, self-contained tutorials, this updated version of the bestselling Git Version Control Cookbook examines the common pain points and best practices to help you solve problems related to versioning. Each recipe addresses a specific problem and offers a proven, best-practice solution with insights into how it works. You’ll get started by learning about the Git data model and how it stores files, along with gaining insights on how to commit changes to a database. Using simple commands, you’ll also understand how to navigate through the database. Once you have accustomed yourself to the basics, you’ll explore techniques to configure Git with the help of comprehensive examples and configuration targets. Further into the book, you’ll get up to speed with branches and recovery from mistakes. You’ll also discover the features of Git rebase and how to use regular Git to merge other branches. The later chapters will guide you in exploring Git notes and learning to utilize the update, list, and search commands. Toward the concluding chapters, you’ll focus on repository maintenance, patching, and offline sharing. By the end of this book, you’ll have grasped various tips and tricks, and have a practical understanding of best-practice solutions for common problems related to versioning.
Table of Contents (19 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Using GitHub to authenticate at Jenkins


Jenkins is the most popular continuous integration software and it allows users to continuously build, test, and release any kind of software. It is extremely flexible and configurable in every aspect, including the way users are able to log in and authorize. GitHub is able to act as an OAuth provider, which is very convenient since it makes a lot of sense to map the users working on a project with the relative area of the CI system.

 

Getting ready

In order to demonstrate the procedure, we will need a Jenkins instance. Every company will have a different setup so, in order to make things more predictable, we will work with a local version of Jenkins.

Jenkins is a Java app but still, the easiest way to get a running ephemeral instance of Jenkins for our example is by using Docker. With Docker installed and running on your machine, simply run:

$ docker run --rm -p 8080:8080 jenkinsci/blueocean

This instance of Jenkins won't leave behind any traces of itself...