Tell me you're using Perforce and thus have a hard...
# voxpupuli
j
Tell me you're using Perforce and thus have a hard, human-driven process (b/c Perforce!) without mentioning it specifically in your reply to a Git PR:
Yeah, the acceptance CI tests can't run on forks, needs to be on a branch. Just a double-check as part of the approval process. I didn't expect anything to go wrong, though I had to rerun a bunch for provisioning issues.
j
The process is mostly automated, but it requires authorization by an employee to create the branch so that we can inherit the secrets needed for the acceptance tests. It's unfortunately a long-standing issue with PRs on forks that we haven't been able to solve without using this automation to spin up separate branches. Unless you were referring to the provisioning. The provisioning is automated, but I have found that sometimes provisioning fails when the load on the service is busy and you need to kick the automation a few times to get it past that issue so it can run tests. Happy to talk more about the process I use to spin these up, if it's helpful! (Or I can silently back away homer if the desire was more to just do some corporate bashing and get some frustrations out...)
j
Yeah sorry I guess I was voicing my years of trauma from Perforce promising they supported Git now, and then pushing in their tech which broke every single automation... and where every bug report I opened on this was answered with "Have your branch manager..." "Have your merge manager..." blah blah seriously burned by this company who completely could not grasp the concept of designing humans out of the way
The idea that a human should be a monkey there to push a button, and that any tech which can do it without the human should be engineered out of existence seems to underly everything Perforce believes in. And I'm not just speaking from bug reports either, I'm talking about long-term business meetings and technical deep-dives where we realized that this wasn't technology, this was religion and Perforce would never, ever understand.
fwiw, I mostly feel sorry for Puppet employees who obviously would have a different mindset forced to work under such conditions
j
I'm fairly new in the Perforce employee world... and there are a lot of 'red tape' type of things for security and compliance, but the push has definitely been to automate as much as possible. Sometimes, the automation does cross the line past where security wants it to and the effort to somehow get everybody happy is not as easy as having something with a button that is pushed by a human. I agree that, as a company selling automation tools, automation should be the way you push for. What if the human isn't able to be there on a given day? How does the work get done? Or if you need to change out people who are doing work, how to you make it easier to transition and capture the knowledge? This is what automation does so well... deterministic logic that captures processes and just works...
💯 1
j
I'm almost always responsible for security so I grok the considerations. My experience with Perforce was just a repeated return to "have a human do it" whenever we attempted to automate things, and the reps behavior in those accounts was so off-putting that I developed a really bad taste in my mouth around Perforce. Sorry for the noise in the channel, I was trying to be funny 😜 Thank you for all you do at Perforce to work with us in the community.
❤️ 1