8 ms·

GitLab 8.10 Released with Wildcard Branch Protection and Manual Actions for CI

135 points by ehPReth 10y ago

jobvandervoort 10y ago
As always, a release we're very proud of. We're happy to answer any questions.
- Zikes 10y ago
  Multiline blockquotes seem to be broken in the GitLab web site's GFM documentation: http://i.imgur.com/agTjiLc.png http://i.imgur.com/agTjiLc.png http://docs.gitlab.com/ce/markdown/markdown.html#multiline-blockquote http://docs.gitlab.com/ce/markdown/markdown.html#multiline-b...
  - DouweM 10y ago
    Good catch! Our Markdown documentation describes a lot of GitLab Flavored Markdown that will (currently) only work inside GitLab itself, not on the docs site which uses a completely different Markdown renderer. I've created a Merge Request to add a note to the top of the document encouraging people to view it within GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 You can check out the Multiline Blockquote example in all its glory here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/markdown/markdown.md#multiline-blockquote https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/mark...
  - JonathonW 10y ago
    Other GFM features are broken in the examples on that page, too. Looks like it was processed using a standard Markdown parser rather than a GFM-aware one. That page renders correctly if viewed through the repository browser (which apparently always renders Markdown as GFM): https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc//markdown/markdown.md https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc//mar...
slyzmud 10y ago
Nice. It keeps getting better with each release. Speed seems to have improved. The only place where github is better is in the UX. Gitlab is ugly on a small laptop screen, in issues view it has three top bars that becomes really annoying. It reminds me old IE days when you had a lot of bars. Apart from that, everything is amazing, I use it daily, specially Gitlab CI, which is one of the best CI ever.
- sytse 10y ago
  Thanks for your kind words. We're working on improving the UX. We recently redesigned the menu https://about.gitlab.com/2016/06/06/navigation-redesign/ https://about.gitlab.com/2016/06/06/navigation-redesign/ and we're hiring more UX designers and a UX lead on https://about.gitlab.com/jobs/ https://about.gitlab.com/jobs/ Thanks for naming an example of a view we can improve, I've screenshotted the issue view in http://imgur.com/a/0FREI http://imgur.com/a/0FREI Suggestions are very welcome. Glad to hear CI is working out for you. It was great seeing CaptainTrain write about it yesterday https://blog.captaintrain.com/12703-building-on-gitlab-ci https://blog.captaintrain.com/12703-building-on-gitlab-ci
  - ryanmaclean 10y ago
    This is a fantastic example of the reason we went with Gitlab! I wish other products were this pro-active! Keep up the great work folks.
    - sytse 10y ago
      Thanks Ryan!
  - dominotw 10y ago
    hey sytse, how does gitlab ci handle caching of maven,ivy, gem s...artifacts? Does each new build have to download it ? I see some issues discussions, workarounds and seems like it does allow -cache directories but it is unclear how it all works. for us( unfortunately) its 40 min vs 5 min build times, with/without caches.
vamega 10y ago
Is it common for Gitlab to take contributions from the community and release them as Enterprise Only, or am I understanding things incorrectly? Is the Kerberos Ticket based git pull Enterprise only?
- sytse 10y ago
  We only release things as Enterprise Edition only if they are contributed to that repository. We never deprecate features from the Community Edition. See https://about.gitlab.com/about/#stewardship https://about.gitlab.com/about/#stewardship In this case I think CERN contributed code for both SAML and Kerberos over time. The SAML code got merged into CE and we ended up spending a lot of time improving it, documenting it, and providing unpaid support. It turns out that SAML is more of a framework for creating standards than a standard :) The Kerberos functionality was contributed by CERN to Enterprise Edition https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6 https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6 and CERN left this comment https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/685#note_1297043 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/685#n... on the Kerberos CE contribution. I think Kerberos Ticket based git pull is Enterprise only.
