upvote

points

by simonw15 hours ago |
comments
upvoteby mbreese15 hours ago|
next
[-]
Trac was great.

But, my first issue tracker was bugzilla. Setting that up was a bit of a pain, and it didn’t integrate well with anything, but it was very satisfying to see “Zarro Boogs”.

reply
upvoteby theshrike7945 minutes ago|
parent|
next
[-]
Bugzilla was too big/complex for pretty much every company I ever worked in :D

Trac was perfection. Self-hosted and just the right amount of features.

reply
upvoteby bombcar13 hours ago|
parent|
prev|
[-]
Bugzilla was relatively painless to setup but it already had a bit of the Jira going on - in that it had SO MANY OPTIONS!

I remember being interested in MantisBT and a few others (Launchpad for BZR?) mainly because it seemed they made a bunch of decisions for me.

reply
upvoteby mbreese13 hours ago|
parent|
[-]
It's a bit fuzzy, but what I remember was getting it running was painless -- but there was a ton of effort in getting it configured.

In retrospect, it was probably the flexibility of projects like Bugzilla that heralded the "opinionated" approaches to software that followed. In many ways software also follows the patterns of the language they are written in . Bugzilla was written in Perl, so of course there is more than one way to do anything.

I had forgotten about Mantis, but that was the first tracker that the non-programmers in our group were comfortable using. It is a bit funny how quickly we all migrated to Github as a larger community as it became the default for just about everything.

reply
upvoteby bombcar12 hours ago|
parent|
[-]
It's fun when you find these various things still in the wild - they're all still out there!

https://dwarffortressbugtracker.com/my_view_page.php

reply
upvoteby vbernat9 hours ago|
prev|
next
[-]
I've switched to GitHub from Trac because of spam. Despite using Akismet and bayesian filters, on a small instance, there were still several spam tickets if you didn't require an account (for the details, https://vincent.bernat.ch/en/blog/2011-migrating-to-github). I am a bit amazed that Trac still exists and is maintained today.
reply
upvoteby the_mitsuhiko15 hours ago|
prev|
next
[-]
Trac is in many ways what motivated me to build out an app in Python rather than in PHP for redistribution. It had a great plugin system!
reply
upvoteby noir_lord15 hours ago|
prev|
next
[-]
I liked bitbucket, it did its job, it didn’t break for me and I preferred mercurial.

Employers used GH so I switched but even now I use GH as a dumb git endpoint and do all my build/deploy with docker and shell scripts so switching for me is extremely cheap.

For work stuff I’ll use whatever I’m paid to use if I don’t get to make the call just as it was back in the svn days.

reply
upvoteby dijit15 hours ago|
prev|
next
[-]
Weirdly, I also have fond memories of Trac despite absolutely despising it at the time for “doing too much and excelling at nothing as a result”.

I guess that award goes to Gitlab now, which I will probably also remember fondly.

reply
upvoteby saghm15 hours ago|
parent|
next
[-]
I like Gitlab fine by ignoring pretty much everything it does other than host the source code and let me view READMEs in the browser (and for work, also merge requests). In general the more I have to use anything other than those, the more frustrated I get, which was also how I felt about Github in the past. I'm not sure I've ever had a non-frustrating experience when trying to set up a CI pipeline on any platform, so I guess Gitlab's CI isn't any better or worse than others in that regard. There are an awful lot of tabs on the left any time I look for something through those menus though, most of which I don't know what they do and I would probably not be happy to have to learn.
reply
upvoteby dijit7 hours ago|
parent|
[-]
> I'm not sure I've ever had a non-frustrating experience when trying to set up a CI pipeline on any platform, so I guess Gitlab's CI isn't any better or worse than others in that regard.

Honestly, Gitlab's CI is one of its killer features.

I really enjoy Gitlab CI.

But, nearly everything else (kubernetes management, AST, AI "DUO", work items, milestones, snippets, workspaces, "operations", "security dashboards", "value stream managements", "service desk") - ugh, awful.

I guess some of the artifact repository stuff is nice, but like; their terraform repository is probably the worst of all choices, all the downsides of the HTTP state backend and no upside..

It's so hit and miss; but! the CI is actually good..

reply
upvoteby saghm1 hours ago|
parent|
[-]
I don't hate using Gitlab CI once it's set up; I just hate "put shell scripts in YAML to define how this should work". The least annoying experiences I've had with them are when every entry is literally just a single line that invokes an external script; shell scripting is already annoying enough without having to also spend the time to understand a YAML schema for what order they get invoked in and what environmental variables are in scope (not to mention what the implicit inputs are; a few months ago I tried to add a task to run some check on the commit message for an MR, and I found that even on repositories where the merge commit option is disabled in favor of squashing or fast-forwarding, the top commit message is still a merge commit).
reply
upvoteby dijit1 hours ago|
parent|
[-]
Ah, super valid point.

I use the command invocation to run python scripts. I tend to believe that CI is just a controlled way to do things you would do locally.

reply
upvoteby jamesfinlayson13 hours ago|
parent|
prev|
[-]
> I guess that award goes to Gitlab now

Painfully true - I remember a company I was at replacing GitHub and a bunch of other tools with GitLab because it was better to pay for one tool that does it all. Kind of.

reply
upvoteby 15 hours ago|
prev|
[-]
deleted
reply