Automate Java Code Analysis with SonarCloud & GitHub Actions

Поделиться
HTML-код
  • Опубликовано: 1 окт 2024
  • Struggling with bugs and lengthy code reviews? Automate Java code analysis with SonarCloud & GitHub Actions! This video shows you step-by-step how to set up & run scans to find issues early, improve code quality & security, and streamline code reviews.
    #devops #java #sonarqube #githubactions

Комментарии • 14

  • @lost_and_finding
    @lost_and_finding 7 месяцев назад +1

    in your node js deploy video whete you use GitHub actions and deploy it in ec2. How do i access the environment variables like my postgressSql creds and aws s3 credentials. In my local machine i am using env file to store it.

    • @IntegrationNinjas
      @IntegrationNinjas  7 месяцев назад

      You can store environment variable details in GitHub secrets and then you can access those variables in your workflow.
      While building docker image you need to pass build arguments and set them in docker file.
      Ex: docker build -t your-image-name --build-arg AP|_KEY=${ secrets.AP|_KEY }.
      While in docker file you can set these as:
      # Dockerfile
      FROM node:14
      # Set environment variable
      ARG APIKEY
      ENV AP|_KEY=$API_KEY
      # Other Dockerfile instructions

  • @kunalacharya5291
    @kunalacharya5291 7 месяцев назад +1

    Sonar cube can't prevent bugs percolate due to logic. Isn't it?

    • @IntegrationNinjas
      @IntegrationNinjas  5 месяцев назад

      You're right, SonarCloud (and static code analysis tools in general) can't entirely prevent bugs due to logic errors. They primarily focus on identifying code smells, potential vulnerabilities, and enforcing coding standards.

  • @lost_and_finding
    @lost_and_finding 6 месяцев назад +1

    bhai mera app deploy ho gaya hai lekin public ip ssi acces nahi kar pa raha unable to connect araha hai security groups mai port 3000 bhi add kiya phir bhi

    • @IntegrationNinjas
      @IntegrationNinjas  6 месяцев назад

      Ensure that your EC2 instance is running and has passed its status checks. If the instance is stopped or terminated, you won't be able to access it.
      Verify that the security group associated with your EC2 instance allows inbound traffic on port 3000 from your IP address or from all IP addresses (0.0.0.0/0) if it's a public-facing service. Sometimes changes to security group rules may take a few moments to propagate.

    • @lost_and_finding
      @lost_and_finding 6 месяцев назад +1

      @@IntegrationNinjasthanks it's working now on port 443

  • @aamirimran9373
    @aamirimran9373 7 месяцев назад +1

    Niceee

  • @rahulray7683
    @rahulray7683 7 месяцев назад +1

    Nice video

  • @darshankhatri9625
    @darshankhatri9625 7 месяцев назад +1

    Informative 👍