What is GitLab?

GitLab is a comprehensive DevOps platform that provides a set of tools for software development and lifecycle management. It combines essential features like source code management, continuous integration/continuous deployment (CI/CD), issue tracking, and collaboration into a single application. GitLab is based on Git, a distributed version control system, and supports both public and private repositories.

GitLab is not just a version control tool but an integrated platform that spans the entire software development lifecycle. It supports version control, automated testing, build pipelines, security scanning, and deployment automation, offering a seamless experience for teams working on development, testing, and production environments.

Key Features of GitLab:

• Source Code Management (SCM): GitLab is built on Git, offering tools for managing code repositories, branching, and merging.
• Continuous Integration (CI): GitLab allows you to automate builds, tests, and code deployment with robust CI pipelines.
• Issue Tracking: Built-in issue tracking for project management, enabling teams to prioritize and track tasks effectively.
• Security: Security features like static code analysis and vulnerability scanning help ensure code safety and compliance.
• Collaboration: Supports team collaboration with features like Merge Requests, Code Reviews, and Discussion Threads.

GitLab offers both cloud-hosted and self-hosted deployment options, making it suitable for teams of all sizes, from startups to large enterprises.

What Are the Major Use Cases of GitLab?

GitLab has a wide range of use cases that span the DevOps lifecycle, enabling teams to streamline and automate their workflows. Below are some of the major use cases:

1. Source Code Management (SCM)

• GitLab is primarily used as a source code repository, allowing teams to track changes to code, collaborate on development, and manage versioning. It is based on Git, meaning that it inherits Git’s powerful version control capabilities.
• Example: A development team working on a web application can use GitLab to store their code, manage branches for different features, and merge them into the main project when ready.

2. Continuous Integration and Continuous Deployment (CI/CD)

• CI/CD pipelines are one of the most powerful features of GitLab. They allow developers to automate tasks like testing, building, and deploying their applications, ensuring fast and reliable delivery of new features and bug fixes.
• Example: A team working on a mobile application can use GitLab CI to automatically run unit tests when new code is pushed, build the app, and deploy it to a test environment for further evaluation.

3. Collaboration and Code Review

• GitLab enables collaboration among team members through Merge Requests (MRs) and Code Reviews. These features allow developers to propose changes, receive feedback, and ensure the quality of the code before merging it into the main branch.
• Example: A developer might submit a Merge Request for a feature they’ve developed, and team members will review the code, suggest improvements, and approve or reject the request.

4. Project Management and Issue Tracking

• GitLab includes an integrated issue tracker to help developers manage tasks, report bugs, and prioritize development work. Teams can use Kanban boards and epics to organize and track progress.
• Example: A product team uses GitLab issues to track tasks like implementing new features, fixing bugs, and testing the application.

5. Automated Testing

• GitLab supports automated testing with built-in tools and integrations for unit testing, integration testing, and static code analysis. This ensures that code is tested thoroughly before being deployed.
• Example: GitLab automatically runs unit tests on every commit, ensuring that changes don’t break the application or introduce regressions.

6. Security and Compliance

• GitLab includes features like static application security testing (SAST), dynamic application security testing (DAST), and dependency scanning, which help identify vulnerabilities in code and third-party libraries.
• Example: A development team can set up automated security scans within their GitLab pipeline, ensuring that no vulnerabilities make it to production.

How GitLab Works Along with Architecture?

GitLab works by integrating various features of DevOps into a unified architecture, enabling teams to streamline their workflows. The architecture of GitLab consists of several components that help in code management, automation, deployment, and security.

1. GitLab Architecture Overview

