-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New post: Build your iOS applications faster with a CICD pipeline #255
Conversation
Congratulations on submitting your Content Draft! Below is a rough outline of the process: Content Draft (you're here) -> Review by reviewer -> You implement changes, if requested -> Final Review by reviewer |
@bketelsen This article is ready for technical review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few small changes requested. Thorough and thoughtful article, thank you for the contribution.
@sebsto Would you please address Brian's edits from his technical review? |
❌ Could not validate the pull request and generate a preview. Validation and preview are only available if the pull request originates from a branch of the build-on-aws/content repository or from a public fork. |
Thank you for the feedback. |
@damonk10 This article is ready for your editorial review. |
First round of editorial changes.
❌ Could not validate the pull request and generate a preview. Validation and preview are only available if the pull request originates from a branch of the build-on-aws/content repository or from a public fork. |
❌ Could not validate the pull request and generate a preview. Validation and preview are only available if the pull request originates from a branch of the build-on-aws/content repository or from a public fork. |
❌ Validation and preview generation failed: Error: Merge failed, please pull changes from upstream and resolve merge conflicts if any. |
posts/cicd-for-ios-app/index.md
Outdated
date: 2023-05-01 | ||
--- | ||
|
||
When it comes to building, testing, and deploying applications, software development engineers and devops engineers master the art of automation. Today, most backend or frontend web applications are built automatically and, sometimes, are also deployed to production as changes occur. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This introduction is well-written, but it takes too long to get to the point -- and it's slightly redundant with the section on automation. How would you feel about something like this?
"When it comes to building, testing, and deploying applications, software development engineers and devops engineers must master the art of automation. Today, most backend or frontend web applications are built automatically and, sometimes, are also deployed to production as changes occur.
The workflows that facilitate this process - fetching code, building it alongside code from other developers, running various tests, and even deploying the changes - are called continuous integration and continuous deployment, or CI/CD for short. CI/CD helps to reduce the time to deliver new code to your customers. It also helps to detect issues faster and to accelerate feedback cycles. The IT industry considers CI/CD as a best practice.
While CI/CD workflows for Linux and Windows have been thoroughly explained, though, building such pipelines to develop applications for Apple operating systems is less commonly understood. iOS, iPadOS, tvOS, watchOS, and macOS require their own unique approach to CI/CD, and building that pipeline is what we'll be learning how to do in this post."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the suggestion. It reads and flows nicely.
Automated Validation Results
Preview results |
pub date and tags
Automated Validation Results
Preview results |
❌ Publication failed |
Content Pull Request Checklist
Please check to make sure your content submission meets the following requirements by adding an
x
between the brackets:index.md
(e.g.posts/what-happens-when-you-type-a-url-into-your-browser/index.md
). If I have a post series, I have followed the structure outlined in the FAQ.Is this pull request linked to a Content Proposal or Idea Suggestion Issue? If so, please link to it below.
https://app.asana.com/0/1202460975106500/1203868590660877/f
#Issue Number
By submitting this pull request, I confirm I own this content, have permission to use each image included in this content, and that it will be released under the CC BY-SA 4.0 SA License.