Git Tutorial EclipseCon France 2014 - Gerrit Exercise 9 - starting demo gerrit

Jul 30, 20140 likes568 views

This document provides instructions for starting a demo instance of Gerrit locally using a pre-configured demo Gerrit instance. It describes unzipping the Gerrit files, starting the Gerrit server using Java, and contains details about the pre-configured user accounts and URLs for interacting with the local Gerrit demo.

EGit/Gerrit Hands-on training #7:
Starting Demo Gerrit
If you don’t have access to Gerrit at http://git.eclipse.org/r/ you may do the exercises locally
using a pre-configured demo Gerrit instance. This exercise describes how to install and start
that.
Prerequisite
Gerrit requires a Java 7 installation.
Installation
Unzip <stick>/git-tutorial/gerrit/gerrit-2.9rc2.zip
into a folder having no blanks in its path name. This will yield a folder gerrit-2.9rc2
containing a pre-configured Gerrit demo instance already containing the example repository.
Starting Demo Gerrit
● From a command shell cd to the folder gerrit_site.
● run the following command to start the server (Gerrit 2.9 requires Java 7)
$ java -jar bin/gerrit.war daemon -d .
● this starts Gerrit, to stop it again kill the running process using CTRL-C
● if something goes wrong look into the logs folder
● If you have a unix-like shell you can also start and stop gerrit with ./bin/gerrit.sh
start/stop
Configuration

The demo Gerrit has 3 pre-configured user accounts
● admin (Andrew Admin): has administration privileges
● developer01 (A Developer)and developer02 (B Developer): have all except
administrative Gerrit privileges.
The demo Gerrit runs in a developer mode hence no real authentication is required to logon to
the Gerrit WebUI:
● open http://localhost:8080/ in a browser
● to logon, click Become in the top right corner
● Choose one of the preconfigured developer accounts “A Developer” (account
“developer01”) or “B Developer” (account “developer02”)
● The demo instance is configured to not send email as this wouldn’t make much sense if
you are offline.

● Generate the HTTP password for the logged on user at
http://localhost:8080/#settings,http-password
● If you want to use SSH protocol upload your public SSH key at
http://localhost:8080/#settings,ssh-keys
● You can’t register your real email address as the demo instance has disabled email
integration. Simply use your real email address instead. This will work as both demo
users have the Gerrit privilege +2 Forge Committer or Tagger Identity this means the
email address contained in git commits pushed to the server isn’t checked against the
email address of the user logged on to Gerrit.
● If you do the exercises using the local demo Gerrit the URLs for git communication with
Gerrit are:
○ HTTP protocol : http://localhost:8080/egit-training.git
○ if you are using native Git ensure that http_proxy isn’t in your way, you may need
to set $export no_proxy=localhost
○ SSH protocol: ssh://developer01@localhost:29418/egit-training.git
○ Gerrit WebUI is reachable under : http://localhost:8080/

Copyright © 2014 by M. Sohn, S. Lay, S.Zivkov

Git is a system for distributed version control and code management, while GitHub is a web-based hosting service for Git projects. This document provides instructions for configuring Git by setting a username and email through the command line interface, in order to set up a user's first GitHub project. It recommends checking more in-depth documentation if any problems are encountered in the setup process.

Git–SVNAli Servet Donmez

Comp 122 lab 4 lab report and source codepradesigali1

Log4cpp - Updated - to verify modify updatesyosaggregator2

Log4cpp provides a configurable logging framework for C++ applications. It allows developers to log debug messages, errors, and monitor systems. Log4cpp builds on previous logging methods, allowing logging levels and output to files through configuration files. Developers can include log4cpp, initialize loggers for classes, and log debug messages through those loggers. Log4cpp also provides testing utilities and configuration files to control logging output.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 6 - submit a changemsohn

News from EGit - Talk EclipseCon Europe 2014 - Ludwigsburgmsohn

This document summarizes recent updates to the Eclipse EGit and JGit projects. It describes new features added in versions 3.2 through 3.5, including improved interactive rebasing, stash support, push wizards, and team/repository menus. It also outlines planned work for 3.6 such as new ignore functionality and submodule improvements. Finally, it discusses potential integration of logical model and merge support for EMF models using the EMF Compare project.

Cool new stuff in JGit and EGit - Eclipse Democamp Munich 2013-06-12msohn

