kharms-dev/discord-power-bot
2
0
Fork 0
Code Issues 5 Pull requests 5 Projects Releases Packages Wiki Activity Actions

Enhancements to GH Actions Pipeline #8

New issue
Open
opened 2022-10-28 12:26:11 +00:00 by mylesagray · 1 comment
mylesagray commented 2022-10-28 12:26:11 +00:00 (Migrated from github.com)
Copy link

Testing should be part of the pipeline for all PRs and commits to master - must pass with no errors to be merged/released.

https://stackoverflow.com/a/62882641/571593

Release pipeline should probably be two separate pipelines:

  • build - builds the application and container image, tags with latest and git SHA
  • release - tags an already-built container image with a static version number e.g: v0.0.1 for human readable releases

End to end pipeline should probably look something like this:

  • linting - Probably using autopep8 and pylint
  • testing - Using built in unittest/nose/pytest and calculate code coverage
  • vulns - Static code analysis & CVE scanning
  • build - Builds the app container image
  • vulns-image - Scan built image for CVEs
  • push - Push built image to repo
  • release - Manually triggered, or triggered with a push to a specific branch or tag to build a "released" image and creates a GitHub "Release"
Testing should be part of the pipeline for all PRs and commits to master - must pass with no errors to be merged/released. https://stackoverflow.com/a/62882641/571593 Release pipeline should probably be two separate pipelines: * `build` - builds the application and container image, tags with `latest` and git SHA * `release` - tags an already-built container image with a static version number e.g: `v0.0.1` for human readable releases End to end pipeline should probably look something like this: * `linting` - Probably using `autopep8` and `pylint` * `testing` - Using built in `unittest`/`nose`/`pytest` and calculate code coverage * `vulns` - Static code analysis & CVE scanning * `build` - Builds the app container image * `vulns-image` - Scan built image for CVEs * `push` - Push built image to repo * `release` - Manually triggered, or triggered with a push to a specific branch or tag to build a "released" image and creates a GitHub "Release"
mylesagray commented 2022-11-14 13:46:00 +00:00 (Migrated from github.com)
Copy link

/reopen more to come :)

/reopen more to come :)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
renovate/pin-dependencies
renovate/requests-2.x
renovate/python-3.x
renovate/py-cord-2.x
feature/sudo-auto
feature/sudo-role
feature/server-queries
feature/command-groups
No results found.
Labels
Clear labels   
bug

Something isn't working

  
documentation

Improvements or additions to documentation

  
duplicate

This issue or pull request already exists

  
enhancement

New feature or request

  
good first issue

Good for newcomers

  
help wanted

Extra attention is needed

  
invalid

This doesn't seem right

  
maintenance

Chores

  
question

Further information is requested

  
wontfix

This will not be worked on

No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
maintenance
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kharms-dev/discord-power-bot#8
No description provided.