Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
O orientation
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 36
    • Merge requests 36
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Newbies
  • orientation
  • Merge requests
  • !42

Open
Created May 30, 2020 by Yogesh Hegde@yh42Owner
  • Report abuse
Report abuse

Update gitlabSummary.md

  • Overview 0
  • Commits 1
  • Changes 1
  1. In this post GitLab Workflow Stages of Software Development GitLab Issue Tracker Confidential Issues Due dates Assignee Labels Issue Weight GitLab Issue Board Code Review with GitLab First Commit Merge Request WIP MR Review Build, Test, and Deploy Koding Use-Cases Feedback: Cycle Analytics Enhance Issue and MR Templates Milestones Pro Tips For both Issues and MRs Subscribe Add TO-DO Search for your Issues and MRs Moving Issues Code Snippets GitLab WorkFlow Use-Case Scenario Conclusions

GitLab Workflow:

Stages of Software Development: ##The natural course of the software development process passes through 10 major steps; GitLab has built solutions for all of them:

  1. IDEA: Every new proposal starts with an idea, which usually come up in a chat. For this stage, GitLab integrates with Mattermost.
  2. ISSUE: The most effective way to discuss an idea is creating an issue for it. Your team and your collaborators can help you to polish and improve it in the issue tracker.
  3. PLAN: Once the discussion comes to an agreement, it's time to code. But wait! First, we need to prioritize and organize our workflow. For this, we can use the Issue Board.
  4. CODE: Now we're ready to write our code, once we have everything organized.
  5. COMMIT: Once we're happy with our draft, we can commit our code to a feature-branch with version control.
  6. TEST: With GitLab CI, we can run our scripts to build and test our application.
  7. REVIEW: Once our script works and our tests and builds succeeds, we are ready to get our code reviewed and approved
  8. STAGING: Now it's time to deploy our code to a staging environment to check if everything worked as we were expecting or if we still need adjustments.
  9. PRODUCTION: When we have everything working as it should, it's time to deploy to our production environment!
  10. FEEDBACK: Now it's time to look back and check what stage of our work needs improvement. We use Cycle Analytics for feedback on the time we spent on key stages of our process.

GitLab Issue Tracker: ##GitLab has a powerful issue tracker that allows you, your team, and your collaborators to share and discuss ideas, before and while implementing them.

##The GitLab Issue Tracker presents extra functionalities to make it easier to organize and prioritize your actions, described in the following sections.

Confidential Issues:

  • Whenever you want to keep the discussion presented in a issue within your team only, you can make that issue confidential. Even if your project is public, that issue will be preserved.
  • The browser will respond with a 404 error whenever someone who is not a project member with at least Reporter level tries to access that issue's URL
Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: patch-4