• Web Interface: GitLab provides a web-based user interface where teams can manage repositories, issues, pipelines, and code reviews. This interface allows for easy collaboration and management of development projects.
• GitLab Runner: GitLab Runners are lightweight agents that execute the CI/CD pipelines defined in the .gitlab-ci.yml file. These can be hosted on different machines or virtual environments, depending on your infrastructure.
• Repository Storage: GitLab stores all source code, commit history, and metadata in repositories. This data is typically stored in a PostgreSQL database, and GitLab uses Git to manage versions and branching.
• CI/CD Pipelines: GitLab pipelines are the automated processes that manage the build, test, and deployment workflows. Pipelines consist of jobs, each performing a specific task like testing, building, or deploying the application.
• CI/CD Integrations: GitLab integrates with various tools like Docker, Kubernetes, and AWS, enabling flexible and automated deployment pipelines.

2. GitLab CI/CD Pipeline

• A CI/CD pipeline in GitLab is defined in a .gitlab-ci.yml file, which contains the configuration for how jobs are executed in the pipeline. Each job can have its own script to perform a specific task.
• Example:

stages:

• build
• test
• deploy

build:
stage: build
script:
– echo “Building the application…”

test:
stage: test
script:
– echo “Running tests…”

deploy:
stage: deploy
script:
– echo “Deploying the application…”

3. Version Control with Git

• GitLab leverages Git for managing source code repositories. Developers interact with repositories by cloning, committing, branching, and merging code changes.
• GitLab allows users to create feature branches for new development, with merge requests used to review and merge changes into the main branch.

4. Security and Compliance Features

• GitLab provides integrated security features like Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), Dependency Scanning, and License Compliance to ensure that applications are secure and compliant with industry standards.

What Are the Basic Workflows of GitLab?

GitLab streamlines workflows through automated pipelines, integrated issue tracking, and efficient collaboration tools. Here’s how the basic GitLab workflow looks:

1. Create a GitLab Project

• Developers create a new project in GitLab, which will contain the code repository and all associated files (e.g., .gitlab-ci.yml for pipeline configuration).

2. Clone the Repository

• Once the project is set up, developers clone the repository to their local machines and start working on their code. They make changes, create new branches, and commit them to GitLab.

3. Commit and Push Changes

• Developers work on their feature branches, commit changes, and push them back to GitLab.
• Example:

git add .
git commit -m “Implemented new feature”
git push origin feature-branch

4. Create a Merge Request

• Once the feature is ready, developers create a merge request (MR) to merge their changes from the feature branch into the main branch. This triggers the review process and potential automated tests.

5. Code Review and Testing

• Team members review the changes in the merge request, and GitLab’s CI/CD pipelines automatically run tests on the new code.
• If the tests pass and the code is approved, the merge request is merged into the main branch.

6. Automated Deployment

• After the merge, the CI/CD pipeline automatically deploys the application to a staging or production environment, depending on the configuration.
• Example: GitLab integrates with Kubernetes to automatically deploy the app to a containerized environment.

7. Monitor and Optimize

• After deployment, GitLab’s monitoring tools help track application performance and issues. Teams can access logs, metrics, and error reports to address problems in real-time.

Step-by-Step Getting Started Guide for GitLab

Follow these steps to start using GitLab for version control and CI/CD automation:

Step 1: Sign Up for GitLab

