SKILupDay

From ideation to development to release.This aims shorter feedback loop and end-to-end automation. Everything means continuous integration, continuous delivery, continuous deployment, continuous testing, continuous monitoring, continuous governance,automation

“if it hurts, do it more often, and bring the pain forward.” Being Agile/Continuously inspect/adapt in every aspect of value delivery and improve time to value instead having delayed perfection /lost opportunity

progressive culture

automated environment with a continuous learning mindset !!

a foolish idea #devops

Continuous Everything in the context of Continuous Delivery Ecosystems refers to the seamless, controlled integration of people, process and tools to enable uninterrupted flow of changes with minimal resistance and with confidence.

I once did a survey called 'How Continuous is Your DevOps?' and then put the research data into a report I called 'DevOps and All the Continuouses' thereby entirely butchering the English language

@pareeksiddharth ah! that is interesting

Cultural transformation

frictionless with agility and anti-fragility

Love the idea as it is "law of nature "

Continuous "Improvement" that leads to Continuous Innovation

a great concept driven with a vague idea facing challenges of cultural transformation.

https://www.crowdchat.net/s/662b0

Born this way !!

The Greatest Show

Come Toghether!

Despacito...continuously improving little by little is the path to a system you can love :-)

Boom Boom Pow (Black Eyed Peas)

(You Drive Me) Crazy - Britney or The Fine Young Cannibals

Wish i could say Just the way you are :) + 1 to Despacito

A custom composition "Every Build You Break..."

Every Build You Break
- https://youtu.be/fVc_VPMsj7A hear it out ;)

Lyrics are:
Every bug you take
Every push you make
Every build you break
Every log you erase
I’ll be watching you…

#devops

@pareeksiddharth lol, I just posted that, its a great one!

@alalit A Song by programmers, for programmers :D
#devops

@pareeksiddharth indeed! Its a fun composition.

We could be Heros ... We go hideaway in daylight
We go undercover when under sun
Got a secret side in plain sight
Where the streets are empty
That's where we run
Everyday people do
Everyday things but I
Can't be one of them
I know you hear me now
We are a

https://www.youtube.com/watch?v=zRUwU6ZE-QA :-)

@PlanetKristine Love it !!

Anything available already in org, Value, flow, and Cost

money ...

Budget always takes the priority unfortunately before considering what matters !!

Talk to people who have already done it - all organizations need to share more about their toolchain architectures

It is important to define a set of standards for each case

Purpose which it fulfills towards the incremental features you need, keep the flexibility intact , no vendor lockin :-)

Architect it so that you can use a value stream management tool to tie it all together and get end-to-end cycle time data and insights into your constraints

Experience defines means, budget defines tools

This is a great question. Important to know your goals and pick a combination of tools that best suit your specific situation. Everyone has budget constraints. Need to be careful to pick a toolchain you can afford not just a tool.

I choose tools basis upon organization #culture #people #process #technology.
Maturity of your #ContinousIntegration

List is endless.

Pipeline started working at night and custome visit was on next day ... still not aware what was the issue and how it worked

answer is easy introducing it . Only the timeline & teams were different :) #devops

best its introduces value traceability and a choice to release on demand based on insights

Best that it breaks often, and worst that it breaks often. Perspective, perspective! :)

@alalit complete agree its awesome in all the cases

My best experience with CD pipeline: large telco system manufacturer reduced time to delivery from 18 month waterfall releases to daily DevOps release candidates. Worse: A large insurance enterprise implemented CD w/o enough testing. Quality problems caused project cancellation

@alalit that's awesome! Love it

Devs use pipeline as personal playground and regularly change gates without informing anyone. Sec: Why haven't you run security checks in 3 weeks? Dev: It took to long, now we only do security checks when we know its not a problem

gazillions I guess :)

(edited)

100+ i know and still counting

always one more.

Toollist ++

my guess is 120. :)

@alalit Totally!

I am counting at the moment. Will let you know once we reach towards the end of the year 2020 :D #Devops

infinite... because they all keep changing and people build their own. But typical pipelines seem to have between 10 to 20 distinct tools

Is it like counting a jar of beans?

Do we really need to know? It should be requirement specific rather than choosing from the bucket and not knowing which tools align with your requirements and then losing $$$ from your investment.s

@mhexcalibur People need to share their reference architectures so that the community can learn from each other

Sometimes yes to understand what we need make inhouse reuse and buy

It is not important

@felidue I second, tools are build for purpose and the purpose is focal to the practice

@BealHelen lol