config.gypi
gyp verb config.gypi checking for gypi file: /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/config.gypi
gyp verb common.gypi checking for gypi file: /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/common.gypi
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn /usr/bin/python2
gyp info spawn args [
gyp info spawn args '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0',
gyp info spawn args '-Dnode_gyp_dir=/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
gyp verb command build []
gyp verb build type Release
gyp verb architecture x64
gyp verb node dev dir /var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0
gyp verb `which` succeeded for `make` /usr/bin/make
gyp info spawn make
gyp info spawn args [ 'V=1', 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build'
g++ '-DNODE_GYP_MODULE_NAME=libsass' '-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1' '-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DOPENSSL_NO_PINSHARED' '-DOPENSSL_THREADS' '-DLIBSASS_VERSION="3.5.4"' -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/include/node -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/src -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/deps/openssl/config -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/deps/openssl/openssl/include -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/deps/uv/include -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/deps/zlib -I/var/lib/jenkins/workspace/Deploy UI/.node-gyp/13.1.0/deps/v8/include -I../src/libsass/include -fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -O3 -fno-omit-frame-pointer -std=gnu++1y -std=c++0x -fexceptions -frtti -MMD -MF ./Release/.deps/Release/obj.target/libsass/src/libsass/src/ast.o.d.raw -c -o Release/obj.target/libsass/src/libsass/src/ast.o ../src/libsass/src/ast.cpp
g++: error: UI/.node-gyp/13.1.0/include/node: No such file or directory
g++: error: UI/.node-gyp/13.1.0/src: No such file or directory
g++: error: UI/.node-gyp/13.1.0/deps/openssl/config: No such file or directory
g++: error: UI/.node-gyp/13.1.0/deps/openssl/openssl/include: No such file or directory
g++: error: UI/.node-gyp/13.1.0/deps/uv/include: No such file or directory
g++: error: UI/.node-gyp/13.1.0/deps/zlib: No such file or directory
g++: error: UI/.node-gyp/13.1.0/deps/v8/include: No such file or directory
src/libsass.target.mk:158: recipe for target 'Release/obj.target/libsass/src/libsass/src/ast.o' failed
make: *** [Release/obj.target/libsass/src/libsass/src/ast.o] Error 1
make: Lea

ving directory '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build'
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:210:5)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Linux 4.15.0-1052-aws
gyp ERR! command "/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/UI/bin/node" "/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass
gyp ERR! node -v v13.1.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above

https://redd.it/dv3lv2
@r_devops

Storing ENV files in git repo for Vue.js?

Before you comment and condem me please read.

&#x200B;

I am creating a pipeline for a Vue.js application - front end only - I was thinking it might make sense to put the .env.production and .env.staging files in the git repo since they contain nothing an end user couldn't figure out. For me that is a third party public key which you can see in the inspect view of chrome and the other is the base URL for axios.

&#x200B;

Am I crazy for thinking it's okay to put these in the git repo? It's a private repo if that matters much.

https://redd.it/dv2sbc
@r_devops

My Perforce P4V Client is frozen

Forgive my ignorance, I'm 3D environment artist so I don't know all the programming jargon. That said, my Perforce seems to be freezing and it has destroyed my progress. Note: I've worked with Perforce for 5 years at several companies, never seen anything like this. So this is not a dig at Perforce, just trying to fix this.

**The problem:** When I load up Perforce, it defaults to no workspace selected. When I choose one from the dropdown, it freezes. Task Manager shows it's not responding. It's currently been in that state for about an hour and I'm just hoping it returns to life...

**What happened:** Earlier tonight I went to submit some files. Basic Unity prefabs and map. It was a decent number (\~400) but nothing compared to what I've done before with no problems. The submit button worked fine and the loading bar was progressing like normal. Then it stalled at 100%. I've seen it hang up before because I'm accessing a remote server, so I kept it there for \~2hours. While that was going on, I continued working on my scene. Maybe the problem was that I was submitting files while I was also editing them? I assumed that wouldn't cause a problem unless I hit "save" though.

I also force quit the application through task manager, thinking I could regain control and wanted to make sure I wasn't mucking up the files I was submitting. That's when Perforce started freezing on workspace. So there's a very good chance this is all my fault. I just want control back.

**What I've noticed:** If I don't select a workspace, I can still browse the depot. Looking at the files, I see that I still have the files checked out. I don't see a changelist but I suspect that's because no workspace is selected.

https://redd.it/dv5ain
@r_devops

Tracking a version through the ephemeral

I have an application that is built/compiled on prem, deployed to the ephemeral world of AWS (spot instances), data is written from the app to s3, and the instances terminate. I need to track the branch/commit hash used to build the output.

How would you do this?

https://redd.it/dv0wcy
@r_devops

All in with AWS vs Spread around (Certification)

Good morning all, what do you think at the moment has a higher value:

1) Have AWS Professional Cert and no certs from any other major cloud provider.

