Anyone out there good with Jenkins that might be able to point me in the right direction?
I'm running Jenkins in docker, persisting the home directory, but every single restart of the container causes all jobs to fire off fresh. Even jobs that are supposed to be run manually (and require user parameters) start running and fail.
I can find zero people on the internet talking about this issue. Is this expected behavior?
I'm safely restarting Jenkins, not just restarting the container.
Started over fresh (again) using jest for testing and was actually able to get much farther along in testing than ever before!
So it looks like I've got it finally figured out. Wheeeeeew!
Everything is broken from the top to the bottom to all the tools in the middle. Webpack, mocha, jest, vuetify, vue.. literally every package appears to be at fault.
This is nuts!
I don't want to keep running without vue tests, but it looks like I just don't have any other option.
PSA: Don't let your web serve serve your .env files. Please!
Just write "DB_USERNAME filetype:env" in @google search and take a cup of coffee :D Enjoy :D @laravel env files publically exposed in the browser.
Placing env files on root is not a good idea :D
I've been working on implementing laravel-echo-server at work, and this just dropped today.
I am definitely going to try it out!
Sending regards to an ex-employer
I came to a realization a week or two ago about how I should have been proud to work for a local company. I left them a year and a half ago due to my salary requirements changing.
The company is run by people who genuinely care about the business and all the employees a great deal, but I joined the company in the middle of some IT drama. The bad apples leaving at that moment kind of tinted my view of what was going on.
I actually felt compelled to send my ex-boss an email.
In a public chat someone asked (written with this capilization) "Is anyone else excited for Macos Mojave?"
In my head I pronounced "Macos" like tacos. I was completely lost and had to google what product I was missing.
I guess this confirms that, despite using a Mac for work, I am not a "Mac person."
wtfnode is _awesome_! it wraps a js script and then tells you what event handlers were left dangling that caused nodejs to hang and never exit https://www.npmjs.com/package/wtfnode
QWOP Cosplay: https://www.youtube.com/watch?v=gfHCUM_OBCc
I guess this is five years old but I hadn't seen it before! So fun.
Linus acknowledging his toxic behavior is a step in the right direction. I'm glad he's finally realizing what people (especially marginalized people) have been telling him, at great personal cost to themselves, for *years.*
While he's taking time to work on himself, I hope the Linux and open-source communities do likewise, and interrogate why we let his toxic behavior damage our community for so long.
What the heck is up with r/linux?
Over the past few weeks I've realized just how far apart my views are from other people in tech that post to r/linux.
There was a hubbub about Redis changing the terms of master and slave to something else - r/linux hated that. "The sjw's are winning!" was the cries.
Now the CoC for the linux kernel and Linus talking about empathy again rallies screams of "The sjw's are winning!"
How are these people in tech and not realizing how rough it is for women and minorities?
Resource suggestions for dealing with turbulence at work?
My team at work is going to be forced to change technologies used at work specifically because we are going to add two people to the team who want to use something else.
This also signals that there may be more changes coming as they get exposed to other things we're using (linux) that they are not familiar with.
Anyone have resources on how to deal with these kinds of ups/downs at work? I am alternating between despair and rising to the challenge.
I'm a Devops tech guy working with docker, programming, linux, and other tech I find time for!
Just trying to be a good person. Be brave, be honest, be kind.
This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!