eMerzh 10y ago
Nice! Good release !... One thing that make the user experience way less friendly and make me worry about pushing as our main repo is the git push/pull speed.... Coming from GitHub or bitbucket it feels really slow. But I don't give up hope! Keep up the good work!
- sytse 10y ago
  Thanks for your enthousiasm. Self hosted GitLab instances should be really fast but GitLab.com is indeed very slow. This is due to us only using a single NFS server. With the release of 'Multiple Repository Mount Points' today we can start adding more servers. Long term we want to move to distributed storage with Ceph and we hired a consultant to help us with this that started last Monday. Also see https://gitlab.com/gitlab-com/operations/issues/1 https://gitlab.com/gitlab-com/operations/issues/1
  - eMerzh 10y ago
    Oh and btw is there some sort of support for gitlab.com we got issues with new accounts and didn't really knew where to go...
    - sytse 10y ago
      I'm sorry to hear you had issues with your new account. I assume it has to do with email confirmation. Please email support@ company domain to get help. For more general GitLab.com questions the options are listed on https://about.gitlab.com/gitlab-com/ https://about.gitlab.com/gitlab-com/ Free subscribers can use the GitLab.com Support Tracker https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues if they have questions. If you purchase GitLab.com Bronze Support you can email support directly for timely, personal and private answers. This costs $9.99 per user per year for next-business-day response time and is available in packs of 20 users.
  - mrmondo 10y ago
    I can confirm this, self-hosted is incredibly fast - you'll wonder how you ever used gitlab.com or github.com for that matter. It's as fast as it is for me to push to a locally running git server to be honest.
nieksand 10y ago
Very excited to see the progress. We're switching over from Github to Gitlab EE in the coming weeks. I do wish cross-repo pull requests could be imported. (http://docs.gitlab.com/ce/workflow/importing/import_projects_from_github.html http://docs.gitlab.com/ce/workflow/importing/import_projects...). Right now we have to hang on to a small number of GH accounts just to keep several years of that valuable history.
- sytse 10y ago
  Thanks for posting Niek. Glad to hear you'll be switching to GitLab! Good point about importing cross repository pull requests correctly, I've made a feature request for it in https://gitlab.com/gitlab-org/gitlab-ce/issues/20153 https://gitlab.com/gitlab-org/gitlab-ce/issues/20153
131hn 10y ago
There's also the "disable clone over http, https, just allow ssh" setting we are so longing for ! Great release !
- sytse 10y ago
  Thanks, glad to hear that we shipped what you needed.
aw3c2 10y ago
Now please tone down the incredible amount of unwanted mail you send to new signups, got my colleagues fairly puzzled after I insisted we use GitLab instead of GitHub. :(
- mrmondo 10y ago
  That's a rather rude, unconstructive way of asking for someone to do something for free for you. How about logging a bug, or if you have - linking to it here to get some additional traction?
  - aw3c2 10y ago
    Can you tell me where to log that bug?
    - swsieber 10y ago
      The second yahoo result for "gitlab issue tracker", (the first was the about page): https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues For the record, it's pretty easy to change your notification settings.
      - aw3c2 10y ago
        That's self-hosted GitLab CE, I meant mails from when people sign up at gitlab.com
    - mrmondo 10y ago
      The first result on google for 'log gitlab bug': https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues Don't worry about the 'ce vs ee' thing, it makes no difference, it's all the same code and regardless, the company and the community care about the product and will respond.
- plusECON 10y ago
  GitLab marketer here - sorry if we inundated your team! This section of our handbook has info on emails, but it's due for an update from me: https://about.gitlab.com/handbook/marketing/demand-generation/#newsletter https://about.gitlab.com/handbook/marketing/demand-generatio... A typical frequency would be 2-5 emails over the first 7 days after signup, then ~2/month afterward (unless you also sign up for security updates). I'd like to make a change so that it's 2-5 emails over the first 9 days after signup. About 80% of people only qualify for newsletters and one onboarding or confirmation email in the first week after signup, whereas people at companies we suspect more interested in EE and/or support will receive 1-3 extra from our business development reps. We try to limit our more "salesy" outreach with "lead scoring", an industry standard for IDing those most likely interested in those type of emails (see https://about.gitlab.com/handbook/marketing/demand-generation/#SQL https://about.gitlab.com/handbook/marketing/demand-generatio... ). The response to our emails is usually positive (sometimes even apologetic to the BDRs for slow response) as the BDR team can attest to, though we do get our fair share of unsubscribes (our reps include a one-click unsub link in their signature - highly unusual!) and the occasional two-word "f* you!" replies. Let me add that we don't ask for phone numbers from new signups and you will not be burdened with nonsense voicemails from us! That being said, feedback like this is always a good catalyst to reevaluate and look for opportunities to adjust and improve. As stated in the first link I provided, "What [you] receive depends on how [you] came to find us and what we believe will be most helpful to [you]", so any specific feedback on how to be more helpful is greatly appreciated! -Hank Taylor
zmmmmm 10y ago
Wow. Hard to believe the pace at which this progresses and the quality that they pull off while doing it. Great job! The only big thing I miss (and I miss this with Github too) is a way to prioritise issues. Yes, I get it, you can label things 10 different ways and achieve most of what you get from a priority system. It doesn't replace the simple ability to get a list in order of the most important things outstanding in order. I want it to be easy to generate a list of 'urgent' and 'high priority' where the 'urgent' issues are listed ahead of the 'high priority' and not ordered randomly.
- Snappy 10y ago
  Priority labels aren't enough for you? (https://about.gitlab.com/2016/06/22/gitlab-8-9-released/#priority-labels https://about.gitlab.com/2016/06/22/gitlab-8-9-released/#pri...) We're using P1, P2, etc. internally, but you could easily use `urgent` and `high priority` labels and then sort your lists by `Priority`.
  - zmmmmm 10y ago
    Oh my goodness I didn't even know about those. I think it will address my needs perfectly. I will have to badger our systems people to upgrade. Thankyou!
    - Snappy 10y ago
      Great! Let us know if you have any feedback after you've tried them out.
- oelmekki 10y ago
  I use milestones, for that. I almost never set a "due date". I find the milestone feature useful for doing, well, lot of not milestone related things. First, they have a three columns (unstarted / started / completed) which adds easily simple trello-like boards to your projects. Then, issues in those columns are sortable, like you describe, to prioritize. Simple drag'n'drop, could not get easier. And finally, I use their description as a "release note". When MRs mention tasks to run on deploy, I'll just add them in milestone description, and I'll have a central doc for release.
vikeri 10y ago
The manual release feature is great! I was just pondering on how to do that. For anyone wondering where to start with Gitlab CI I wrote a short post about our very simple but still very useful CI setup: https://pilloxa.gitlab.io/posts/ci-with-gitlab-and-docker/ https://pilloxa.gitlab.io/posts/ci-with-gitlab-and-docker/
- sytse 10y ago
  Glad to hear you like it. Thanks for your post. BTW now that we have the container registry you no longer need to create an account at Dockerhub I think.
faizmokhtar 10y ago
Loving the new update but I can't help noticing that each new update will reset my view preferences.
- sytse 10y ago
  Mmm, I thought these are stored in the database, they should not reset I think. If so please create an issue.
nullcipher 10y ago
I want to love gitlab but it's very slow on small machines (2gb). Worse is that they insist on this omnibus stuff which is all great if you have time on your hands. Any reason gitlab does not auto update?
- lloeki 10y ago
  This is lacking detail about the exact use case but either one of: - use gitlab.com with private repos for free - install from source to skip omnibus. I've been updating ours for a couple years now and it's always been simple. Bonus is that if you need a quick patch or even the occasional bespoke tweak you've got the git repo right there which has been invaluable. - githost.io is a thing (contemplating migrating to it nonetheless because GitLab has really come so far that we don't need much patches anymore)