2) Have AWS associate certs and associate level certs from Google (GCP)

2) Have AWS associate certs and associate level certs from Microsoft (Azure)

https://redd.it/duvogc
@r_devops

One ELK Stack for all ENV or seprate ELK stack per env?

Guys,
What do you recommend?
\- Having separate ELK stack for Dev, Stage & Prod Env
OR
\- Having one ELK stack for (all) Dev, Stage & Prod Env?

https://redd.it/dv926a
@r_devops

Azure devops

Hey guys,

&#x200B;

first at all. Sorry for my bad english.

second, does anybody already made a ui or js project where they can let users add a bug of the app they made?

So that if they have a bug the user can report it on a page where they add the problem and automatically adds a work item in our backlog?

&#x200B;

Thanks for reading and i'm looking forward to the answers!

https://redd.it/dutz1s
@r_devops

Is it for me?

Hello to you all,

I've been wondering if I could feel safe with my new position. I've been hired as Junior DevOps and the skills I know are CRUD operations in terms of databases (I have previous experience in terms of data processing), I know some Java and Python but never used it in too serious manner before. I do not have any previous experience with system scripts or administration.

DevOps seems to be responsibility focused work, and I do not wish to fail. Do you think it's a good position for someone like me? I'm a bit shocked, happy and scared at the same time. I do not want to fail badly as it would have really bad outlook for my life and career.

Thank you in advance for sharing your thoughts.

https://redd.it/duvjbf
@r_devops

How to face sensible load variations on a Kubernetes infrastructure without overscaling it?

I wrote an article to help you get started with [horizontal pod autoscaling](https://www.padok.fr/en/blog/autoscaling-kubernetes) to manage a peak without spending a fortune. Check it out and give me your insights.

https://redd.it/dvc5ea
@r_devops

Simple way to keep configs in sync between 2x Apache web servers?

Wondering what a good way to do this is. Kind of reluctant to go down the full blown config management path (ansible, etc), as its literally only 2 servers that need to stay in sync.

 

Was thinking maybe store the configs in git and have a cronjob that grabs it every couple of hours and reloads the httpd? Although thats pretty clunky.

https://redd.it/dvfld3
@r_devops

Gerrit - Multiple Intermediates (Or steps)

I'm responsible for the CI pipeline at work. Current workflow is the following:

1. Push to gerrit
2. Code review and Jenkins Build
3. Submit

I would like to add another round of tests between the jenkins build and the submit. Those are selenium tests, a bit overlong to run and require deploying the application. I don't want to deploy the application and run those tests for every gerrit patchset, but I don't want developpers to be able to merge without those tests having been run.

&#x200B;

The way I picture it would be the same flow as right now - back and forth until code review and build + ut are done, THEN start the back and forth with seleniun tests, THEN merge to master

&#x200B;

It seems simple enough to do with a pull request merge. I would just need to have an intermediate branch in between that would include all commits waiting for selenium tests, and they could then be added to master when ready.

&#x200B;

I can't quite figure out how this would work with gerrit though... Any ideas?

https://redd.it/dvfcrf
@r_devops

Visualize (And control) your helm?

Hi all,

I'm working as a devops for the last couple of years (mainly k8s) - and from my own personal pain i started working on a dashboard to visualize helm deploy, current status, and history (as a first step).

Show diff between versions.

And Later i plan on adding some control (mainly rollback).

I already started developing it but wonder if you some easy/cool tools that does what i need?

Anyway i would love to have some beta tasters for the dashboard, so feel free to contact me :)

https://redd.it/dvh0nm
@r_devops

Container Internals Series | Part 0 — System Architecture

