SKILupDay

   6 years ago
#SKILupDayObservability #SKILupDayDiscussing Observability and Upskilling in DevOps ahead of SKILup Day
Anshul Lalit
Who owns your Continuous Delivery Pipeline? :)
𝓐𝓷𝓾𝓻𝓪𝓰 𝓢𝓱𝓪𝓻𝓶𝓪
Its everyone success in organization so everyone in org. is responsible. A valuable business requirement helps to create valuable software. And when software gets right feedback at right time, its going to generate value for organization.
Garima Bajpai
Treat Cd pipeline as product and Cd product owner is responsible for incremental features- align it with business goals
Mitesh Soni
COE should own it for Continuous Improvement of the Pipeline as per my view!
felipe dueñas
Is there a Continuous delivery main stakeholder?
Garima Bajpai
@mjenkins70718 interesting, can you elaborate
Anshul Lalit
@bajpaigarima1 Second that! Please elaborate @mjenkins70718

(edited)

Mitesh Soni
@bajpaigarima1 @alalit Usually Improvement stops when Pipeline is stable. Everyone is Happy with the current state where even quality teams are fine with Pipelines as it exists. If COE team is involved then they look for current trends and improvement based on technology and tool
Siddharth
there are new roles emerging like the Continuous Delivery engineer / manager which may own. however I think the #productowner are also coming up for product driven organization. Last but not the least, segregate ownership for each pipeline. Can be many but avoid #devops
Garima Bajpai
we define north star for cd pipeline product , create leader action plan for the product, define taxonomy of the product & create a charter to set accountability

(edited)

Mark Peters
Shared ownership, everyone must be responsible for contributing, through feedback, from dev to prod, developing team owns their code, their development. Ops owns shared environments, stable delivery
Mark Peters
@mjenkins70718 If improvement stops, you are done. Doesn't have to be big improvements, small steps forward
DevOps Institute
Is there such a thing as a Continuous Integration (CI) ecosystem?
Siddharth
Ecosystem as per dictionary meaning is, a biological community of interacting organisms and their physical environment. Similar goes for #DevOps environment where we have sub #ecosystem for #ContinousIntegration #ContinousDelivery #ContinousDeployment and many more.
Marc Hornbeek, DevOps_the_Gray esq.
Continuous Integration ecosystems are a combination of developers working with code version management systems and integration practices that ensure each commit meets commit quality criterion prior to merging changes into the trunk and avoid breaking the trunk.
Mark Peters
Look at @mhexcalibur comment about #ContinousIntegration and substitute #ContinousDelivery. Its about processes and collaboration to remove constraints and add flow/feedback
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
Version control server + Build server+Code analysis tool+ Artefact repository server = #ContinousIntegration ecosystem !!
Mitesh Soni
CI has lot of integral part in it such as code inspection, unit tests, and build and hence it is a complete ecosystem on its own.
Romnick Acabado
CI ecosystem creates frequent, small, incremetal integrations and it enables a release through many individual changes. This ecosystem covers version control repository activities to artifact repository.
felipe dueñas
Continuous delivery includes creating the foundations of automated deployment pipeline
DevOps Institute
What are the key components in the Continuous Delivery ecosystem?
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
Exploration (CE), Continuous Integration (CI), Continuous Deployment (CD), and Release on Demand,
Mitesh Soni
Continuous Delivery, Continuous Deployment, Continuous Improvement and Continuous Innovation
𝓐𝓷𝓾𝓻𝓪𝓰 𝓢𝓱𝓪𝓻𝓶𝓪
It started with Continuous valuable Idea , Integrated business thought, CI, CD, CT and Final delivery
Helen Beal 🐝
Portfolio mgmt, product backlog, artifact repository, version/source control, build/CI tool, continuous testing suite, deployment automation (breathes), service desk and monitoring... from idea to value realisation. Put Value Stream Management around the whole lot.
Romnick Acabado
Elastic architecture, continuous integration, continuous deployment, continuous testing and continuous monitoring, continuous automation and governance.
Anshul Lalit
Sprints > Code > CI > Version Control > Automation on test/deployment > UAT > Security > Release Management > Monitoring
felipe dueñas
Continuous Delivery Director can orchestrate most continuous delivery operations through various direct and indirect integrations
Marc Hornbeek, DevOps_the_Gray esq.
Continuous Delivery ecosystems are comprises of collaborative cultures using integrated processes orchestrating interconnected tools designed to reduce bottlenecks and improve release flow.
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
I think the future of cd ecosystem is automation ecosystem !!
felipe dueñas
CD helps ecosystem helps overcome the complexities, obstacles, and demands of business needs.
Garima Bajpai
Future of Cd ecosystem will be based on DevOps practices - which will consist of Next-Gen data capabilities, bridging multi-cloud env
Mark Peters
clear pipeline structure, understood and agreed upon processes
DevOps Institute
Why are Continuous Delivery Ecosystems Important?
Garima Bajpai
Improving purposefulness of deployment of feature
Helen Beal 🐝
Because a DevOps toolchain consists of many parts that need to interoperate necessarily creating an ecosystem
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
Because it is the center of DevOps transformation !!
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
Additionally, it provides the key role in delivering the product/services faster !!
𝓐𝓷𝓾𝓻𝓪𝓰 𝓢𝓱𝓪𝓻𝓶𝓪
Its heart of devops transformation. one of continuous. This enable to understand value of code
Mark Peters
guardrails for your practices, keeping effort focused in the right direction
Mitesh Soni
It helps in culture transformation initiatives
Romnick Acabado
It is important to produce software in short cycles while ensuring that software can be reliably released at any time. This will help in building, testing and releasing software faster and more frequently. It improves the value stream flow .
Dheeraj Nayal - Organizer of Global SKILup Day🦸‍♂
The ecosystem also brings the buy-in from clients/enterprise for better products/applications !!
Garima Bajpai
@TinyCyber totally - keep the value of the features inline with the effort
Anshul Lalit
Faster feedback loops, quick turnaround
Siddharth
teams need to move away from traditional development models to new ways of working which is the continuous delivery ecosystem at present for future benefits #devops

(edited)

James Wasson
@alalit That's what I was typing. I agree!
Mark Peters
@pareeksiddharth Traditional is such a rough word, looking for continuous improvement, less resistance
Mark Peters
@DevOpsLeaderPH Does the ecosystem determine the cycle or does the short cycle determine which ecosystem to use?
Romnick Acabado
@TinyCyber Great tricky question, for me it always starts with setting the vision, measurements and identification of the outcomes that you want to achieve. Ecosystem has a big impact to influence shorter cycle and better feedback loop. Not sure if my answer makes sense. ;)
Siddharth
@TinyCyber could be said. Agree. Guess we need to traditionally move away from the word #tradional now :D #devops
Marc Hornbeek, DevOps_the_Gray esq.
Continuous Delivery Ecosystems are important to ensure software deliveries meet the business goals for agility, stability, efficiency, security, quality and team satisfaction.
Mark Peters
@pareeksiddharth heh, when you call your stakeholders traditional, they just get more so
Mark Peters
@DevOpsLeaderPH agreed! Vision drives value, improved feedback drives shorter cycles, less expensive improvement, and back to value
felipe dueñas
It driveS performance improvements in software delivery, and prior research suggested it could even improve culture.