- sytse 10y ago
  If you run it on a 2GB machine I recommend using the Omnibus package since it automatically kills and restarts processes that run out of memory (unicorn and sidekiq). You mention that Omnibus is great if you have time on your hands. I don't understand this remark, the of the Omnibus package is to allow you to install GitLab in 2 minutes. With the Omnibus packages you can use apt or yum to auto update.
Sheepsteak 10y ago
Inline Videos now supported! I've been wanting this on GitHub for so long. The example in the docs seems broken to me though - http://docs.gitlab.com/ce/markdown/markdown.html#videos http://docs.gitlab.com/ce/markdown/markdown.html#videos
- DouweM 10y ago
  Yep, you're right, our Markdown documentation describes a lot of GitLab Flavored Markdown that will (currently) only work inside GitLab itself, not on the docs site which uses a completely different Markdown renderer. I've added a note to the top of the document encouraging people to view it within GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 You can check out the Videos example in all its glory here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/markdown/markdown.md#videos https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/mark... It appears however that it doesn't currently work correctly with files in the same repo, just with absolute links. I've created an issue for that here: https://gitlab.com/gitlab-org/gitlab-ce/issues/20189 https://gitlab.com/gitlab-org/gitlab-ce/issues/20189
b34r 10y ago
What's with the >>> fencing notation? Bugs me when companies intentionally reinvent the wheel.
- DouweM 10y ago
  I added the blockquote fence feature because I was getting tired of having to manually prefix every line with `>` when I was quoting a multiline message like an entire email. I picked `>>>` because it mirrored the triple-backtick syntax for fenced code blocks, and `>` was already used for single-line blockquotes. You can see the feature proposal I filed at https://gitlab.com/gitlab-org/gitlab-ce/issues/16564 https://gitlab.com/gitlab-org/gitlab-ce/issues/16564, and the merge request I submitted to implement the feature at https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3954 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3954, for some more insight into how this came to be. I'm sad to hear that this feels like reinventing the wheel to you. From my perspective, there existed an imperfect wheel that we "invented" a more powerful alternative to.

135 points by ehPReth 10y ago

jobvandervoort 10y ago

As always, a release we're very proud of. We're happy to answer any questions.

Zikes 10y ago
Multiline blockquotes seem to be broken in the GitLab web site's GFM documentation: http://i.imgur.com/agTjiLc.png http://i.imgur.com/agTjiLc.png http://docs.gitlab.com/ce/markdown/markdown.html#multiline-blockquote http://docs.gitlab.com/ce/markdown/markdown.html#multiline-b...
- DouweM 10y ago
  Good catch! Our Markdown documentation describes a lot of GitLab Flavored Markdown that will (currently) only work inside GitLab itself, not on the docs site which uses a completely different Markdown renderer. I've created a Merge Request to add a note to the top of the document encouraging people to view it within GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 You can check out the Multiline Blockquote example in all its glory here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/markdown/markdown.md#multiline-blockquote https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/mark...
- JonathonW 10y ago
  Other GFM features are broken in the examples on that page, too. Looks like it was processed using a standard Markdown parser rather than a GFM-aware one. That page renders correctly if viewed through the repository browser (which apparently always renders Markdown as GFM): https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc//markdown/markdown.md https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc//mar...

slyzmud 10y ago

Nice. It keeps getting better with each release. Speed seems to have improved. The only place where github is better is in the UX. Gitlab is ugly on a small laptop screen, in issues view it has three top bars that becomes really annoying. It reminds me old IE days when you had a lot of bars. Apart from that, everything is amazing, I use it daily, specially Gitlab CI, which is one of the best CI ever.