Great article about container internals: [https://medium.com/@tiemma/breaking-down-containers-part-0-system-architecture-37afe0e51770](https://medium.com/@tiemma/breaking-down-containers-part-0-system-architecture-37afe0e51770).

Covers User & System space, syscalls, sysgroups etc. First part in a series.

https://redd.it/dvhkg7
@r_devops

Run Kubernetes+Istio+Knative locally, as a developer

What's the most lightweight/easiest way to run k8s + istio + knative locally as a development environment?

We'd love if our devs could run their services (multiple) locally and utilize Knative Eventing to test their event producer - customer setup.

Most of our devs use MacPROs and a few of them are on Linux.

https://redd.it/dvfvbm
@r_devops

Organising Terrform Workloads

I wrote about how I go about organising, or laying out, my Terraform code.

[https://opsfactory.com.au/organising-terraform-workloads/](https://opsfactory.com.au/organising-terraform-workloads/)

Hopefully you find it useful. Any and all feedback welcome, of course.

https://redd.it/dvn8ce
@r_devops

What is the scale at which companies start thinking about observability/monitoring/logging?

What is the typical scale at which companies/products start thinking about monitoring/observability? Is it based on the revenue, number of people on the dev team or on the number of users using the product on a monthly/daily basis?

I understand that the above variables are correlated - but want to understand of there are any standard accepted frameworks around this? Or is it just that people start worrying about monitoring/observability when things start breaking

https://redd.it/dvodks
@r_devops

Impacts of CI plus Pull Requests for large teams

Are you guys using CI plus Pull Requests for large teams (say 14) and different approvers?

In this situation the order of the approvals may result in some conflits, right? Or drop productivity a little?

Is it worth the cost? Isn't CI offering enough confidence on what is being published.

Thanks for sharing.

https://redd.it/dvj74s
@r_devops

A curated list of best practices for Kubernetes in production

We've curated a list of best practices for deploying and scaling apps on Kubernetes in production.
The list covers application development, administering and configuring clusters.
It's been a hard work collating and curating dozens of other articles and books.
I hope you find it useful.
[https://learnk8s.io/production-best-practices/](https://learnk8s.io/production-best-practices/)

https://redd.it/dvpzsi
@r_devops

Patterns and examples of Terraform projects that enable a continuous flow of changes and improvements

This is a 40 minute talk from GOTO Amsterdam 2019 by Kief Morris, author of O'Reilly's "Infrastructure as Code" & cloud practice lead at ThoughtWorks. Check out the full talk abstract and link below:

[https://youtu.be/1f\_P8ZH5BC8?list=PLEx5khR4g7PKT9RvuVyQxJLO8CZUJzNMy](https://youtu.be/1f_P8ZH5BC8?list=PLEx5khR4g7PKT9RvuVyQxJLO8CZUJzNMy)

People are adopting dynamic infrastructure technologies like the cloud, containers, and serverless so that they can easily make changes to their systems. Defining infrastructure as code should make systems consistent, reliable, and easy to manage, but an infrastructure codebase can easily become a complicated, fragile mess that is scary to change.

In order to routinely change, extend, and improve infrastructure, teams need to have confidence that changes will work correctly and that the impact of failures is low and easily corrected. This creates a virtuous cycle of continuously improving the quality of the systems. Teams can gain this confidence by applying appropriate design patterns and implementation practices.

Kief Morris shares patterns and examples of Terraform projects using pipelines, automated tests, and loosely integrated stacks to enable a continuous flow of changes and improvements. These patterns—which have been used at clients across the financial services, retail, public sector, and media industries—ensure that any part of the infrastructure can be easily rebuilt, minimize the “blast radius” for a given change, automatically validate changes for correctness, security, compliance, and other operational and architectural requirements, and structure projects to enable multiple people and teams to work on systems while minimizing coordination overhead.

**What will the audience learn from this talk?**

* The role of different types of tools and technologies in an evolutionary infrastructure
* Implementing automated infrastructure testing and validation
* Designing pipelines to deliver changes across environments and into production
* Handling data and configuration in a system where infrastructure is dynamically rebuilt, expanded, and contracted
* Advanced patterns for structuring and integrating infrastructure projects and pipelines in larger systems used by multiple teams

https://redd.it/dvq93o
@r_devops