渚 あ すか

渚 あ すか

1613446260

GitHub Auto Merge | AWS Lambda Node 14サポート | 技術情報共有サービス Zenn 4ヶ月で買収 | sqlcommenter【エンジニアニュース】【2月2週目】

GitHub Auto Merge | AWS Lambda Node 14サポート | 技術情報共有サービス Zenn 4ヶ月で買収 | sqlcommenter【エンジニアニュース】【2月2週目】

#aws #github

What is GEEK

Buddha Community

GitHub Auto Merge | AWS Lambda Node 14サポート | 技術情報共有サービス Zenn 4ヶ月で買収 | sqlcommenter【エンジニアニュース】【2月2週目】
渚 あ すか

渚 あ すか

1613446260

GitHub Auto Merge | AWS Lambda Node 14サポート | 技術情報共有サービス Zenn 4ヶ月で買収 | sqlcommenter【エンジニアニュース】【2月2週目】

GitHub Auto Merge | AWS Lambda Node 14サポート | 技術情報共有サービス Zenn 4ヶ月で買収 | sqlcommenter【エンジニアニュース】【2月2週目】

#aws #github

Creating your first AWS Lambda Function in Node.js | Serverless Saturday

In this Serverless Saturday video, we’ll be going over how to create your first AWS Lambda function!
In the next video, we’ll be covering how to set up CI/CD with your AWS Lambda function so stay tuned and make sure to subscribe!

To get started, log-in to your AWS account here: https://aws.amazon.com/console/

Found this video helpful? Feel free to support this channel here: https://ko-fi.com/jacksonyuan

#node.js #node #lambda #aws #aws lambda #serverless

Alex Lambert

Alex Lambert

1605788880

CI/CD Pipeline for NodeJS Lambdas on AWS using Jest, Serverless Framework, Github

I wanted to start a serverless project, and one of the primary headaches aside from architecting the workflow and deciding which lambda functions need to be created is a simple and yet effective CICD workflow.

Typical AWS’s suggestion is to use a combination of CodeCommit, CodeBuld, CodeDeploy, and glue everything together in CodePipeline. But I already have GitHub for other projects, so setting up CodeCommit will be unnecessary. The same applies to CodeBuild whose functions I currently perform with TravisCI, where I run both integration and feature specs.

This will be a NodeJS project, and I am interested in fully testing my functions at the Build phase using Jest. I also know I can adapt TravisCI to perform CodeDeploy’s functions in deploying code changes to production. But I still want my serverless function run on AWS Lambda. So here is my plan;

I use Github for my code repository, and Serverless Framework for creating and deploying my functions to AWS while running the Build phase on Travis. The build phase on Travis will run Jest tests on the functions, if all tests pass, it deploys the code on AWS Lambda using the serverless CLI depending on the working branch. I will create two environments, one for staging and the other for production. The staging branch deploys to my staging env, while the master branch deploys to production. Other branches will only run Jest tests on the lambda code and will not deploy.

All code used on this hands-on is available here on Github. Alright then, here we go.

#nodejs #aws #aws-lambda #github #node

Bongani  Ngema

Bongani Ngema

1618245300

4 Ways to Run Your AWS Amplify Project From An Existing GitHub Repo

Aws-amplify is great to develop and air an application in minutes. However, we end up messing with our application’s configuration in a way it doesn’t let us push in the cloud.

Either we can try fixing the existing app or we could clone it fresh and run it again.

Option1 : amplify remove “service”

Option 2: amplify pull

Option 3 : Clone Git your repo

Option 4 : Clone Git someone else’s repo

#aws #github #aws-services #aws-lambda #aws-s3

Obie  Rowe

Obie Rowe

1598479440

How To Automatically Transition Jira Issues Using a Github Webhook

What’s this all about eh?

One of the perks of my job is that on the last Friday of every month we get to work on our hack of choice, as long as it is in some way work related - come join us 👋

We use Github for our repos and Jira for project management. This pairing offers some nice functionality through the use of third-party add-ons such as GitHub for Jira which allow us to add pull request context to Jira issues.

Jira supports many workflow transitions out-of-the-box including the following:

- Pull Request created

- Branch created

- Commit created

- Review rejected

See the full list at confluence.atlassian.com

Our Work Setup 💻

Our Jira Workflows are quite involved but for us developers our primary focus is on the following Jira workflow transition states:

- In Development

- Ready for UI review

- Ready for review (Dev)

- Ready for QA

As part of a busy team there’s the inevitable context switching and we have many responsibilities including:

- Performing due diligence on new functionality

- PR reviews within our team

- Feature planning and development

- Bug fixing

- Mentoring

- etc.

Once our PRs have passed UI approval we then assign two Dev reviewers from within our team and transition the Jira ticket to Ready for review.

Reviews can take time for many reasons including the size of the feature, the amount of feedback, changes requested, and the number of PRs we have on the go at a given point in time; it can be difficult to notice when one has been granted the required number of approving Dev reviews and to manually then move the associated Jira ticket to the next stage in the workflow (Pull Panda can be hugely beneficial in this area, it’s a must-have for any large team).

#aws-lambda #lambda #aws #jira #slack #github #webhook #jira-to-github