sytse 10y ago
Thanks for your kind words. We're working on improving the UX. We recently redesigned the menu https://about.gitlab.com/2016/06/06/navigation-redesign/ https://about.gitlab.com/2016/06/06/navigation-redesign/ and we're hiring more UX designers and a UX lead on https://about.gitlab.com/jobs/ https://about.gitlab.com/jobs/ Thanks for naming an example of a view we can improve, I've screenshotted the issue view in http://imgur.com/a/0FREI http://imgur.com/a/0FREI Suggestions are very welcome. Glad to hear CI is working out for you. It was great seeing CaptainTrain write about it yesterday https://blog.captaintrain.com/12703-building-on-gitlab-ci https://blog.captaintrain.com/12703-building-on-gitlab-ci
- ryanmaclean 10y ago
  This is a fantastic example of the reason we went with Gitlab! I wish other products were this pro-active! Keep up the great work folks.
  - sytse 10y ago
    Thanks Ryan!
- dominotw 10y ago
  hey sytse, how does gitlab ci handle caching of maven,ivy, gem s...artifacts? Does each new build have to download it ? I see some issues discussions, workarounds and seems like it does allow -cache directories but it is unclear how it all works. for us( unfortunately) its 40 min vs 5 min build times, with/without caches.

vamega 10y ago

Is it common for Gitlab to take contributions from the community and release them as Enterprise Only, or am I understanding things incorrectly? Is the Kerberos Ticket based git pull Enterprise only?

sytse 10y ago
We only release things as Enterprise Edition only if they are contributed to that repository. We never deprecate features from the Community Edition. See https://about.gitlab.com/about/#stewardship https://about.gitlab.com/about/#stewardship In this case I think CERN contributed code for both SAML and Kerberos over time. The SAML code got merged into CE and we ended up spending a lot of time improving it, documenting it, and providing unpaid support. It turns out that SAML is more of a framework for creating standards than a standard :) The Kerberos functionality was contributed by CERN to Enterprise Edition https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6 https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/6 and CERN left this comment https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/685#note_1297043 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/685#n... on the Kerberos CE contribution. I think Kerberos Ticket based git pull is Enterprise only.

eMerzh 10y ago

Nice! Good release !... One thing that make the user experience way less friendly and make me worry about pushing as our main repo is the git push/pull speed.... Coming from GitHub or bitbucket it feels really slow. But I don't give up hope! Keep up the good work!

sytse 10y ago
Thanks for your enthousiasm. Self hosted GitLab instances should be really fast but GitLab.com is indeed very slow. This is due to us only using a single NFS server. With the release of 'Multiple Repository Mount Points' today we can start adding more servers. Long term we want to move to distributed storage with Ceph and we hired a consultant to help us with this that started last Monday. Also see https://gitlab.com/gitlab-com/operations/issues/1 https://gitlab.com/gitlab-com/operations/issues/1
- eMerzh 10y ago
  Oh and btw is there some sort of support for gitlab.com we got issues with new accounts and didn't really knew where to go...
  - sytse 10y ago
    I'm sorry to hear you had issues with your new account. I assume it has to do with email confirmation. Please email support@ company domain to get help. For more general GitLab.com questions the options are listed on https://about.gitlab.com/gitlab-com/ https://about.gitlab.com/gitlab-com/ Free subscribers can use the GitLab.com Support Tracker https://gitlab.com/gitlab-com/support-forum/issues https://gitlab.com/gitlab-com/support-forum/issues if they have questions. If you purchase GitLab.com Bronze Support you can email support directly for timely, personal and private answers. This costs $9.99 per user per year for next-business-day response time and is available in packs of 20 users.
- mrmondo 10y ago
  I can confirm this, self-hosted is incredibly fast - you'll wonder how you ever used gitlab.com or github.com for that matter. It's as fast as it is for me to push to a locally running git server to be honest.

nieksand 10y ago

Very excited to see the progress. We're switching over from Github to Gitlab EE in the coming weeks. I do wish cross-repo pull requests could be imported. (http://docs.gitlab.com/ce/workflow/importing/import_projects_from_github.html http://docs.gitlab.com/ce/workflow/importing/import_projects...). Right now we have to hang on to a small number of GH accounts just to keep several years of that valuable history.

sytse 10y ago
Thanks for posting Niek. Glad to hear you'll be switching to GitLab! Good point about importing cross repository pull requests correctly, I've made a feature request for it in https://gitlab.com/gitlab-org/gitlab-ce/issues/20153 https://gitlab.com/gitlab-org/gitlab-ce/issues/20153

131hn 10y ago

There's also the "disable clone over http, https, just allow ssh" setting we are so longing for ! Great release !

sytse 10y ago
Thanks, glad to hear that we shipped what you needed.

aw3c2 10y ago

Now please tone down the incredible amount of unwanted mail you send to new signups, got my colleagues fairly puzzled after I insisted we use GitLab instead of GitHub. :(

mrmondo 10y ago
That's a rather rude, unconstructive way of asking for someone to do something for free for you. How about logging a bug, or if you have - linking to it here to get some additional traction?
- aw3c2 10y ago
  Can you tell me where to log that bug?
  - swsieber 10y ago
    The second yahoo result for "gitlab issue tracker", (the first was the about page): https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues For the record, it's pretty easy to change your notification settings.
    - aw3c2 10y ago
      That's self-hosted GitLab CE, I meant mails from when people sign up at gitlab.com
  - mrmondo 10y ago
    The first result on google for 'log gitlab bug': https://gitlab.com/gitlab-org/gitlab-ce/issues https://gitlab.com/gitlab-org/gitlab-ce/issues Don't worry about the 'ce vs ee' thing, it makes no difference, it's all the same code and regardless, the company and the community care about the product and will respond.
plusECON 10y ago
GitLab marketer here - sorry if we inundated your team! This section of our handbook has info on emails, but it's due for an update from me: https://about.gitlab.com/handbook/marketing/demand-generation/#newsletter https://about.gitlab.com/handbook/marketing/demand-generatio... A typical frequency would be 2-5 emails over the first 7 days after signup, then ~2/month afterward (unless you also sign up for security updates). I'd like to make a change so that it's 2-5 emails over the first 9 days after signup. About 80% of people only qualify for newsletters and one onboarding or confirmation email in the first week after signup, whereas people at companies we suspect more interested in EE and/or support will receive 1-3 extra from our business development reps. We try to limit our more "salesy" outreach with "lead scoring", an industry standard for IDing those most likely interested in those type of emails (see https://about.gitlab.com/handbook/marketing/demand-generation/#SQL https://about.gitlab.com/handbook/marketing/demand-generatio... ). The response to our emails is usually positive (sometimes even apologetic to the BDRs for slow response) as the BDR team can attest to, though we do get our fair share of unsubscribes (our reps include a one-click unsub link in their signature - highly unusual!) and the occasional two-word "f* you!" replies. Let me add that we don't ask for phone numbers from new signups and you will not be burdened with nonsense voicemails from us! That being said, feedback like this is always a good catalyst to reevaluate and look for opportunities to adjust and improve. As stated in the first link I provided, "What [you] receive depends on how [you] came to find us and what we believe will be most helpful to [you]", so any specific feedback on how to be more helpful is greatly appreciated! -Hank Taylor

zmmmmm 10y ago

Wow. Hard to believe the pace at which this progresses and the quality that they pull off while doing it. Great job! The only big thing I miss (and I miss this with Github too) is a way to prioritise issues. Yes, I get it, you can label things 10 different ways and achieve most of what you get from a priority system. It doesn't replace the simple ability to get a list in order of the most important things outstanding in order. I want it to be easy to generate a list of 'urgent' and 'high priority' where the 'urgent' issues are listed ahead of the 'high priority' and not ordered randomly.

Snappy 10y ago
Priority labels aren't enough for you? (https://about.gitlab.com/2016/06/22/gitlab-8-9-released/#priority-labels https://about.gitlab.com/2016/06/22/gitlab-8-9-released/#pri...) We're using P1, P2, etc. internally, but you could easily use `urgent` and `high priority` labels and then sort your lists by `Priority`.
- zmmmmm 10y ago
  Oh my goodness I didn't even know about those. I think it will address my needs perfectly. I will have to badger our systems people to upgrade. Thankyou!
  - Snappy 10y ago
    Great! Let us know if you have any feedback after you've tried them out.
oelmekki 10y ago
I use milestones, for that. I almost never set a "due date". I find the milestone feature useful for doing, well, lot of not milestone related things. First, they have a three columns (unstarted / started / completed) which adds easily simple trello-like boards to your projects. Then, issues in those columns are sortable, like you describe, to prioritize. Simple drag'n'drop, could not get easier. And finally, I use their description as a "release note". When MRs mention tasks to run on deploy, I'll just add them in milestone description, and I'll have a central doc for release.

vikeri 10y ago

The manual release feature is great! I was just pondering on how to do that. For anyone wondering where to start with Gitlab CI I wrote a short post about our very simple but still very useful CI setup: https://pilloxa.gitlab.io/posts/ci-with-gitlab-and-docker/ https://pilloxa.gitlab.io/posts/ci-with-gitlab-and-docker/

sytse 10y ago
Glad to hear you like it. Thanks for your post. BTW now that we have the container registry you no longer need to create an account at Dockerhub I think.

faizmokhtar 10y ago

Loving the new update but I can't help noticing that each new update will reset my view preferences.

sytse 10y ago
Mmm, I thought these are stored in the database, they should not reset I think. If so please create an issue.

nullcipher 10y ago

I want to love gitlab but it's very slow on small machines (2gb). Worse is that they insist on this omnibus stuff which is all great if you have time on your hands. Any reason gitlab does not auto update?

lloeki 10y ago
This is lacking detail about the exact use case but either one of: - use gitlab.com with private repos for free - install from source to skip omnibus. I've been updating ours for a couple years now and it's always been simple. Bonus is that if you need a quick patch or even the occasional bespoke tweak you've got the git repo right there which has been invaluable. - githost.io is a thing (contemplating migrating to it nonetheless because GitLab has really come so far that we don't need much patches anymore)
sytse 10y ago
If you run it on a 2GB machine I recommend using the Omnibus package since it automatically kills and restarts processes that run out of memory (unicorn and sidekiq). You mention that Omnibus is great if you have time on your hands. I don't understand this remark, the of the Omnibus package is to allow you to install GitLab in 2 minutes. With the Omnibus packages you can use apt or yum to auto update.