This document summarizes new features in JGit and EGit, including faster serving of Git repositories using JGit bitmap indexes. It describes using JGit to run a Git daemon, the GitBlit and Gerrit servers which are based on JGit. Bitmap indexes in JGit 3.0 and Gerrit 2.6 allow much faster counting of objects during clone and fetch by pre-computing reachability data in a pack file. Demostrations are shown of bitmap indexing improving performance against the native Git daemon, as well as other new features in EGit like rename detection and improved merging capabilities.

News from Git in Eclipse - EclipseCon 2015 Europemsohn

Git Tutorial EclipseCon France 2014 - Git Exercise 01 - installation and conf...msohn

This document provides instructions for installing and configuring EGit and Gerrit for a hands-on training session. It describes downloading necessary files from a provided USB stick, installing Eclipse and EGit, configuring Gerrit access, and cloning an example project repository for the exercises. The example project contains a simple calculator application and test code that can be run or debugged within Eclipse.

Setting up Git.pptxtapanvyas11

The document provides instructions for setting up Git on Windows. It discusses downloading and installing Git, configuring user information, creating a local Git repository, staging and committing changes, and connecting the local repository to a remote repository on a hosting platform like GitHub. The objectives are to grasp version control concepts, install Git, create and navigate a Git repository history, and connect the local repository to a remote one.

Git intro hands on windows with msysgitGeshan Manandhar

The document discusses how to use the Git version control system on Windows. It explains that Git is a free, open source distributed version control system used by many large projects. It then provides step-by-step instructions for installing Git on Windows using MsysGit, configuring user settings, initializing and preparing a working directory, making commits to a local repository, creating a public repository, pushing and pulling changes between the local and public repositories, using .gitignore files, and some common Git commands.

Gerrit tutorialHarikaReddy115

This document provides an overview and instructions for setting up Gerrit, an open source code review tool integrated with Git. It discusses installing Git on different platforms, configuring Git with username and email, generating SSH keys for authentication with Gerrit, and preparing to work with Gerrit by installing Git-Review. The goal is to help beginners learn the basic functionality of Gerrit and get set up to submit patches for code review.

Everything you didn't know you neededHenry Schreiner

The document describes various productivity tools for Python development, including: - Pre-commit hooks to run checks before committing code - Hot code reloading in Jupyter notebooks using the %load_ext and %autoreload magic commands - Cookiecutter for generating project templates - SSH configuration files and escape sequences for easier remote access - Autojump to quickly navigate frequently visited directories - Terminal tips like command history search and referencing the last argument - Options for tracking Jupyter notebooks with git like stripping outputs or synchronizing notebooks and Python files.

Git & githubMicroPyramid .

Git is a version control system created by Linus Torvalds that allows developers to track changes to files over time through snapshots called commits. GitHub is a hosting service for Git repositories that provides additional features like tracking commit histories and code comparisons. The basic Git workflow involves initializing a repository, adding files, committing changes locally with messages, and pushing commits to a remote repository such as one hosted on GitHub. This allows developers to collaborate by pulling each other's changes and merging code together.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 1 - configure for gerritmsohn

This document discusses configuring a local Git repository to work with Gerrit for code reviews. It explains running the Gerrit configuration wizard to set the target branch, push changes with change IDs in commit messages, and fetch review notes from Gerrit. The wizard is accessed by right-clicking the "Remotes" node for the repository in the Git Repositories view and selecting "Gerrit Configuration..." to set the default configuration values.

EnterpriseLogManagement.pdfManas Mondal

The document outlines steps to implement an enterprise log management architecture using AWS services: 1. Install and configure the CloudWatch Agent on EC2 instances to collect and send logs and metrics to CloudWatch. 2. Use a Lambda function triggered by EventBridge to copy logs from CloudWatch to S3 for long-term storage in a data lake. 3. Analyze the log data stored in S3 using Athena, Glue and Redshift before creating reports and dashboards with QuickSight.

Git and git hub basicsprostackacademy

Os dev tool boxbpowell29a

This document provides instructions for installing various developer tools including Git, Vim, Java, Tomcat, Maven, and Psi Probe on Linux, Mac OSX, and Windows. It then outlines 3 homework assignments: 1) creating a basic Git repository, 2) forking and cloning a provided repository, adding a feature, resolving conflicts, and deploying the application, and 3) using Psi Probe to manage Tomcat web applications. Step-by-step instructions are provided for completing each task along with explanations of commands used.

Github By Nyros DeveloperNyros Technologies

Gerrit Code Review: how to script a plugin with Scala and GroovyLuca Milanesio

