Heads up if you’re using Alpine images to host your services or run build pipelines. Alpine’s packages are going to be less current unless some others maintainers are found to pick up the slack.

  • stevecrox@kbin.social
    1·
    1 year ago

    @ergoplato I didn’t suggest that.

    Personally I don’t think its ego. I think you have two issues.

    The first is people go through stages learning DevOps. Stage 1 has people deploy a CI because its cool, they build a few basic pipelines and then 90% of people get bored. The 2nd stage is people start extending those pipelines, it results in really complex pipelines requiring lots of unique changes based on the opinion of the writer. You move to the 3rd stage when your asked to recreate/extend for a new project and realise how specific your solutions are.

    Learning how to make minor tweaks and hook in a few key points to get what you want takes years. Without that most packagers will want to make big changes upstream which won’t go down well.

    The second issue, I have met quite a few developers who become highly stressed when the build system is doing something they haven’t needed to do or understand.

    A really simple example I have a Jenkins function which I tend to slip into release pipelines, it captures the release version and creates a version in Jira.

    I normally deploy it first as a test before a few other functions to automate various service management requirements.

    Its surprising how many devs will suddenly decide every problem (test failed, code failed review, sharepoint breaks, bad os update, etc…) is due to that function.

    For me this little function is a test, if the team don’t care I will work to integrate various bits. If they freak out, I’ll revert decide if it is worth walking them through the process or walk away.