Sheepsteak 10y ago

Inline Videos now supported! I've been wanting this on GitHub for so long. The example in the docs seems broken to me though - http://docs.gitlab.com/ce/markdown/markdown.html#videos http://docs.gitlab.com/ce/markdown/markdown.html#videos

DouweM 10y ago
Yep, you're right, our Markdown documentation describes a lot of GitLab Flavored Markdown that will (currently) only work inside GitLab itself, not on the docs site which uses a completely different Markdown renderer. I've added a note to the top of the document encouraging people to view it within GitLab: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/5440 You can check out the Videos example in all its glory here: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/markdown/markdown.md#videos https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/mark... It appears however that it doesn't currently work correctly with files in the same repo, just with absolute links. I've created an issue for that here: https://gitlab.com/gitlab-org/gitlab-ce/issues/20189 https://gitlab.com/gitlab-org/gitlab-ce/issues/20189

b34r 10y ago

What's with the >>> fencing notation? Bugs me when companies intentionally reinvent the wheel.

DouweM 10y ago
I added the blockquote fence feature because I was getting tired of having to manually prefix every line with `>` when I was quoting a multiline message like an entire email. I picked `>>>` because it mirrored the triple-backtick syntax for fenced code blocks, and `>` was already used for single-line blockquotes. You can see the feature proposal I filed at https://gitlab.com/gitlab-org/gitlab-ce/issues/16564 https://gitlab.com/gitlab-org/gitlab-ce/issues/16564, and the merge request I submitted to implement the feature at https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3954 https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3954, for some more insight into how this came to be. I'm sad to hear that this feels like reinventing the wheel to you. From my perspective, there existed an imperfect wheel that we "invented" a more powerful alternative to.