Skip to content
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

#4 Configure deployment automation #32

Merged
merged 15 commits into from Jun 10, 2021
Merged

Conversation

malparty
Copy link
Owner

@malparty malparty commented Jun 9, 2021

#4 Configure deployment automation

What happened

GitHub Action Deploy Heroku is now working for staging env and deploys the app here

Insight

  • Update deploy_heroku.yml to map with the right registry token and Heroku App name (underscores not accepted by heroku)
  • Create default route so that the test can be fully done

Proof Of Work

Staging App available here

image

image

@malparty malparty self-assigned this Jun 9, 2021
@malparty malparty added !project-config Project setup, configuration, standards, ... @0.1.0 Initial release Chore labels Jun 9, 2021
@malparty malparty added this to In development in Product backlog via automation Jun 9, 2021
@malparty malparty added this to the 0.1.0 milestone Jun 9, 2021
@malparty malparty moved this from In development to In code review in Product backlog Jun 9, 2021
@malparty
Copy link
Owner Author

malparty commented Jun 9, 2021

(Unit tests are passing, I just did not bring the changes from previous PR into this branch)

@github-actions
Copy link

github-actions bot commented Jun 9, 2021

3 Errors
🚫 Brakeman static analysis detected issues in the code. If this is a false positive, mark it as such.
🚫 Code coverage data not found
🚫 Undercover: coverage report cannot be found.

BRAKEMAN REPORT

Application path Rails version Brakeman version Started at Duration
/home/runner/work/google-search-ruby/google-search-ruby 6.1.3.1 5.0.1 2021-06-10 08:25:18 +0000 1.859606934 seconds
Checks performed
BasicAuth, BasicAuthTimingAttack, CSRFTokenForgeryCVE, ContentTag, CookieSerialization, CreateWith, CrossSiteScripting, DefaultRoutes, Deserialize, DetailedExceptions, DigestDoS, DynamicFinders, EscapeFunction, Evaluation, Execute, FileAccess, FileDisclosure, FilterSkipping, ForgerySetting, HeaderDoS, I18nXSS, JRubyXML, JSONEncoding, JSONEntityEscape, JSONParsing, LinkTo, LinkToHref, MailTo, MassAssignment, MimeTypeDoS, ModelAttrAccessible, ModelAttributes, ModelSerialize, NestedAttributes, NestedAttributesBypass, NumberToCurrency, PageCachingCVE, PermitAttributes, QuoteTableName, Redirect, RegexDoS, Render, RenderDoS, RenderInline, ResponseSplitting, RouteDoS, SQL, SQLCVEs, SSLVerify, SafeBufferManipulation, SanitizeMethods, SelectTag, SelectVulnerability, Send, SendFile, SessionManipulation, SessionSettings, SimpleFormat, SingleQuotes, SkipBeforeFilter, SprocketsPathTraversal, StripTags, SymbolDoSCVE, TemplateInjection, TranslateBug, UnsafeReflection, UnsafeReflectionMethods, ValidationRegex, VerbConfusion, WithoutProtection, XMLDoS, YAMLParsing

SUMMARY

Scanned/Reported Total
Controllers 2
Models 1
Templates 3
Errors 0
Security Warnings 1 (0)
Warning Type Total
Cross-Site Scripting 1

SECURITY WARNINGS

Confidence Class Method Warning Type Message
Medium Cross-Site Scripting loofah gem 2.10.0 is vulnerable (CVE-2018-8048). Upgrade to 2.2.1 near line 212

Generated by 🚫 Danger

config/routes.rb Outdated Show resolved Hide resolved
Product backlog automation moved this from In code review to Ready for QA Jun 9, 2021
@ankitkalia1195
Copy link
Collaborator

@malparty Can you check why the Build Docker image (push) is failing, also the unit and system tests can be run again.

@ankitkalia1195 ankitkalia1195 self-requested a review June 9, 2021 09:42
Bring Unit Test config to this branch
@malparty
Copy link
Owner Author

@malparty Can you check why the Build Docker image (push) is failing, also the unit and system tests can be run again.

This was because I did not merge from develop before. It's now done, tests are passing ✅ ;-)

@junan
Copy link
Contributor

junan commented Jun 10, 2021

@malparty How about adding the Heroku url in readme? Just like this. It will be easier for other developers to find out the server url without checking from the PR description.

Merge branch 'develop' into chore/setup-deployment

And regarding updating the local branch from the base branch, we use Git's rebase instead of merge as rebase provides cleaner commit history. You can use rebase in your nest PRs when you need to get update from the base branch 👍

Co-authored-by: Junan Chakma <junan.cs@gmail.com>
config/routes.rb Outdated Show resolved Hide resolved
config/routes.rb Outdated Show resolved Hide resolved
@malparty malparty merged commit 98a6af2 into develop Jun 10, 2021
@malparty malparty deleted the chore/setup-deployment branch June 10, 2021 08:54
@malparty malparty mentioned this pull request Jun 11, 2021
@malparty malparty moved this from Ready for QA to Completed in Product backlog Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Chore !project-config Project setup, configuration, standards, ... @0.1.0 Initial release
Projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants