After 15 years, I use Outlook as my build pipeline • Hacker News Board

Re: After 15 years, I use Outlook as my build pipeline

#41

Post by TechSquidTV » Wed, Nov 26, 2025, 3:39 PM UTC

throw-the-towel wrote: post #27

easterncalculus wrote: post #20

I don't know if Telegram, Slack, Discord, GitHub Actions, GitLab CI, Jenkins, or Kubernetes will be around (or without massive breaking changes) in 20 years, but email absolutely will be.

TIL that Jenkins was only released in 2011. Feels like it's been around since forever.

2011 was a huge year for tech/devops. I feel like so much of what we do now started right then for some reason.

Re: After 15 years, I use Outlook as my build pipeline

#42

Post by formerly_proven » Wed, Nov 26, 2025, 3:40 PM UTC

slackfan wrote: post #23

Traubenfuchs wrote: post #2

[flagged]

If your build pipeline is anything more than a deploy.sh file containing go build binary scp binary root@server:/deploymentlocation you are a hack, a fraud, an overengineer and someone who should NOT work as software or devops engineer.

Look what “real” devops engineers have demanded respect for. They have played us for absolute fools!

Re: After 15 years, I use Outlook as my build pipeline

#43

Post by charles_f » Wed, Nov 26, 2025, 3:43 PM UTC

inetknght wrote: post #38

1970-01-01 wrote: post #32

Good. The next step is turning that into an OS. From there, you should be able to take it further and fully support virtualization.

...but why?

To run Doom, what else?

Re: After 15 years, I use Outlook as my build pipeline

#44

Post by gdulli » Wed, Nov 26, 2025, 3:43 PM UTC

ramon156 wrote: post #34

corysama wrote: post #9

I knew a guy who would brag that he used Outlook as his build system 20 years ago. Builds would take 9 to 24 months depending on the complexity of the project. But, as the CTO of a mid-sized software company, it worked for him.

> Builds would take 9 to 24 months depending on the complexity of the project. I might be stupid, are you saying a build would take 9 to 24 months to finish?

They're saying he used Outlook to assign a project to a team.

Re: After 15 years, I use Outlook as my build pipeline

#45

Post by usrusr » Wed, Nov 26, 2025, 3:47 PM UTC

hshdhdhj4444 wrote: post #29

throw-the-towel wrote: post #27

Earlier quoted context omitted.

TIL that Jenkins was only released in 2011. Feels like it's been around since forever.

I think that might be because it was called Hudson before that I believe. Unless that was a different project altogether?

Same project, rebranded around Oracle. Basically MySQL/MariaDB without the alliteration.

Re: After 15 years, I use Outlook as my build pipeline

#46

Post by Traubenfuchs » Wed, Nov 26, 2025, 3:51 PM UTC

micahdeath wrote: post #36

Traubenfuchs wrote: post #2

[flagged]

I like [x]copy deployments personally, then you have 1 command =)

I bow!

We had that at my first job where I deployed .war to a remote production tomcat directly from eclipse with one tool button click.

Zero lines of code even, depending on definition.

Re: After 15 years, I use Outlook as my build pipeline

#47

Post by Traubenfuchs » Wed, Nov 26, 2025, 3:52 PM UTC

slackfan wrote: post #23

Traubenfuchs wrote: post #2

[flagged]

If your build pipeline is anything more than a deploy.sh file containing go build binary scp binary root@server:/deploymentlocation you are a hack, a fraud, an overengineer and someone who should NOT work as software or devops engineer.

2 commands -that‘s 33% better than my solution!

Re: After 15 years, I use Outlook as my build pipeline

#48

Post by Traubenfuchs » Wed, Nov 26, 2025, 3:54 PM UTC

afavour wrote: post #6

Traubenfuchs wrote: post #2

[flagged]

Wait, my docker registry has no authorization? Uh oh

The executing system provides an authenticated kubectl.

Re: After 15 years, I use Outlook as my build pipeline

#49

Post by uliqquel » Wed, Nov 26, 2025, 3:57 PM UTC

ramon156 wrote: post #34

corysama wrote: post #9

I knew a guy who would brag that he used Outlook as his build system 20 years ago. Builds would take 9 to 24 months depending on the complexity of the project. But, as the CTO of a mid-sized software company, it worked for him.

> Builds would take 9 to 24 months depending on the complexity of the project. I might be stupid, are you saying a build would take 9 to 24 months to finish?

Maybe the build system was him sending the email to some factory that would encode it into the silicon of a chip and ship the chip back to him.

Re: After 15 years, I use Outlook as my build pipeline

#50

Post by bux93 » Wed, Nov 26, 2025, 4:05 PM UTC

jbverschoor wrote: post #24

/Mail/Messaging in SMTP, and you have what it is: A message broker and queue. It has durability, retries, everything

SMTP is even a transport for SOAP

It was really fun using filters in Pegasus Mail (no SOAP) to automate mailing lists, PGP key signing with e-mail validation etc.