Skip to content
This repository has been archived by the owner on Jul 10, 2021. It is now read-only.

docs(newsletter): add News edition 4 - WIP #1855

Open
wants to merge 34 commits into
base: master
Choose a base branch
from

Conversation

dnilasor
Copy link
Contributor

Draft of Newsletter issue 4 including some proposed new sections including Jobs and Call for Participation. Tweet section is still to be completed; additions welcome. Looking for additional jobs to include, so please add any you think are a good fit. Also hoping for more Call for Participation items and would like to ask SIG leads.

@dorbin @plumpy @brian-armory @dogonthehorizon @balajisiva

news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
news/editions/edition4.md Outdated Show resolved Hide resolved
@dnilasor dnilasor requested a review from 317brian October 6, 2020 05:50
@dnilasor
Copy link
Contributor Author

dnilasor commented Oct 6, 2020

Hey @dorbin and @brian-armory, I have resurrected this and would appreciate another round of review. Not ideal to have such a long newsletter but I want to feature the most salient content from the summer while sharing all of the great stuff that's been coming out lately. A doable new year's resolution for our community team will be a bite-sized version of this in a consistent monthly cadence in 2021. @nikema-armory is making progress towards that by automating the curation process via TalkWalker and Zapier : )

@nikema-armory, do you have bandwidth to contribute to this PR by helping me fill in the Jobs and Tweet Street sections? I'd love to see a couple tweets you think are good about Spinnaker, and some jobs. Maybe some of the stuff that got picked up by TalkWalker? And any Armory or OpsMX jobs that require Spinnaker skills are good too. If you're focused on other stuff, no worries as I could fill them in, or else delete the sections for this time around.

Copy link
Contributor

@dorbin dorbin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of very minor edits, but otherwise LGTM so far.

news/editions/edition4.md Outdated Show resolved Hide resolved
## [Integrating Spinnaker with ServiceNow](https://www.armory.io/blog/integrating-spinnaker-with-servicenow/)
Using ServiceNow as a system of record for software code and infrastructure changes to production environments? In this video and blog, learn to trigger Spinnaker pipelines from ServiceNow, use Spinnaker Pipeline Expressions to capture build metadata, and automate ServiceNow change requests.
### [How to build a CI/CD pipeline with Spinnaker](https://youtu.be/nTXrKiQEeO8)
In this episode of Season of Scale, Carter Morgan shows you how you can utilize Google's Cloud Build and Artifact Registry with Spinnaker and other tools to develop an automated, tag-based continuous integration and deployment pipeline.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In this episode of Season of Scale, Carter Morgan shows you how you can utilize Google's Cloud Build and Artifact Registry with Spinnaker and other tools to develop an automated, tag-based continuous integration and deployment pipeline.
In this episode of Season of Scale, Carter Morgan shows you how to use Google's Cloud Build and Artifact Registry with Spinnaker and other tools to develop an automated, tag-based continuous integration and deployment pipeline.

## [Spinnaker idea: reusable run job stages via script runner containers](https://medium.com/@tomas_lin/spinnaker-idea-reusable-run-job-stages-via-script-runner-containers-ff5fd95ec056)
Combine the deployment ease of the run script stage with the security advantages of a containerized stage by building general runner containers that run mix-and-match script workflows from S3. Enjoy the flexibility and security of a container runtime, and reduce time spent building containers.
### [Spinnaker @ GIPHY](https://engineering.giphy.com/spinnaker-giphy/?fbclid=IwAR1aztJT68aqrDUBzPDGmYfpTQfvpNK5WHkVBQ1lxLViGbg6yx8aoJj-hMI)
Understand the Site Reliability team at GIPHY's process for distributing applications to Kubernetes on AWS servers. Spinnaker has made it easy for GIPHY to integrate with existing Jenkins pipelines and tooling, deploy to multiple cluster via Helm, and handle automated canary testing and releases.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Understand the Site Reliability team at GIPHY's process for distributing applications to Kubernetes on AWS servers. Spinnaker has made it easy for GIPHY to integrate with existing Jenkins pipelines and tooling, deploy to multiple cluster via Helm, and handle automated canary testing and releases.
Understand the process the Site Reliability team at GIPHY uses for distributing applications to Kubernetes on AWS servers. Spinnaker has made it easy for GIPHY to integrate with existing Jenkins pipelines and tooling, deploy to multiple cluster via Helm, and handle automated canary testing and releases.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants