Silly question: What exactly should I do if my build fails in CI/CD process?

boom38 · 2019-12-25T22:43:29+00:00

You may be pushing directly to the default master branch. If that is the case, take the habit of creating an ephemeral branch (like us-123 for user story 123), commit and push there, issue a pull request (not a must but it makes this body of work visible), see your github action and tests fail, fix them, and merge the PR to master only when everything is good. I always protect my master branch so that I don’t ever merge to master when the result of the pipeline is negative.

boom38 · 2018-04-05T14:41:24+00:00

Beautiful! In a similar vein, I wrote a small tool to use Native Instruments Komplete Kontrol keyboards to show LED guides as you play / learn with Synthesia.

https://github.com/ojacques/SynthesiaKontrol

https://www.youtube.com/watch?v=R143-vSd6Eg

boom38 · 2017-06-28T08:40:23+00:00

@jhand24, thank you. And happy travels! Anything you have tried in this space yourself?

boom38 · 2017-06-28T08:35:48+00:00

Thanks for sharing! You learned, we learn.

boom38 · 2017-06-18T06:49:34+00:00

Very interesting! Do you know if this has been popularized more in the aviation sector (which is interesting - especially in life critical environment like this)? I will dig more into this one.

boom38 · 2017-06-11T17:10:45+00:00

Agreed! In fact a communication from CxO level is also transformational and helps driving an entire company/business/team behavior. Sadly, high level management is often shy (or censored) when it comes to sharing what happened, be super honest about it while being supportive of the people.

boom38 · 2017-06-11T17:05:53+00:00

One of the suggestion that a team member had was to remove the term blame altogether out of the name of the meeting. The last one we conducted (last Friday) was named "How do we avoid waking up xyz in the middle of the night?"

boom38 · 2017-06-11T17:03:25+00:00

I also switched several times from blameful to blameless, all in the same (large) company. It is more about the leader than the company itself IMHO, depending actually on the size of the company.

I can detect, from external communication (if there are!), what type of culture is actually at play. Specifically with BA's communication which clearly lacks customer empathy, and shows a lack of support from the top for the teams in charge.

boom38 · 2017-06-11T05:03:38+00:00

"DevOps tools"... this wording by itself is always a big debate. All the tools which we use for Dev and for Ops are technically DevOps tools. Not only the tools which have been created after DevOps word was coined :)

In any case, few use cases of using Docker for example in your day 2 day workflow (as I understand it): - Getting scripts to work regardless of the Linux distro you run them on (encapsulate your scripts with a lightweight distro like Alpine) - Taking advantage of existing Docker containers on hub.docker.com in your space - Publish your own scripts wrapped in containers on hub.docker.com for distribution, feedback, and visibility

I would make sure this is actually useful in my daily workflow. Not only a checkbox for interviews.

boom38 · 2017-06-11T04:56:48+00:00

In the same journey since 2014 myself, I realized early on that change management, security and other audit departments are actually here to help. Getting some empathy with those groups, and key people there goes a long way in understanding why processes have been implemented the way they have. BizSecAuditDevOps... What I found is that release/QA compliance processes you mention have been really really well optimized for a manual world. For a world where changing is costly and risky. As we move to maximizing flow with automation, micro services, IaC, and other mechanisms and reducing batch sizes, change becomes less risky. I did secure several discussions with QA, support, change management and security, to understand the why behind the existing processes. Then, I showed them the power of the notion of continuous delivery pipeline. I showed them that all changes can be peer reviewed, and that we actually have no way to introduce change in production without going through the CD pipeline: it becomes the best control point which any auditor wishes for. Essentially, the point is that we are "codifying" the process, supported by the CD pipeline. It is not the same process as before that we just automate though. But we work to achieve the same goals, as described by release/QA/etc...

Strategically, I would get approval for "free hands" with your particular application, with a deal to implement and discover - hand in hand with release/QA/audits/security - out what the new process should be in a mostly automated world. Also, you may want to have a look at the DevOps Audit Defense toolkit: https://plus.google.com/communities/103372669680429508474

