mozilla #frontend-infra

13 Nov 2019

A place for those focused on efforts for improving the quality, efficiency, tooling, and experiences of web front-ends in engineering operations. Discussions: github.com/orgs/mozilla-frontend-infra/teams/everyone/discussions

• 20:59
  ekyle2
  armenzg: is health.graphics hosted by netlify? When we merge, where is it deployed? For context: I am currently messing with netlify node and yarn versions: mozilla-frontend-infra/firefox-health-dashboard #602
• 21:00
  ekyle2
  armenzg: my concern is that node and yarn must be upgraded in production too,
• 21:13
  armenzg
  ekyle2: Netlify; your change looks sane
• 21:13
  ekyle2
  armenzg: thanks!
• 21:14
  armenzg
  ekyle2: deploy-preview-602--firefox-health-dashboard.netlify.com
• 21:14
  armenzg
  once you merge it should just work
• 21:14
  armenzg
  notice that on your PR you will see a bunch of status checks and one of them is the link to the Netlify deployment
• 21:14
  ekyle2
  armenzg: yes, that's my question: "if the preview works, then prod will work?"
• 21:15
  armenzg
  ekyle2: always
• 21:15
  ekyle2
  armenzg: I was not sure if netlify is just another build tool (like travis) or intergated with hosting prod too.
• 21:15
  armenzg
  unless there's some very odd thing I cannot think of!
• 21:15
  ekyle2
  thanks for the clarification
• 21:15
  armenzg
  you're welcome; anytime