• Create an account on GitLab (https://gitlab.com) or set up a self-hosted instance for your team or organization.

Step 2: Create a New Repository

• After signing in, create a new project in GitLab. Choose whether to make it public or private and initialize it with a README.md file.
• GitLab will generate a repository URL for you to clone to your local machine.

Step 3: Clone the Repository

• Clone the newly created repository using Git:

git clone https://gitlab.com/your-username/your-repository.git

Step 4: Add Code and Commit Changes

• Add your code to the repository, commit it, and push it back to GitLab:

git add .
git commit -m "Initial commit"
git push origin master

Step 5: Set Up CI/CD Pipelines

• Create a .gitlab-ci.yml file in the root of your repository to define your CI/CD pipeline. Define stages such as build, test, and deploy.

Step 6: Create a Merge Request

• Create a new merge request (MR) from your feature branch to the main branch. This triggers code reviews and testing.

Step 7: Deploy and Monitor

• GitLab will automatically deploy your application and monitor it. You can track metrics and logs directly within GitLab.

The post Comprehensive Guide to GitLab: Overview, Use Cases, Architecture, and Getting Started appeared first on scmGalaxy.

Choosing the right source code management solution is no easy task. Even more so when you think about hosting your code behind your own firewall.

This post takes you through this decision – starting with a few common questions.

One of the first questions you’ll need to answer for yourself is: do you have the resources and expertise to professionally manage your code’s on-premises hosting?

1. Is On-Premise Hosting the Right Choice for You?

Any IT department must follow strict security policies. If your organization’s policies require you to keep your code in-house, then of course you will have to deal with hosting your code behind your firewall.

However, self-hosting your code is not a decision you should rush. There is much to keep in mind.

Security:

In an on-premises scenario, your IT department is responsible for setting up a secure environment and installing relevant updates consistently. Keeping a server secure and properly maintained is nothing to be taken lightly.

Availability / Backups:

Today, the code is important to many areas within the company. Therefore its permanent availability is often important. You should make sure that your server has little or no downtime.

Also, note that losing code can be a life-threatening event for many enterprises. You need to provide a completely fail-safe and complete backup strategy in order to make data loss impossible.

Integrations:

Also, think about other systems that need to interact with your code repository. Things like continuous integration servers or issue tracking systems can be other important parts of your software cycle.

Make sure they can be integrated with your code hosting platform – whether it’s behind a firewall or in the cloud.

Budget:

Depending on your needs, the size of your team, and the number of repositories, different solutions come at wildly different prices. This is true for both self-hosted installations and online services. You need to make sure that your own IT department can handle core subjects like security and maintenance flawlessly.

2. Commercial or OpenSource?

As of today, almost all source code hosting options are commercial systems. In fact, the main argument for paying a really high price sometimes is the professional support that it includes. For further updates in case of problems/queries, you can count on the professionals who help you.

If you don’t need these services, you can consider an open-source solution.

3. Complementing Tools

As with most solutions, the actual task of “source code management” is only part of their offering. This makes sense if you consider that today, software development involves a myriad of different tools and workflows – the ones that work best when tightly integrated with one another. Think issue tracking, code reviews, continuous integration systems, etc.

Here is the list of Top 10 Website to Host Git Repository Online:

1. Amazon AWS CodeCommit:

Amazon’s AWS platform includes hosting for Git repositories. It also comes with features that facilitate collaboration, such as code review and access control.

AWS CodeCommit is a secure, highly scalable, managed source control service that hosts private Git repositories. It makes it easy for teams to collaborate on code securely, including encrypted contributions in transit and at rest. CodeCommit eliminates the need for you to manage your own source control system or worry about scaling up its infrastructure. You can use CodeCommit to store anything from code to binaries. It supports the standard functionality of Git, so it works seamlessly with your existing Git-based tools.

Benefits:

• Fully managed
• Secure
• High availability
• Faster development lifecycle
• Use your existing tools
• Collaborate on code

2. Assembla:

Assembla has a long history in the business with its Subversion hosting. It includes a “workspace” platform with issue management, time tracking, and collaboration tools such as Wiki and its own messaging system.

It is a source code management tool that specializes in providing cloud-based version control services for code projects and agile software development. They provide an additional project management tool for those who use their cloud repositories.

Features:

• Work together with Git merge requests
• Collaboration
• Integrated Issue Tracking
• Security
• Package Management
• Project Management
• Code Analysis

3. Beanstalk:

Being a very lean and reliable service, Beanstalk is a great option for businesses. It provides its own “deployment” infrastructure and integrates well with other tools such as Zendesk, FogBugz, Basecamp, or Lighthouse.

Features:

• Easy-to-use service for deploying.
• Scaling web applications
• Services developed with Java
• Backup / Recovery
• Development Environment
• Testing

4. Bitbucket:

Bitbucket, one of the giants in the industry.

The biggest advantage of Bitbucket Server is certainly that it comes from Atlassian – the company that develops highly popular products like JIRA and Confluence. This is why the integration with these tools (especially JIRA) in BitBucket Server is seamless.

BitBucket Server is an obvious choice if your development toolchain already relies on other Atlassian products like JIRA and Bamboo.

Features:

• Merge Checks.
• Code search
• Git Large File Storage
• Bitbucket Pipelines
• IP whitelisting.

5. Codebase:

One of the few platforms to support Git, Subversion, and Mercurial. Additionally, ticketing, project management, and deployment infrastructure tools are included. The codebase is packed with features to help you manage your code and your project with ease.

Features:

• Repository Hosting
• Exception Tracking
• Time Tracking
• Customizable Permissions
• Complete Developer API
• Powerful Searching & Filtering
• Custom Branding

6. RhodeCode:

Sophisticated code review and approval system including news feed and mention system. With features like LDAP support and IP restrictions, Roadcode seems to be geared for corporate use.

Roadcode allows developers to use not only Git but Mercurial and Subversion for revision control. Feature-wise, the platform offers the most important collaboration features such as code reviews and pull requests – but banks on flexible integration with external tools for both issue tracking and continuous integration.

Features:

• Advanced code reviews.
• Side-by-side diffs.
• Pull requests.
• Inline source code chat.
• Full-text code search and source code indexing.
• Web-based file adding, editing, deletion.

7. SourceForge:

SourceForge is an open-source community resource that is dedicated to helping you succeed as much as possible in open-source projects. We thrive on community collaboration to help make it a premier resource for open-source software development and distribution.

A classic hosting site whose reputation took a turn for the worse in the early 2010s after some shady practices, SourceForge has been under new ownership since 2016 and is determined to restore its good reputation.

Features:

• Unlimited bandwidth for Open Source projects
• Integrated Issue Tracking
• Spambot protection
• Extensive worldwide mirror network
• Download statistics over time, by platform, and by region.
• Analytics is completely free, takes no time to set up.
• Automatic platform detection

8. Perforce Helix:

Perforce has the longest history in source code management of all the companies in this overview. It is mostly known for having an impressive tradition in enterprise code hosting through its own Perforce version control system. Recently, however, the company expanded its offering with its new Helix4Git platform.

Features:

• Security and scalability
• By mirroring work into a Perforce server
• Specific branches and files can be locked

Especially will large companies appreciate the long-term experience Perforce as source code management provider; Enterprises can ensure that is well understood their needs and requirements.

9. GitHub:

GitHub is an increasingly popular programming resource that is used to share the access code. It is a social networking site for programmers that use a large range of companies and organizations’ project management and collaboration.

Undisputed number one in the open-source world is having projects like Ruby on Rails or jQuery hosted on GitHub. Offerings include great code review and collaboration features.

Features:

• Drag and Drop Gist Code.
• Creating a folder via the Web Interface
• Using Git URL Shortener.
• Task Checklist.
• Using Github Command Line Interface.

10. GitLab:

GitLab is a web-based Git repository that offers free open and private repositories, issue-following capabilities, and wikis. This is a full DevOps platform that enables all tasks to professionals from the project planning and source code management, monitoring, and security. It allows teams to collaborate and build better software.

With open-source background, GitLab code provides the perfect platform to develop at a rapid pace for cooperation. The free Community Edition and Enterprise Edition can be installed on your own servers. A hosted offering running on GitLab.com is also available.

Features:

• Offers git repository management.
• Code Reviews
• Issue tracking
• Activity feeds and wikis

GitLab teams product helps increase reducing lifecycle and productivity, which creates value for customers return.

There’s a good chance that one of these solutions is the perfect choice for your requirements.

The post Top 10 Website to Host Git Repository Online appeared first on scmGalaxy.

Benefits of Version Control Software:

The main advantages of using version control software include streamlining the development process, managing the code for multiple projects, and keeping a history of all changes within a code.

A version control software saves all the changes in a repository. So, if developers make a mistake, they can undo it. Also, they can compare the new code with the previous version to resolve their grievance. It can reduce human errors and unintended consequences to a great extent. Very suitable for any web development company around the world.

In addition, it facilitates the management of the project’s centralized repository, file storage, documents, and other information related to the project.

Here is the list of Top 4 git version control software in cloud:

1. GitHUb

GitHub helps software teams collaborate and maintain a full history of code changes. You can track changes in the code, turn back the clock to undo errors, and share your efforts with other team members.

It is a repository for host Git projects. For those wondering what is Git? It is an open-source version control system with local branching, multiple workflows, and convenient staging areas. Git version control is an easy-to-learn alternative and provides faster operation speeds.

Features:

• Drag and Drop Gist Code.
• Creating a folder via the Web Interface.
• Using Github Command Line Interface.
• Linking Lines.

2. GitLab

GitLab comes with a number of useful features such as an integrated project, a project website, etc. By using GitLab’s continuous integration (CI) capabilities, you can test and distribute code automatically.

You can access all aspects of a project, view the code, receive requests and add conflict resolution.

This version control software is designed for the DevOps lifecycle. Meaning, your projects are quite complex and involve cloud engineering and the like. Gitlab provides basic features such as view code, pull requests, and merge resolution.

• Development.
• Security.
• Ops teams collaborate
• Build software
• Reduce development costs

4. Beanstalk

Beanstalk is a perfect choice for those who need to work from remote locations. This software is based on browser and cloud, which allows users to code, commit, review and deploy using the browser.

It allows users to code, commit, review, and deploy code using the browser. For its ease of use, you can integrate it with any messaging or email platform for efficient collaboration.

It can be integrated with messaging and email platforms for efficient collaboration regarding code and updates. It supports both Git and SVN and also comes with built-in analytics features. For security, it takes advantage of encryption, two-factor authentication, and password protection functions.

Features:

• Variety of Application Deployment Options.
• Wide Selection of Application Platforms.
• Management and Updates.
• Customization
• Scaling
• Compliance

4. HelixCore

Helix is one of the best version control systems. It provides an integrated platform for collaborative development and protection of intellectual property of any kind. It benefits from several new capabilities, support for both distributed and centralized development workflows. Helix also provides a complete Git ecosystem. And it comes in both on-premises and cloud versions.

Helixcore provides seamless team collaboration and support for both centralized and distributed development workflows. It is available for both cloud and on-premises deployments, which makes it scalable.

Features:

• Work order management
• Applications Management
• Document Management
• Access Controls
• Procurement Management

5. Apache Subversion

Apache Subversion is another open-source version control system, founded a few decades ago by CollabNet. Both open-source arenas and enterprises consider it a reliable option for valuable data.

SVN is easy to implement with any programming language. Also, it provides persistent storage for handling text and binary files.

Features:

• Inventory management
• Security management
• History tracking
• User access controls
• Data recovery
• Workflow management

These are the best version control systems that a web development company should definitely consider using, according to the requirements.

The post Top 5 Git Version Control Software in Cloud appeared first on scmGalaxy.

I am getting error called “GitLab is not responding” on front page.

Followup –

I did run status commands and got following output…

sudo gitlab-ctl status
run: nginx: (pid 12728) 165s; run: log: (pid 12574) 372s
run: postgresql: (pid 12731) 165s; run: log: (pid 12485) 421s
run: redis: (pid 12741) 165s; run: log: (pid 12402) 427s
run: sidekiq: (pid 12744) 165s; run: log: (pid 12558) 378s
run: unicorn: (pid 12808) 28s; run: log: (pid 12546) 380s

I stop and restart the gitlab using…

sudo gitlab-ctl start
ok: run: nginx: (pid 12961) 0s
ok: run: postgresql: (pid 12964) 0s
ok: run: redis: (pid 12967) 0s
ok: run: sidekiq: (pid 12970) 0s
ok: run: unicorn: (pid 12983) 0s

Solution

I found out that some other services was running with port 80. I just stopped that services and re-startted the gitlab services and it went through..
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post GitLab is not responding appeared first on scmGalaxy.

#!/bin/bash
sudo -u git -H /home/git/bin/gitlab-backup.sh

Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post How to take Gitlab backup appeared first on scmGalaxy.

The post GitLab: You are not allowed to access develop! appeared first on scmGalaxy.

To see the config –
cd /home/git/gitlab/config
more gitlab.yml
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn

The post My Gitlab First Notes… appeared first on scmGalaxy.

My setup:
I am using wehooks to to this configuration, the configuration is all fine.

Issue: when I push tag through Git Bash, it is triggering jenkins job, but when i push though Gitlab UI it does not.

Attach is my setup.

Also I dnt want to use Gitlab plunging to trigger jenkins job.

The post After Pushing tag in Gitlab UI, Gitlab should fire jenkins job. appeared first on scmGalaxy.

• web-based hosting service
• Unlimited private repositories
• Supports private & Public repositories
• Native integration (Jira, Confluence,Bamboo)
• Flexible deployment models
• Source tree – works with any git hosting
• Branch permissions
• Git Large File Storage (LFS)

• web-based hosting service
• Unlimited private repositories
• Built-in code review
• Supports private and Public repositories
• Support Many Programming language
• Flexible hosting plans
• Free to use for public and open source projects
• Comes with Issue tracking & Wikis

• Unlimited public and private repos
• web-based Git repository manager
• wiki and issue tracking features
• open source
• Allow Project importing
• Own Continuous Integration service
• Collect and share reusable code
• Control read/write permissions to specific branches

• Unlimited private code repositories
• Customizable Dashboards
• Branch Updates
• Code reviews
• Web Hooks & API Integration
• unlimited free private git repositories
• Get functionality with extensions
• Semantic Code Search
• Security – SOC compliance and multi-factor authentication
• Built-in continuous integration and support for Jenkins and others tools

Key Features

• All the power and flexibility of Git without compromise:
• Access control is more fine-grained
• Specific branches and files can be locked
• Developers can “slice” big repositories and pull only what they need
• Pull requests
• Merge-request workflow
• Issue tracking
• Git powered Wiki
• Project visibility & security
• Automatically mirrors work into Helix mainline repository

The post Top 5 Git hosting solutions | List of best Git hosting tools appeared first on scmGalaxy.

• What is GIT?
• What is a repository in GIT?
• What is the command you can use to write a commit message?
• What is the difference between GIT and SVN and other CM systems?
  • Answers –
    • Cheap Local Branching
    • Everything is Local
    • Git is Fast
    • Git is Small
    • The Staging Area
    • Distributed
    • Any Workflow
    • Easy to Learn
    • Git is the new standard
• What are the advantages of using GIT?
• What language is used in GIT?
• What is the function of ‘GIT PUSH’ in GIT?
• Why GIT better than Subversion?
• What is “Staging Area” or “Index” in GIT?
• What is GIT stash?
• What is GIT stash drop?
• How will you know in GIT if a branch has been already merged into master?
• What is the function of git clone?
• What is the function of ‘git config’?
• What does commit object contain?
• How can you create a repository in Git?
• What is ‘head’ in git and how many heads can be created in a repository?
• What is the purpose of branching in GIT?
• What is the common branching pattern in GIT?
• How can you bring a new feature in the main branch?
• What is a ‘conflict’ in git?
• How can conflict in git resolved?
• To delete a branch what is the command that is used?
• What is another option for merging in git?
• What is the syntax for “Rebasing” in Git?
• What is the difference between ‘git remote’ and ‘git clone’?
• What is GIT version control?
• Mention some of the best graphical GIT client for LINUX?
• What is Subgit? Why to use Subgit?
• What is the function of ‘git diff ’ in git?
• What is ‘git status’ is used for?
• What is the difference between the ‘git diff ’and ‘git status’?
• What is the function of ‘git checkout’ in git?
• What is the function of ‘git rm’?
• What is the function of ‘git stash apply’?
• What is the use of ‘git log’?
• What is ‘git add’ is used for?
• What is the function of ‘git reset’?
• What is git Is-tree?
• How git instaweb is used?
• What does ‘hooks’ consist of in git?
• Explain what is commit message?
• How can you fix a broken commit?
• What is ‘bare repository’ in GIT?
• How do you start Git and what is the process called?
• How do you put your local repository (repo) on the GitHub server?
• How to delete the working branch?
• What as the strength and weaknesses of the software?
• But I am quite happy with Subversion (SVN). What is all this fuss about? Is there a substantial trend for distributed versioning control systems (DVCS)?
• Isn’t DVCS something for small teams and startups? I am working in a very big company. We value established things way more than the cutting edge stuff, that may not be here to stay.
• Okay. Let’s say we go with DVCS. Why should I take git and not mercurial?
• I like, that git allows our developers to host the complete repository on his local machine. That makes software development faster. So why do
• you I need Stash on top?
• How do you use this rights management with Stash? How does it work? Will developers only get have a repository? Is that still functional then?
• What is a pull request? What is this for? Aren’t we sharing all code with all developers and let everyone do what he wants? Is that only for
• hierachical software development methods?
• How would you summarize the advantages of Stash in short?
• What is the one reason, that your customers give Atlassian today on why they purchase Stash?
• Can you offer us a small sneak peak into your upcoming next releases? Is there anything, that you can share first hand with us?
• What is your general roadmap for stash? Where do you want to position it near and long term?
• Do you ultimately plan to support Mercurial? When is a good time to buy Stash, if I run with hg at the moment?
• Why should I go for Stash in favor of GitHub Enterprise or RhodeCode?
• Why is Stash a separated product and not part of Bitbucket. I could imagine seeing Bitbucket Enterprise resembling GitHub Enterprise.
• Is Atlassian using Stash internally in software development? If not, why not?
• Wouldn’t it be interesting to combine Fisheye, Crucible and Stash in one product?
• What is the difference between GIT and SVN?
• What are the advantages of using GIT over other tools?
• What is GIT stash?
• What does commit object contain?
• How can conflict in git resolved?
• What is the difference between ‘git remote’ and ‘git clone’?
• Mention some of the best graphical GIT client for LINUX?
• What does ‘hooks’ consist of in git?
• What is ‘bare repository’ in GIT?
• Add a line to the some.txt file and then throw out all changes since the last commit.
• Why GIT better than Subversion?
• How to troubleshoot Git?
• How to troubleshoot GitLab?
• How to troubleshoot Github?
• How to take Gitlab backup
• What is Git Objects? explain about Tree, blob, commit, tag, branch objects?
• How git Object storage works?
• What is SHA1?
• Introduction to the GitHub platform
• github Distributed version control synchronization
• github Project management and repository integration
• github Multiple remotes and Fork maintenance
• github Remote repository interaction and dependencies

The post All Possible Interview Questions on Git, Github and Gitlab appeared first on scmGalaxy.

Step 1- Generate a public/private key using puttygen

• Download a puttygen from  and generate a public key and private key by following below image.
• Click on Conversions à Export OpenSSH Key à  and save it to % USERPROFILE %\.ssh with file name “id_rsa”
• Copy the public key from puttygen window and save into gitlab.

Step 2-  Add .ssh folder to your command line path
By following command..

     set HOME=%USERPROFILE%

or
add into user system variable.
HOME=%USERPROFILE%

And you are good to go. Comment if you face any issues?

The post Access gitlab Password Less in Windows appeared first on scmGalaxy.

Download gitlab from

https://www.gitlab.com/downloads/

Installation, setup, configuration, backup Instructions is given in…

https://gitlab.com/gitlab-org/omnibus-gitlab/blob/master/README.md
https://github.com/gitlabhq/gitlabhq/blob/6-1-stable/doc/install/installation.md

The post How to setup Gitlab in local machine ? appeared first on scmGalaxy.