GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring • Hacker News Board

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#21

Post by mrmondo » Mon, Jan 23, 2017, 3:10 AM UTC

sytse wrote: post #20

mrmondo wrote: post #18

Another smooth upgrade minus one bug with people on chrome trying to approve and accept merge requests (I've logged ee bug #1575 for this).

Sam, thanks for filing https://gitlab.com/gitlab-org/gitlab-ee/issues/1575 I've pinged our frontend team.

No worries, hope my report was good enough! Excellent support as always :)

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#22

Post by sytse » Mon, Jan 23, 2017, 4:17 AM UTC

mrmondo wrote: post #21

sytse wrote: post #20

Earlier quoted context omitted.

Sam, thanks for filing https://gitlab.com/gitlab-org/gitlab-ee/issues/1575 I've pinged our frontend team.

No worries, hope my report was good enough! Excellent support as always :)

Thanks for helping to troubleshoot in the issue. Our frontend lead and VP of Engineering are on it.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#23

Post by gtirloni » Mon, Jan 23, 2017, 4:21 AM UTC

Got it running on GKE but the mandatory password change didn't work (request rejected).

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#24

Post by sytse » Mon, Jan 23, 2017, 4:29 AM UTC

gtirloni wrote: post #23

Got it running on GKE but the mandatory password change didn't work (request rejected).

Mmm, that is strange, I don't have a clue why that would happen.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#25

Post by sandGorgon » Mon, Jan 23, 2017, 5:44 AM UTC

Also includes Mattermost in this release. Sweet!

>This release migrates project related statistics to a separate table, removing existing columns in the process. This migration process requires downtime, and can take 10-15 minutes for large installations.

Any place i can eyeball this upgrade script first?

Incidentally, Im curious to know (to try and learn) how do you guys test this kind of stuff? do you have lots of different databases saved over that you try this kind of a major db upgrade on?

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#26

Post by bedros » Mon, Jan 23, 2017, 6:22 AM UTC

I'm currently using redmine for my private project, anyone would recommend using gitlab CE instead?

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#27

Post by mrmondo » Mon, Jan 23, 2017, 6:43 AM UTC

sytse wrote: post #22

mrmondo wrote: post #21

Earlier quoted context omitted.

No worries, hope my report was good enough! Excellent support as always :)

Thanks for helping to troubleshoot in the issue. Our frontend lead and VP of Engineering are on it.

And they swarmed the issue and found the issue (within the nginx config) very odd-ball one indeed that didn't affect everyone, fantastic troubleshooting by all the Gitlab engineers, excellent communication and top-notch support like I've never experienced from any software vendor before. A+++ would commit again ;)

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#28

Post by KuhlMensch » Mon, Jan 23, 2017, 8:58 AM UTC

markdog12 wrote: post #11

Using Gitlab at our company and I love it. I could never agree with the "small teams don't need/want time tracking" argument, so I'm very happy to see they released it for CE.

I am a bit unsure what Gitlab consider a small team. But I find myself getting a little exasperated when they choose to keep features from CE because "small teams don't need it". Last week I found this was the reason they did not include global contributer statistics in CE. This would be a trivial change, and an important one for my team of ~14 engineers with in-house tools and a microservice architecture who would like to see the pulse of development.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#29

Post by petepete » Mon, Jan 23, 2017, 9:16 AM UTC

bedros wrote: post #26

I'm currently using redmine for my private project, anyone would recommend using gitlab CE instead?

We made the jump (moving various internal projects from Redmine, Trac and Assembla) and couldn't be happier. Everyone loves Gitlab, updates are frequent and full of new features, stability isn't a problem and CI is so easy to get up and running.

Only negative is that you need quite a beefy server to run it (compared to say Gitea or Gogs), but it's a small price to pay.

Re: GitLab 8.16 Released with auto deploy on GKE and Prometheus monitoring

#30

Post by vetinari » Mon, Jan 23, 2017, 10:19 AM UTC

bedros wrote: post #26

I'm currently using redmine for my private project, anyone would recommend using gitlab CE instead?

Depending what you need it for.

Redmine is still better from the project management planning and control POV (i.e. issues can be in different queues, but still form a coherent hierarchy, milestones consisting from issues and the control of time spent/still required to finish them; the work needed can be not only programming, but also other activities, etc.).

Gitlab is much nicer for the developers.

So for a private project, Gitlab might be a worth to try.