This document discusses scripting plugins for Gerrit code review. It describes how plugins can now be written in Groovy or Scala by creating a simple class file and placing it in the plugins directory. This allows defining new SSH commands or REST APIs with just a few lines of code. The document outlines several examples including creating branches, listing projects, and validating commit messages. It announces plans to further develop scripting plugin support at the next Gerrit hackathon with the goal of merging it into the core Gerrit codebase.

git-commands-cheat-sheet-infopediya-com.pdfmurad khan

Git BasicsRyan Condron

This document provides an overview of basic Git commands and workflows. It discusses what Git is, why it's useful for version control and collaboration, and how to install, set up, initialize and commit code to a Git repository. It also covers branching, merging, tagging, forking repositories, and resolving merge conflicts. The document recommends setting up a remote repository on a hosting service like GitHub and pushing and pulling changes between local and remote repositories. It challenges readers to participate in Hacktoberfest and suggests some GUI tools for Git.

Git Memento of basic commandsZakaria Bouazza

Cooking Perl with Chef: Real World Tutorial with JitterbugDavid Golden

A Simple Introduction to GitDaniel Tai

This document provides a simple introduction to Git, a distributed version control system. It explains what version control and distributed version control are. It then covers the basic Git concepts and commands for initializing and cloning repositories, staging and committing files, checking statuses and diffs, and working with remote repositories on GitHub. Key commands discussed include git init, git add, git commit, git status, git diff, git log, git remote add, git push, and git pull. The document encourages hands-on practice on the Try Git tutorial.

Introduction to git and GithubWycliff1

Openstack contribution processSyed Armani

The document outlines the steps to fix a bug in OpenStack code: 1. Set up your development environment by signing the CLA, creating a Launchpad account, adding yourself to the contributors wiki, and requesting membership in the openstack-cla group. 2. Get the source code of the Tempest project from GitHub and configure it using git-review. 3. Create a branch to fix the duplicate lines, commit the change, and submit it for review. The change will be merged once it passes tests and gets two positive reviews and a "+1 Approved" vote from a core reviewer.

OpenStack Contribution Processopenstackindia

The document outlines the steps to fix a bug in OpenStack code: 1. Set up your development environment by signing the CLA, creating a Launchpad account, adding yourself to the contributors wiki, and requesting membership in the openstack-cla group. 2. Get the source code of the Tempest project from GitHub and configure it using git-review. 3. Create a topic branch to remove the duplicate line, commit the change with a descriptive message, and submit it for review. Once submitted, any OpenStack developer can review the change and two +2 reviews are needed for merging, with one additional +1 approval from a core reviewer to trigger automated testing and merging.

Project Gardener - EclipseCon Europe - 2018-10-23msohn

News from Git in Eclipse - EclipseCon EU - 2016-10-26msohn

The document summarizes recent developments in Git and Eclipse tools. It discusses improvements to EGit such as enhanced merge strategies using EMF Compare, improved project import wizards, and usability enhancements. It also covers JGit developments like improved support for hooks, attributes, and large file storage using Git LFS. Finally, it outlines work on distributed versions of JGit using RefTree and Ketch approaches.

More Related Content

More from msohn (20)

Project Gardener - EclipseCon Europe - 2018-10-23msohn

News from Git in Eclipse - EclipseCon EU - 2016-10-26msohn

Git journey from mars to neon EclipseCon North America - 2016-03-08msohn

The document summarizes improvements to the Git and EGit tools over several releases. It describes adding support for hooks, merge strategies, smart project imports, staging views, non-workspace files, date formats, and Gerrit integration in EGit. For JGit, it covers hooks, merge strategies, large file storage (LFS) integration, distributed repositories using RefTree and Ketch, and fixing attributes handling. LFS is explained as a way to efficiently store large binaries outside the main Git repository. Distributed versions of JGit use RefTree to version reference updates and Ketch implements leader election and consensus.

Versioning large binary files with JGit, EGit and Gerritmsohn

Git missiontomars 2015-03-10msohn

The document summarizes recent updates to the JGit and EGit projects. Key updates include improved symlink support, the ability to squash commits in the history view, a new commit graph layout, kerberos authentication, archive command support, editing commits, initializing repositories in non-empty directories, warning when launching if a checkout is running, rebasing with --preserve-merges, improved interactive rebasing and stashing. Future plans include hook and git attribute support, moving to Java 7 and model merging. Security fixes addressed a Git vulnerability on case-sensitive file systems.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 7 - new changescreenmsohn

