Created a new blog post

[azarboon]

I've created a new blog post. This is my first time doing this. Please let me know if there is any issue.

I have added few tips about how to make better serverless pipelines. I havent seen much serverless related content on your blog post so I'm trying to change this.

[zbynek]

For the record this is a replacement of https://github.com/jenkins-infra/jenkins.io/pull/7585/files .

This new blog post seems to talk about serverless best practices in general, but has little to do with Jenkins.
On Jenkins blog I'd expect a more specific topic, like "how to run Jenkins in serverless environment" (similar to the 2018 blog post) or "how to deploy code into serverless environment with Jenkins".

[MarkEWaite]

On Jenkins blog I'd expect a more specific topic, like "how to run Jenkins in serverless environment" (similar to the 2018 blog post) or "how to deploy code into serverless environment with Jenkins".

I agree wit @zbynek . I think that posts to the Jenkins blog should almost always include something about Jenkins in the post.

[azarboon]

Thanks for feedback. May I create a high level solution diagram about using Jenkins in AWS and its services? It will be high level design and I wont detail the configurations. Let me know if that would satisfy you.

[kmartens27]

@azarboon the diagram sounds like a solid idea, but I would advise there be some sort of explanation of how Jenkins helps with this or even some instructions on how to use Jenkins in this configuration. The diagram should help illustrate these steps/points and provide some context as to why Jenkins is a good solution for this process. Something like this AWS blog post is a good example of what I'm thinking of when it comes to a diagram + explanation.

[azarboon]

@azarboon the diagram sounds like a solid idea, but I would advise there be some sort of explanation of how Jenkins helps with this or even some instructions on how to use Jenkins in this configuration. The diagram should help illustrate these steps/points and provide some context as to why Jenkins is a good solution for this process. Something like this AWS blog post is a good example of what I'm thinking of when it comes to a diagram + explanation.

Thank you. Originally, I was planning to expand on this blog post:

https://www.jenkins.io/blog/2018/08/06/serverless-cicd-jenkins/

It gives a 50,000 ft view of the solution without going into details nor explaning why to use Jenkins. I can make similar solution diagram using Jenkins to prove my points.

To be clear: I'm not expert on Jenkins so I cant really help on the "why jenkins" part. However, given the popularity of Jenkins, there should be some guidelines / tips for Jenkins' serverless users on your official website. But I feel there is a void. So, aim of my post is to fill that gap.

Please let me know what's your advice.