A gaskiya ma, Ivan sau da yawa ya yi dariya game da ƙoƙarin da abokan aikinsa na sa ido suka yi. Sun yi matukar kokari wajen aiwatar da matakan da mahukuntan kamfanin suka umarce su da su cimma. Sun shagaltu da cewa ba sa son wani ya yi wani abu.
Amma bai isa ba ga gudanarwar - koyaushe suna yin umarni da ƙarin sabbin awoyi, da sauri sun daina amfani da abin da aka yi a baya.
Kwanan nan, kowa yana magana game da LeadTime - lokacin isar da fasalolin kasuwanci. Ma'aunin ya nuna mahaukacin lamba - kwanaki 200 don isar da ɗawainiya ɗaya. Yaya kowa ya fashe da aah suka daga hannu sama!
Bayan wani lokaci, a hankali hayaniyar ta mutu kuma gudanarwa ta sami umarni don ƙirƙirar wani ma'auni.
Ya bayyana sarai ga Ivan cewa sabon ma'aunin zai mutu cikin nutsuwa a cikin duhu.
Lalle ne, Ivan ya yi tunani, sanin lambar ba ta gaya wa kowa komai ba. Kwanaki 200 ko kwanaki 2 - babu bambanci, saboda ba shi yiwuwa a ƙayyade dalilin ta lambar kuma fahimtar ko yana da kyau ko mara kyau.
Wannan wani tarko ne na ma'auni: da alama sabon awo zai faɗi ainihin wanzuwar kuma ya bayyana wani sirrin sirri. Kowa yana fatan hakan, amma saboda wasu dalilai babu abin da ya faru. Ee, saboda bai kamata a sami sirrin a awo ba!
Ga Ivan, wannan mataki ne da ya wuce. Ya fahimci haka don ma'auni, kuma duk asirin dole ne a nemi a ciki , i.e. shine wannan ma'aunin an yi shi ne.
Don kantin sayar da kan layi, abin da ke da tasiri zai zama abokan cinikinsa waɗanda ke kawo kuɗi, kuma ga DevOps, za su kasance ƙungiyoyin da ke ƙirƙira da rarraba rarraba ta amfani da bututun mai.
Wata rana, zaune a cikin kujera mai dadi a cikin zauren, Ivan ya yanke shawarar yin tunani a hankali ta yadda yake so ya ga ma'aunin DevOps, la'akari da gaskiyar cewa abin da ke tasiri shine ƙungiyoyi.
Manufar DevOps Metrics
A bayyane yake cewa kowa yana so ya rage lokacin bayarwa. Kwanaki 200, ba shakka, ba su da kyau.
Amma ta yaya, wannan ita ce tambayar?
Kamfanin yana ɗaukar ɗaruruwan ƙungiyoyi, kuma dubban rarrabawa suna bi ta bututun DevOps kowace rana. ainihin lokacin bayarwa zai bayyana azaman rarrabawa. Kowace ƙungiya za ta sami lokacinta da halayenta. Ta yaya za ku sami wani abu a cikin wannan rikici?
Amsar ta taso a zahiri - muna buƙatar nemo ƙungiyoyin matsala kuma mu gano abin da ke faruwa tare da su da kuma dalilin da yasa yake ɗaukar lokaci mai tsawo, kuma mu koyi daga ƙungiyoyin "mai kyau" yadda ake yin komai cikin sauri. Kuma don yin wannan, kuna buƙatar auna lokacin da ƙungiyoyi suka kashe a kowane ɗayan DevOps yana tsaye:
“Manufar tsarin zai kasance zabar kungiyoyi ne bisa la’akari da lokacin da suka wuce tashoshi, watau. Sakamakon haka, ya kamata mu sami jerin umarni tare da zaɓin lokaci, ba lamba ba.
Idan muka gano adadin lokacin da aka kashe a kan tsayawar gabaɗaya da kuma lokacin da aka kashe a kan raguwa tsakanin tsayawa, za mu iya nemo ƙungiyoyi, mu kira su kuma mu fahimci dalilan dalla-dalla kuma mu kawar da su, "in ji Ivan.
Yadda ake ƙididdige lokacin bayarwa don DevOps
Don ƙididdige shi, ya zama dole a zurfafa cikin tsarin DevOps da ainihin sa.
Kamfanin yana amfani da ƙayyadaddun tsarin tsarin, kuma ana iya samun bayanai daga gare su kawai ba tare da wani wuri ba.
An yi rajistar duk ayyukan da ke cikin kamfanin a Jira. Lokacin da aka ɗauki wani aiki, an ƙirƙiri reshe don sa, kuma bayan aiwatarwa, an yi alƙawarin zuwa BitBucket da Buƙatun Buga. Lokacin da aka karɓi PR (Request Pull), an ƙirƙiri rarraba ta atomatik kuma an adana shi a ma'ajiyar Nexus.
Bayan haka, an fitar da rarraba a kan tashoshi da yawa ta amfani da Jenkins don bincika daidaiton ƙaddamarwa, gwajin atomatik da na hannu:
Ivan ya bayyana daga wane tsarin abin da bayanai za a iya ɗauka don lissafin lokaci a tsaye:
- Daga Nexus - Lokacin ƙirƙirar rarrabawa da sunan babban fayil ɗin da ke ɗauke da lambar umarni
- Daga Jenkins - Lokacin farawa, tsawon lokaci da sakamakon kowane aiki, suna tsayawa (a cikin sigogin aiki), matakai (matakan aiki), haɗi zuwa rarrabawa a cikin Nexus.
- Ivan ya yanke shawarar kada ya haɗa Jira da BitBucket a cikin bututun, saboda ... sun fi alaƙa da matakin ci gaba, kuma ba don ƙaddamar da rarrabawar da aka gama akan tashoshi ba.
Dangane da bayanin da aka samu, an zana zane mai zuwa:
Sanin tsawon lokacin da ake ɗauka don ƙirƙirar rarrabawa da kuma lokacin da aka kashe akan kowannensu, zaka iya ƙididdige jimlar farashin shiga cikin bututun DevOps gaba ɗaya (cikakken zagayowar).
Anan ga ma'aunin DevOps Ivan ya ƙare da:
- Adadin rabawa da aka ƙirƙira
- Raba rabon da ya “zo” wurin tsayawa da “wuce” tsayawar
- Lokacin da aka kashe akan tsayawa (zagayowar tsayawa)
- Cikakken zagayowar (jimlar lokaci don duk tsayawa)
- Tsawon lokacin aiki
- Lokacin hutu tsakanin tsayawa
- Downtime tsakanin ƙaddamar da aiki akan tsayawa ɗaya
A gefe guda, ma'auni sun nuna bututun DevOps sosai dangane da lokaci, a gefe guda, an ɗauke su da sauƙi.
Da gamsuwa da aikin da aka yi, Ivan ya gabatar da gabatarwa kuma ya je ya gabatar da shi ga gudanarwa.
Ya dawo a fusace da hannunsa kasa.
"Wannan fiasco ne, bro," abokin aikin ban mamaki ya yi murmushi ...
Kara karantawa a cikin labarin "".
source: www.habr.com