KISS 🇺🇦

Stop the war!

Stop the war in Ukraine! Fuck putin!

More information is at: https://war.ukraine.ua/.

There is a fund to support the Ukrainian Army: https://savelife.in.ua/en/donate/, and there is a special bank account that accepts funds in multiple currencies: https://bank.gov.ua/en/about/support-the-armed-forces. I donated to them. Please donate if you can!

Killer putin

Killer putin. Source: politico.eu.

Arrested putin

"It hasn't happened yet, but it will happen sooner or later. Beautiful photo, isn't it?" Source: twitter.

Jenkins doesn't run as a LaunchAgent?

| comments

If you are interested in Jenkins and followed my post about setting it up in a virtual machine, you should be totally fine. However, when I was messing with it, I had an issue when the jenkins agent wouldn’t start:

1
2
3

launchctl load ~/Library/LaunchAgents/org.jenkins-ci.plist
launchctl load ~/Library/LaunchAgents/org.jenkins-ci.plist
/Users/Shared/Jenkins/Library/LaunchAgents/org.jenkins-ci.plist: Operation already in progress

Operation already in progress implies the agent is already running, even though:

1

pgrep -fil jenkins

prints nothing, which means no jenkins process runs. There is nothing is the Console.app logs.

Turns out the issue is that I accidentally used the sudo launchctl load … command before, and the logs in /var/log/jenkins/ had the root permissions. Jenkins (or is it launchd?) doesn’t want to start in that case. So you’ll need to do this:

1
2

launchctl unload ~/Library/LaunchAgents/org.jenkins-ci.plist
sudo chown jenkins /var/log/jenkins/*

The second command reverts the log files ownership back to the jenkins user. Now launchctl load works fine. Enjoy!

Comments