If your users are external to the org then this probably doesn’t apply. However, if your users are internal, you give them a repo of their own and grant them access to publish to the pipeline.
That’s interesting. I assume there is still some review and approval process this has to go through? So it basically means you are on call constantly for unscheduled deployments?
Its not in place yet. I’m seeing it take shape. I don’t see how it can be successful on its own and will either lead to user teams adding their own Shadow IT or the skeleton IT Operations group balloon into a giant Shared Services outfit.
However, I thought I’d mention it as its the same mindset that lead to Devops, which was just a business reaction to finding a way to hire and maintain fewer IT roles. Its interesting to see the IT roles being pushed directly onto the users now.
If your users are external to the org then this probably doesn’t apply. However, if your users are internal, you give them a repo of their own and grant them access to publish to the pipeline.
That’s interesting. I assume there is still some review and approval process this has to go through? So it basically means you are on call constantly for unscheduled deployments?
Its not in place yet. I’m seeing it take shape. I don’t see how it can be successful on its own and will either lead to user teams adding their own Shadow IT or the skeleton IT Operations group balloon into a giant Shared Services outfit.
However, I thought I’d mention it as its the same mindset that lead to Devops, which was just a business reaction to finding a way to hire and maintain fewer IT roles. Its interesting to see the IT roles being pushed directly onto the users now.