You're doing code review of a new feature and wonder how it'll actually feel, look and work when it's live. Yesterday, you had to sacrifice your local development environment's state, checkout the remote branch, run migrations, and then spin up the entire development environment. Today, you can just go to GitLab and click the link in the merge request to play with a fully functional, live environment.
Maybe you have some feedback on what you saw and start talking with your colleague on chat. Rather than having to communicate on who moves the result to issues, you just create an issue directly from chat. You can immediately add a time estimate to the issue and anyone peeking at the cycle analytics will see the new issue come by and over time, move to production, giving you feedback on where things might get stuck.
You can do all of the above and much more with GitLab 8.14, today. Time tracking, Review Apps, Chat commands, Cycle Analytics improvements and much more.
This month's Most Valuable Person (MVP) is Toon Claes. Toon contributed the button to delete all merged branches, a great addition to GitLab. Thanks Toon Claes!
Tune in on Nov. 30 for our 8.14 release webcast with a live demo of Review Apps and Time Tracking for EE! Register here!
Time Tracking Beta (EE)
Whether you're a contractor that needs to keep track of their time, or you're managing time spent on issues and projects, time tracking has traditionally been a painful experience: You have various systems to keep track or log your time and these never seem to fit in your day-to-day workflow.
You can now track your time right where you're working, with Time Tracking in GitLab.
With Time Tracking, you're able to set estimates for how much time is necessary for a particular issue. All you have to do is use a new slash command, which can be entered in the issue description or a comment:
/estimate 6h
You can adjust this at any time with the same command. Once you've spent time on an issue, you can log this simply with:
/spend 3h
You'll see this reflected in the interface.
Time Tracking is made available as trial to all our Enterprise Edition customers during the beta period, after which it becomes available as a paid Product.
We're interested in hearing how we can improve time tracking to fit your workflow. Let us know by creating an issue or below in the comments.
Chat Commands (experimental)
It seems like communication has moved from the conference room to the online chatroom in the last few years. In particular, collaboration and idea generation seem to happen here, and that's an important part of the idea-to-production vision that we aim to capture with GitLab. With Chat Commands you can now bridge the gap between chat and GitLab's repositories, issue tracker, and CI/CD pipelines quickly and easily.
With this first iteration, you can quickly create or view an issue, for instance, using this to make an issue with the title and description already filled in:
/gitlab issue create Even Better Issue Boards
Let's make Issue boards _even_ better!
You can also embrace ChatOps and trigger deploys to production (using the proper identity and permissions of the user):
/gitlab deploy staging to production
This iteration supports Mattermost, which ships with GitLab Omnibus. Slack support is coming soon. The command set is limited, but we're looking to add more soon and would love your feedback.
continue reading @ https://about.gitlab.com/2016/11/22/gitlab-8-14-released/?utm_medium=email&utm_source=marketo&utm_campaign=survey+newsletter&utm_content=november+22+2016&mkt_tok=eyJpIjoiWmpZNU5ERmhaRGd4TURNMiIsInQiOiJncXBkNnQzVDljaXh2U1dKUm9SckJLQTNLNEM5a2c2dFBiZVVMaE5OWVVSZmlud3dUR1lNZHIzM2NLYWxBdG4yV1lkdlF6V0FvN2F5YnRhU3BEKzJHS1NPT2dlRm1vbEZ0TTlIUkV4XC9STUU9In0%3D
Post a Comment