How DNS mapping works?

I was wondering, how the mapping works on a DNS. Is made from an IP to the names or from the name to the IP?

How would a data structure look like?

`var map = {`

`"`[`60.90.60.90`](https://60.90.60.90)`":[`

`"domain1", "domain2", "domain3"`

`]`

`};`

Or something like this:

`var map = [`

`"domain1": "`[`60.90.60.90`](https://60.90.60.90)`",`

`"domain2": "`[`60.90.60.90`](https://60.90.60.90)`",`

`"domain3": "`[`60.90.60.90`](https://60.90.60.90)`"`

`];`

​

Thanks.

https://redd.it/du8fqu
@r_devops

Self-hosted runners for GitHub Actions is now in beta

Check out their announcement [at their blog](https://github.blog/2019-11-05-self-hosted-runners-for-github-actions-is-now-in-beta/). They are written in .NET Core. I would have thought GitHub would use Go as it is easy to cross compile and results in a single binary. Instead you have to download 285MB with lots of ddls. I know GitLab runners are written in Go. Maybe it's because GitHub can reuse code from Azure DevOps runners.

https://redd.it/dsfc6i
@r_devops

The Special role of PID 1
https://www.reddit.com/r/DabbleCommV/comments/dsodma/blogpost_containers_the_special_role_of_pid_1/

https://redd.it/durwmg
@r_devops

Should your cicd tool commit back to git?

As the title says.. For example, if a Docker build succeeds, and tests pass, you semver out a new version. Should your CICD tool commit this to the terraform variables on the same branch in your IaC code? Or would that be a bad idea, and should the tool fill it in as dynamic parameter (unversioned somewhere) in the pipeline run that will execute the Terraform deploy?

Why would it be a good idea, or bad idea to commit stuff like semvers back to the git repository that contained the source code?

This would assume ofcourse that there are no circular runs. The trigger should not happen to run and build and test again due to the commit of the version number back.

https://redd.it/dutisg
@r_devops

PR test pipeline involving docker build, any ideas

Does anyone have any ideas for the best build tool to use for a scenario where it'll build the docker file in the given branch, spin up the image, then run the tests on the image. Most of the tools I've looked at rely on being provided a static image or docker image repo and they just use the 'latest' one. But that'll cause issues if the PR's intention is to update the dockerfile or files used by the dockerfile. Ideally it would actually build two images, one for a temporary DB to seed test data on and the other for the app but I can manage with one.

I'll trigger this on PR creation and update. Sorry if I'm asking stupid questions here.

Sidenote, I suspect this whole process will make it very slow to test since it's having to build and spin up images repeatedly. Is there any way to test if the dockerfile and other related files have changed between builds so the image can be cached and reused if nothing has changed?

https://redd.it/dutw90
@r_devops

Free devops tool?

Im currently a beginner in DevOps. I am doing Native Android Jenkins. But Jenkins seems to be a bit of a hard setup for me yet as i am still learning. Any suggestions of a free devops tool that can do in local machine? Its okay with me if its just in the local not in the server. Just so that i can learn more on DevOps.

https://redd.it/dsf0u8
@r_devops

Alternatives to Issuehunt.io?

I want to find development for my open source project using a service to Issuehunt. Are there any alternatives that perhaps have a larger user base, or one that works with GitLab?

T.I.A.

https://redd.it/duwy71
@r_devops

tfsec: Static analysis powered security scanner for your terraform code

[https://github.com/liamg/tfsec](https://github.com/liamg/tfsec)

https://redd.it/duruqu
@r_devops

What status pages do y'all look at / subscribe to?

Hey! I'm a PM on [statuspage.io](https://statuspage.io) and I'm curious what status pages you all look at / subscribe to! I focus a lot on what it's like to manage / update your own status page, but not as much on what it's like to be a viewer / subscriber and am trying to learn more.

Also, if you'd like to go deeper on how we can improve the experience - if any of you would be willing to chat for 30-45 minutes in the next couple weeks shoot me a DM and we can set it up :)

https://redd.it/duz0gr
@r_devops

Does switching to Kubernetes make sense if your applications are all stateful and not microservices?

My org is looking to switch off Cattle (Rancher 1.6.x) and the Operations and DevOps team are trying to find a new orchestrator. We've looked into Swarm w/ Portainer and Rancher 2.x w/ Kubernetes. 98% of our apps are legacy that do not scale and are very much stateful and monolithic. Is it worth the effort and training to use kubernetes, or should we stay in our safe zone with continuing to use Docker Compose with Swarm & Portainer?

https://redd.it/duzaq2
@r_devops

Kubernetes or OpenShift, to start with ?

​

Hi Folks,

From system admin prospective, which certification may be tough then other in Kubernetes Certification vs OpenShift certification?

Or it is very subjective? lol..

If one has to start somewhere in Ops side of DevOps, what would be suggested pick among both of these options?

Thanks in advance

https://redd.it/dv1gs7
@r_devops

Issuing doing npm install on Jenkins for Vue project

I have a Jenkins build I am using for a Vue.js application. I am trying to install all dependancies as part of the pipeline and am running into some issues. I've included the below output as well as the npm install part of my pipeline.

​

It looks like a python issue to me however I don't think I'm using python unless vue uses it under the hood

​

error from below build step

+ npm install
> [email protected] install /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.12.0/linux-x64-79_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.12.0/linux-x64-79_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
try setting a proxy via HTTP_PROXY, e.g.

export HTTP_PROXY=https://example.com:1234

or configure npm proxy via

npm config set proxy https://example.com:8080

> [email protected] postinstall /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass
> node scripts/build.js

Building: /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 info it worked if it ends with ok
gyp verb cli [
gyp verb cli '/var/lib/jenkins/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/UI/bin/node',
gyp verb cli '/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli 'rebuild',
gyp verb cli '--verbose',
gyp verb cli '--libsass_ext=',
gyp verb cli '--libsass_cflags=',
gyp verb cli '--libsass_ldflags=',
gyp verb cli '--libsass_library='
gyp verb cli ]
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:158:21)
gyp verb `which` failed python2 Error: not found: python2
gyp verb `which` failed at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:158:21) {
gyp verb `which` failed stack: 'Error: not found: python2\n' +
gyp verb `which` failed ' at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js

:13:12)\n' +
gyp verb `which` failed ' at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)\n' +
gyp verb `which` failed ' at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5\n' +
gyp verb `which` failed ' at FSReqCallback.oncomplete (fs.js:158:21)',
gyp verb `which` failed code: 'ENOENT'
gyp verb `which` failed }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` failed Error: not found: python
gyp verb `which` failed at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:158:21)
gyp verb `which` failed python Error: not found: python
gyp verb `which` failed at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:13:12)
gyp verb `which` failed at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)
gyp verb `which` failed at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5
gyp verb `which` failed at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5
gyp verb `which` failed at FSReqCallback.oncomplete (fs.js:158:21) {
gyp verb `which` failed stack: 'Error: not found: python\n' +
gyp verb `which` failed ' at getNotFoundError (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:13:12)\n' +
gyp verb `which` failed ' at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:19)\n' +
gyp verb `which` failed ' at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5\n' +
gyp verb `which` failed ' at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5\n' +
gyp verb `which` failed ' at FSReqCallback.oncomplete (fs.js:158:21)',
gyp verb `which` failed code: 'ENOENT'
gyp verb `which` failed }
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack at PythonFinder.failNoPython (/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/lib/configure.js:484:19)
gyp ERR! stack at PythonFinder.<anonymous> (/var/lib/jenkins/workspace/Deploy UI/node_modules/node-gyp/lib/configure.js:406:16)
gyp ERR! stack at F (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:68:16)
gyp ERR! stack at E (/var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:80:29)
gyp ERR! stack at /var/lib/jenkins/workspace/Deploy UI/node_modules/which/which.js:89:16
gyp ERR! stack at /var/l

ib/jenkins/workspace/Deploy UI/node_modules/isexe/index.js:42:5
gyp ERR! stack at /var/lib/jenkins/workspace/Deploy UI/node_modules/isexe/mode.js:8:5
gyp ERR! stack at FSReqCallback.oncomplete (fs.js:158:21)
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.

npm ERR! A complete log of this run can be found in:
npm ERR! /var/lib/jenkins/workspace/Deploy UI/.npm/_logs/2019-11-12T02_15_01_035Z-debug.log


package.json

"dependencies": {
"@agametov/vueditor": "^0.4.1",
"@chenfengyuan/vue-countdown": "^1.1.2",
"apexcharts": "^3.8.3",
"axios": "^0.19.0",
"bootstrap": "^4.3.1",
"bootstrap-social": "^5.1.1",
"bootstrap-vue": "^2.0.0-rc.27",
"chart.js": "^2.8.0",
"flag-icon-css": "^3.3.0",
"ionicons": "^4.6.2",
"moment": "^2.24.0",
"node-sass": "^4.12.0",
"sass-loader": "^7.1.0",
"simple-line-icons": "^2.4.1",
"v-autocomplete": "^1.8.2",
"vue": "^2.6.10",
"vue-apexcharts": "^1.4.0",
"vue-bootstrap-datetimepicker": "^5.0.1",
"vue-chartjs": "^3.4.2",
"vue-custom-scrollbar": "^1.1.0",
"vue-event-calendar": "^1.5.2",
"vue-full-calendar": "^2.7.0",
"vue-good-table": "^2.17.4",
"vue-hljs": "^1.1.2",
"vue-input-tag": "^2.0.6",
"vue-ins-progress-bar": "^1.0.0",
"vue-maskedinput": "^0.1.3",
"vue-moment": "^4.0.0",
"vue-notification": "^1.3.16",
"vue-nvd3": "^1.0.0",
"vue-pop-colorpicker": "^1.0.2",
"vue-router": "^3.0.7",
"vue-select": "^3.1.0",
"vue-slider-component": "^3.0.33",
"vue-sparklines": "^0.1.9",
"vue-stripe-elements-plus": "^0.3.2",
"vue-sweetalert2": "^2.1.1",
"vue2-google-maps": "^0.10.7",
"vuejs-datepicker": "^1.6.2"
},
"devDependencies": {
"@vue/cli-plugin-babel": "^3.9.2",
"@vue/cli-plugin-eslint": "^3.9.2",
"@vue/cli-service": "^3.9.3",
"vue-template-compiler": "^2.6.10"
},

&#x200B;

&#x200B;

my pipeline code

stage('Build') {
steps {
nodejs(nodeJSInstallationName: 'UI') {
sh "npm install && npm install --only=dev && npm run build --${params.buildenv}"
}
}
}

&#x200B;

installed python via the apt repo and ran into a bigger (longer) error message. I can't include here as too long (tried already)

&#x200B;

A bunch of lines about node openssl like the below

&#x200B;

gyp verb extracted file from tarball include/node/openssl/aes.h

&#x200B;

&#x200B;

gyp verb tarball done parsing tarball
gyp verb check download content checksum, need to download `SHASUMS256.txt`...
gyp verb checksum url https://nodejs.org/download/release/v13.1.0/SHASUMS256.txt
gyp http GET https://nodejs.org/download/release/v13.1.0/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v13.1.0/SHA

SUMS256.txt
gyp verb checksum data {"node-v13.1.0-aix-ppc64.tar.gz":"5faec026afe9052f277402500236dd9ec4d58e0e8de93f66989fc337c65e33c8","node-v13.1.0-darwin-x64.tar.gz":"6501c1bcf2babb5b9c81dcff8b52021f726da8f6ee28df1637acade1a16c7d39","node-v13.1.0-darwin-x64.tar.xz":"b918bdc6ca5726084a737c926744cdaecde624ba39ac8aaed889f296007a5094","node-v13.1.0-headers.tar.gz":"577785216f5a4097a9108fd05f3117556f0954f0a03a26cfbfd1ce7af94587d4","node-v13.1.0-headers.tar.xz":"73ec6759903137d3e22806e745777cb7cda3150f0d81c5ba13e7599c2be03d32","node-v13.1.0-linux-arm64.tar.gz":"dd36c7846f7713b6e55baf0b6ab7882c18b129d83a3d0f7ef62790d181461d22","node-v13.1.0-linux-arm64.tar.xz":"646d597e6b0dc400429e46b703a5135c77bd71e653ea4c8254d0b60c17b6ec1d","node-v13.1.0-linux-armv7l.tar.gz":"88450bc38dac0be15c9bd09bfccf4ce79f1911930f37658c730c151b26c5aa97","node-v13.1.0-linux-armv7l.tar.xz":"e15601106fbd9ed75a4642eab91bb3f3ddab8b5821e886bdb070c014d9ab9af2","node-v13.1.0-linux-ppc64le.tar.gz":"0c804f0671bcdada9be66e4ca844c08f897357fbf2426be8cc326d20e6362833","node-v13.1.0-linux-ppc64le.tar.xz":"561dbaa36db7dcb4fff378e110b4ddd29d918754e73449208899fbfb9f3ce1ae","node-v13.1.0-linux-s390x.tar.gz":"24c29e917230d9cc510ba764ff6ef57bcc816520c146b47dce3ed4aeb3f7d333","node-v13.1.0-linux-s390x.tar.xz":"a3229a795ee8bda15396701badd31d695d9a6f487a730c73022305c98522767a","node-v13.1.0-linux-x64.tar.gz":"490e998198e152450e79bb65178813ce0c81708954697f91cfd82537acfcb588","node-v13.1.0-linux-x64.tar.xz":"2eecb5a4b7975c3b406bee36b12c9a29e8bedf9553c88cad310b8f076db00881","node-v13.1.0.pkg":"3b6abd2a5f7a5778bbe5363ea222910b19674648eb2b3d734d9ee751ec29da71","node-v13.1.0-sunos-x64.tar.gz":"8e17a613950018e27f34f7268e01cbb385777189961ccf386f7d0d05883687b3","node-v13.1.0-sunos-x64.tar.xz":"e9dd61b7f537b98a6656c0e03766997aa712bf3d40e7cb08ba4019e942846739","node-v13.1.0.tar.gz":"df640a2f151f788d02dc25c91d80fffe06b4c3c72fbdee07ab9abd7c6879d6cd","node-v13.1.0.tar.xz":"d42c056cbd33b35836b0f5cfb2c56712b965ea76e188ef79af492614cf14cb68","node-v13.1.0-win-x64.7z":"8f242259fa929f759f06bb1cf399df3b81061eb1ce5ccaa9d206dc157fcf93fc","node-v13.1.0-win-x64.zip":"d735e97bdeb7b74551b9d165c708a3fdea4dbb3801a65e70f6d6ae3539d48a03","node-v13.1.0-win-x86.7z":"c4ecf16dd147956c9335b547fdfb1b0eb1c333c1a1722843b45ba04b9fee17fe","node-v13.1.0-win-x86.zip":"81af54ba9e852073ac975aa0955da1efb4b2ea6ef213eb3ce90f3b22a82555d8","node-v13.1.0-x64.msi":"22ec0be47b0f3f5f163f82e18c01df456921f39b756ee4a828534264b06d0fe6","node-v13.1.0-x86.msi":"7f56fa7350eaf0da6d33b24578a281e8d759a9344e5c8ea851ea541eaebb94fe","win-x64/node.exe":"5c3b0006330a08743363ebf26ccdf1618ab0269f50756088b6e5257d7a32c5a1","win-x64/node.lib":"aa183bbe6f7a2b63395ff83ac6f687274bafbc1e64be2e6e5bb600dc1e5c7bea","win-x64/node_pdb.7z":"7e4bc02444eea52b90d15d1985789aa10efa5b058a6550aac389db3eba42a4b7","win-x64/node_pdb.zip":"ae389590498393e57379d462b3d8d6c2639afcf04d6c279f99b8e2122b98b94e","win-x86/node.exe":"20fb3aa33b88628c533e59fec344db02683434cfbd91d70a36e3a0c3f865ed03","win-x86/node.lib":"caa896eb2249fdf32ed3dda1c7bdb8250b8dbdf6f5498b10a4dec91f541d2d11","win-x86/node_pdb.7z":"e2301d3ae38b01fecceb8111955568a741183de87d05c88a6499abfca1e913b1","win-x86/node_pdb.zip":"5d9cc82ef9f2165f08ad4057b23c90154bf6a334ed7f9d3b5757003f70f49108"}
gyp verb download contents checksum {"node-v13.1.0-headers.tar.gz":"577785216f5a4097a9108fd05f3117556f0954f0a03a26cfbfd1ce7af94587d4"}
gyp verb validating download checksum for node-v13.1.0-headers.tar.gz (577785216f5a4097a9108fd05f3117556f0954f0a03a26cfbfd1ce7af94587d4 == 577785216f5a4097a9108fd05f3117556f0954f0a03a26cfbfd1ce7af94587d4)
gyp verb get node dir target node version installed: 13.1.0
gyp verb build dir attempting to create "build" dir: /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build
gyp verb build dir "build" dir needed to be created? /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: /var/lib/jenkins/workspace/Deploy UI/node_modules/node-sass/build/

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