aws-samples / aws-codepipeline-stepfunctions

This project shows how to integrate AWS CodePipeline and AWS Step Functions state machines. The integration enables developers to build much simpler CodePipeline actions that perform a single task and to delegate the complexity of dealing with workflow-driven behavior associated with that task to a proper state machine engine. As such, developers will be able to build more intuitive pipelines and still being able to visualize and troubleshoot their pipeline actions in detail by examining the state machine execution logs.

Summary
email_034-attachment-send-file-code-cssCreated with Sketch.
Main Code: 1,457 LOC (16 files) = JS (63%) + YAML (36%)
Secondary code: Test: 0 LOC (0); Generated: 1,580 LOC (3); Build & Deploy: 170 LOC (15); Other: 1,982 LOC (21);
Artboard 48 Duplication: 25%
File Size: 0% long (>1000 LOC), 41% short (<= 200 LOC)
Unit Size: 0% long (>100 LOC), 71% short (<= 10 LOC)
Conditional Complexity: 0% complex (McCabe index > 50), 94% simple (McCabe index <= 5)
Logical Component Decomposition: primary (5 components)
files_time

4 years, 3 months old

  • 100% of code older than 365 days
  • 63% of code not updated in the past 365 days

0% of code updated more than 50 times

Also see temporal dependencies for files frequently changed in same commits.

Goals: Keep the system simple and easy to change (4)
Commits Trend

Latest commit date: 2021-08-27

0
commits
(30 days)
0
contributors
(30 days)
Commits

11

9

3

13

Contributors

2

5

2

2

2021 2020 2018 2017
show commits trend per language
Reports
Analysis Report
Trend
Analysis Report
76_startup_sticky_notes
Notes & Findings
Links

generated by sokrates.dev (configuration) on 2022-01-31