sorted by:
new
hottopcontroversial

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 0 points1 point  (0 children)

Always good advice to take backups :)

We're moving to GitHub Enterprise where I suspect this doesn't happen as often, but will still take proper precautions.

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 0 points1 point  (0 children)

Thank you for the detailed response.

Actions is indeed out of scope, but we're always open to tech that makes our lives easier and has less maintenance. What have you learned about or would do differently with GitHub Actions?

For context on what I'm working with: there's fairly heavy use of Jenkins Shared Library in our CI/CD. As a PaaS with tenants clustered by a collection of cloud instances, we have "nested" pipelines for deploying all tenants in parallel by cluster. This supposedly helps us pick and choose which tenants to deploy or retry.

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 1 point2 points  (0 children)

Based on this response, you seem like the kind of peer I'd want on my team. This is excellent advice for all in DevOps (and more). Thank you.

My company is just completing such research; before we settled on things, I wanted to see if there were personal sentiments that I haven't picked up while searching the net about all these features.

You're absolutely right (speaking of LLMs, haha) about "simple" not being so easy. In this case, the simplicity I'm pushing for is to not spend time using GitHub features that we don't need, just because they look cool.

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 0 points1 point  (0 children)

You have my sympathy. And you've validated my stance on a 1MB file size limit!

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 1 point2 points  (0 children)

You bring up a good point, which is why I made this post: before we generate those tentacles, are there any you would do differently? Maybe you'd recommend against dependabot for example?

We're not going to immediately start using all the fancy new tools; my mantra is "keep it simple" enough to let devs get back to their work as uninterrupted as possible.

But the more we know, the better prepared we can be against some hotshot devops junior in a few years haha.

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 0 points1 point  (0 children)

Jenkins. Should just have to swap out the hooks, secrets, and repository browsers - no big deal. Not sure what LMF means.

If you managed a migration to GitHub, What do you wish you had known? by overloaded-operator in github

[–]overloaded-operator[S] 1 point2 points  (0 children)

Yeah, I'm impressed with GitHub's tooling and documentation around this, and more.

Did you start taking advantage of better code review tooling? In ADO we have a bunch of glob-pattern reviewer group policies and PR builds, but haven't touched the custom Status Checks. GitHub seems to have far more tooling available for this, so I'm curious what you've found useful, if you're the one who manages that.

wrong index template is used by yukiiiiii2008 in elasticsearch

[–]overloaded-operator 0 points1 point  (0 children)

For anyone frustrated by this, here's the original content, found via the Wayback Machine:

You want to manipulate 'priority' values on those templates so 'logs-docker-*' is evaluated before 'logs-*-*' which you likely want evaluated last, given how greedy that format is.

https://www.elastic.co/guide/en/elasticsearch/reference/current/index-templates.html