I see this as typical of organizations that value creating a more inclusive environment for their developers.
Also, for what it's worth, Jenkins changed their terminology to use "agent" instead of slave in 2020 [0]. These efforts might seem futile in isolation, but they add up over time.
[0] https://www.jenkins.io/blog/2020/06/18/terminology-update/
An organization that cared more about inclusivity than compliance would have done more.
As of February 2016, references to "slave" in documentation began to be replaced with "agent": https://issues.jenkins.io/browse/JENKINS-27268
The comment I'd make is that this appears to have been settled nearly eight years ago in this particular context, and that maybe you should give it a rest.
It was "settled" in that we're all agreed it's obviously incredibly stupid but not worth fighting over and getting called racist.
The good news is that "master vs mainline" was so embarrassing that even the people who push this stuff realized they overreached and have settled down since.
You seem to misunderstand. My objections to the change are minimal. It is the incompleteness of the change that is remarkable.
I feel like I understand well enough, I feel you've misrepresented the magnitude of the issue.
Then you met with the Scrum Master to discuss planning?
I do not see justification in reworking our CI/CD, procedures, muscle memory, et. al. over contemporary politics.
* Jenkins worker
Maybe if they spun up a new cluster with new hostnames it’d say that. It doesn’t.
The same terminally online leftists who pushed for the change away from using these words have spent the last couple of weeks explaining on X how the actual slavery practiced by Huttis is actually not that bad.
Re:Trunk-Based Development
by willsmith72 on Sunday January 21, 2024 @08:18PM
(#39084929)
huttis? you mean like jabba?
I'll bet good Republic credits that the Hutts advocate for Gitflow.
At $ORGNAME we went through some mild hassle to use “main” on new repos, leading to assorted mild wastes of time when people get things wrong (especially when we don’t use it).
The inoffensively named branch is then pushed to gitlab-master.orgname.tld and, typically, a build pipeline runs on some kind of Jenkins slave.
It occurs to me that one could make some sort of comment about this. My own comment is that this is somewhat typical of compliance-oriented workflows.