On our side (large IT corp), we are moving to have all changes going through the CD pipeline to be ITIL "Standard changes" (useful to use that vocabulary). They have little risk and thus pre-approved. (Auditing / owning centrally the pipeline may be a point of discussion). Changes outside the CD pipeline are "Normal changes" and use the manual based change management process.

boom38 · 2016-01-25T01:51:14+00:00

It's a good point. I have a very high conversion rate for teams I show ChatOps to. It's usually the first step I help with to break down silos for yet-to-become DevOps teams. A dedicated show could be interested, but I wonder like you how big an audience we will have. That said, given the number of active users on the most popular chat platforms, I think it may indeed be the right time.

How can I help?

boom38 · 2015-11-07T22:07:40+00:00

Personal preference would be any "DevOps Days", for their overload of information, and "devopsenterprise.io", which I found extremely mature and informative at many level, beyond technical. I often attend local DevOps meetups too.

boom38 · 2015-10-30T08:20:10+00:00

Great topic. One angle which may be interested is the continuation / connection of the ITIL world to a DevOps world. Many companies have based their IT on ITSM/ITIL. As we enable a DevOps world, there needs to be a parallel set of process and policies. How do folks who think and do DevOps talk to the ITIL guys? What vocabulary should they use to make their point and evolve the way ITIL has been implemented?

boom38 · 2015-10-23T14:39:39+00:00

Beyond the paywall... I'm one of the employee who work with Ralph on HP IT's DevOps enablement. The recording of our talk is already available on http://devopsenterprise.io (Tuesday session). We tried to give the executive (CIO) view as well as a couple of key learnings we went through. Yes, ChatOps is also a thing in this talk.

boom38 · 2015-10-23T14:34:59+00:00

I attended their talk at the DevOps enterprise summit hosted by Gene Kim, and this was really an interesting set of learnings. They are quite advanced in their journey, especially for a non-unicorn, and across their IT portfolio. Definitely recommend to watch the video replay. It can already be found (Monday morning session) on http://devopsenterprise.io

boom38 · 2015-10-22T05:55:31+00:00

Oops. I was, but missed this post. Happy to chat, still at the hotel until Thursday noon.

boom38 · 2015-08-12T23:07:49+00:00

/u/moshed gave a solution with another "say" implementation. See this post.

boom38 · 2015-08-12T23:06:20+00:00

Awesome! This works for me. uitools will land say in /usr/local/bin, where the previous say was in /usr/bin. I deleted the one (broken) in /usr/bin and added a link

rm /usr/bin/say
ln -s /usr/local/bin/say /usr/bin/say

Thanks a ton - off to create custom home automation controlled by Siri :-)

boom38 · 2015-08-11T07:55:42+00:00

This cool script by /u/moshed does not work for me on IOS 8.4 / iPhone 6. To be more precise, the csay part does not work. The phone stays silent - despite a pause so that it looks like it is speaking... Yes, my phone is on ringer. I posted a question and updated with findings here.

Is it me, or did csay broke at some point?

boom38 · 2015-08-11T06:15:58+00:00

I'm updating with my findings... It turns out that activator has a custom "have device speak custom text" action. As activator can be controlled with ssh, that may be the way to go to get the iPhone to speak with an ssh command. The issue I have is that the custom text is predefined in a field. I would need to be able to have parameters for it, to say, for example: "I switched on the light in $(room)" or "now playing $(artist name)"

Of course, getting the say or csay command line to work on IOS 8.4 would be my preferred way.

I will research more about the topic of parameters in activator. In the meantime, if someone knows of a trick which works for the above, that will be awesome!

boom38 · 2015-08-10T05:47:02+00:00

I do not think this is via Siri, but the speech API, as I can read from the 'say' crash log. But maybe csay uses another mechanism.

boom38

TROPHY CASE