Hey, guys!
In recent weeks, I have been attempting to coordinate with the other devs on my team and lay out the structure and earliest implementation of a CI / CD pipeline which will be used to guide and optimize the development process. A few early challenges I have been working through include:
- Determining what type of access roles my devs need to have to the repository to be able to properly utilize the CI / CD pipeline and action workflows I am defining for them
- Selecting impactful inputs that provide the devs configurability, without creating extra work for no reason
For the first item, I am in the process of determining whether GitHub free version is capable of allowing collaborators on a project repo to access repo settings (variables, secrets, etc). If not, then I am considering renewing my ‘student’ access to GitHub enterprise features – as described here:
https://github.com/education/students
In regards to effective inputs, I am in the middle of onboarding my devs to the new workflows and I am getting feedback from them during the initial implementation. I am hoping that our conversations will help determine what inputs are necessary or missing.
I am finding that building a CI / CD pipeline is an iterative process that requires robust feedback from the ‘customers’, which in this case are the developers. Still in the thick of it, but I am hopeful that my team and I can create an end product that will serve us effectively for the rest of our time in the course sequence!
Best Regards,
Kenneth Huddleston