This document provides instructions for reviewing code changes using the new Gerrit Change Screen. It describes how to switch to the new screen, review source code and commit message changes, comment on specific lines, edit the commit message, navigate between revisions, and vote and publish comments. The new Change Screen was introduced in Gerrit 2.8 and will replace the old screen in version 2.9.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 5 - improve a changemsohn

This document provides instructions for improving a change that did not pass code review by submitting another patch set. It outlines preparing to improve either your own change or someone else's change. The steps include checking out the relevant branch, fetching the latest patch set, making improvements based on reviewer comments, committing the changes with the existing Change-Id, and pushing the new patch set to Gerrit for additional review. Repeating this process allows iterative improvements until the change is approved.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 4 - review changemsohn

This document provides instructions for reviewing code changes in Gerrit. It describes how to review changes directly in the Gerrit UI or by fetching them locally. The key steps are: 1. Find a change to review that was not authored by you. 2. Review each changed file by looking at the side-by-side diffs and adding inline comments. 3. Also review the commit message for clarity. 4. Vote on the change and publish your review comments for the author to consider in improving the change.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 3 - push change to gerritmsohn

This document provides instructions for pushing a code change to Gerrit for review. It describes configuring the local Git repository to push to Gerrit, making a commit with a Change-Id, pushing the change, and then viewing the change in the Gerrit web interface. The pushed change will be the first patch set that can be reviewed by comparing files and checking that the patch set SHA1 matches the local commit.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 2 - fetch the latest statemsohn

Fetching the latest state from the remote repository updates the remote tracking branches in the local repository without changing any local branches or the working tree. This allows developers to base new feature branches on the most up-to-date code from upstream. Developers should fetch changes regularly, especially before starting new features or fixes, to keep their local repositories in sync with the central repository.

Git Tutorial EclipseCon France 2014 - Gerrit Exercise 8 - view gerrit review ...msohn

Git Tutorial EclipseCon France 2014 - Git Exercise 07 - git blamemsohn

Git Tutorial EclipseCon France 2014 - Git Exercise 06 - interactive rebasemsohn

Interactive rebase allows rewriting the local commit history of a branch before sharing it with others. It provides options to edit commit messages, edit or remove commits, change the commit order, or squash commits together. The document demonstrates using interactive rebase to reword a commit message, pick a commit, skip a commit, and squash the last two commits together. Care should be taken not to rewrite published commits that others may have based work on.

Git Tutorial EclipseCon France 2014 - Git Exercise 05 - history viewmsohn

Git Tutorial EclipseCon France 2014 - Git Exercise 04 - merging rebasing and ...msohn

This document provides instructions for merging feature branches, resolving conflicts during merging, and rebasing branches. It explains how to merge two feature branches into the master branch, how to identify and resolve conflicts using merge tools, and how to undo a merge or rebase using reset. It also demonstrates rebasing a feature branch instead of merging and resolving conflicts that arise during rebasing.

Git Tutorial EclipseCon France 2014 - Git Exercise 03 - work on branches in p...msohn

1) The document discusses how to efficiently work on multiple branches in parallel in Git. It presents two methods: using a preliminary commit that can later be amended with additional changes, or using Git's stash feature to temporarily store changes. 2) It walks through an example where the user starts work on a new feature branch, then switches to another branch while temporarily saving their work either by stashing or doing a preliminary commit. 3) When returning to the original branch, the user can continue working and amend their preliminary commit, or apply the stashed changes to continue where they left off.

Git Tutorial EclipseCon France 2014 - Git Exercise 02 - develop a featuremsohn

Code Matters - Eclipse Hackers Git Guide - EclipseCon France 2014msohn

This document provides an overview of using Git and Gerrit for code review at Eclipse projects. It discusses how Eclipse projects have increasingly adopted Git and Gerrit since 2010, with EGit and JGit providing tools to use Git within Eclipse. Gerrit is presented as a code review tool that started at Google and is now used for most Eclipse projects, allowing contributors to push changes for review and committers to accept submitted changes after review. The document concludes with exercises for attendees to try out configuring and using Gerrit for code review of sample projects.

Interactive Rebase with EGitmsohn

EGit 3.0 and beyondmsohn

The document summarizes new features and improvements in recent versions of EGit, the Eclipse Git integration plugin. Key updates include performance improvements and recursive merging in 3.0, a staging view and usability enhancements in 3.1, and wizards for pushing branches and interactive rebasing in 3.2. It also discusses using JGit for faster Git operations and serving repositories, as well as upcoming planned features like merge drivers.