Sign inSign up

whatishedoing/aws-codebuild-node-cypress

By whatishedoing

•Updated almost 7 years ago

Extending the excellent work of others to add Yarn, and packages required by Cypress.

Image
0

1.3K

whatishedoing/aws-codebuild-node-cypress repository overview

⁠WhatIsHeDoing Docker

Github repository

⁠👋 Introduction

Simple Docker files used for my images on Docker Hub⁠.

⁠🐳 Images

⁠AWS CodeBuild Node.js Cypress

AWS Node.js Cypress automated AWS Node.js Cypress build AWS Node.js Cypress pulls

Designed to be used in AWS CodeBuild⁠, this Node.js⁠ image adds several dependencies required by Cypress⁠, without installing Cypress itself. Yarn⁠ is also available.

Your buildspec.yml can then automate tests as follows:

# Reference: https://docs.aws.amazon.com/codebuild/latest/userguide/build-spec-ref.html
version: 0.2

phases:
  install:
    commands:
      - yarn install --frozen-lockfile

  build:
    commands:
      - yarn start

artifacts:
  base-directory: cypress/
  files:
    - screenshots/**/*
    - videos/**/*
  name: smoke-test-results
⁠AWS CodeBuild Node.js PostgreSQL

AWS Node.js PostgreSQL automated AWS Node.js PostgreSQL build AWS Node.js PostgreSQL pulls

Designed to be used in AWS CodeBuild⁠, this Node.js⁠ image adds several dependencies required by builds compiling code targeted for PostgreSQL⁠. TypeScript⁠ and Yarn⁠ are also available.

⁠.NET Core Telerik Reporting Base

.NET Core Telerik Reporting Base automated .NET Core Telerik Reporting Base build .NET Core Telerik Reporting Base pulls

Telerik Reporting⁠ has been ported to .NET Core⁠. However, containerising it is surprisingly challenging!

To alleviate some of the major problems, this base image should allow you to run your compiled reporting project, as part of a multi-stage image as follows:

# https://docs.microsoft.com/en-gb/aspnet/core/host-and-deploy/docker/building-net-docker-images
# https://docs.telerik.com/reporting/use-reports-in-net-core-apps
# https://feedback.telerik.com/reporting/1406043-can-not-run-in-docker

FROM mcr.microsoft.com/dotnet/core/sdk:2.2-stretch AS build

WORKDIR /build
COPY . ./

RUN dotnet restore
RUN dotnet build --configuration Release --output dist

FROM build AS publish
RUN dotnet publish --configuration Release --output dist

FROM whatishedoing/dotnet-core-telerik-reporting-base:latest AS base

EXPOSE 80

WORKDIR /app
COPY --from=publish /build/dist .

ENTRYPOINT ["dotnet", "report-service.dll"]
⁠Jekyll Node.js

Jekyll Node.js automated Jekyll Node.js build Jekyll Node.js pulls

Designed to be used as a base image for Jekyll⁠ builds, with Node.js⁠ augmentation. Yarn⁠ is also available.

Try using it as as part of your CI/CD⁠ pipeline:

# Specify this image.
FROM whatishedoing/jekyll-node

WORKDIR /home

# Copy all files that are not in .dockerignore.
COPY . .

# Install modules.
RUN yarn install --frozen-lockfile

# Run the build.
RUN yarn build

# Let the consumer know that Jekyll will serve from port 4000 on docker run.
EXPOSE 4000

# Run Jekyll serve to test!
CMD [ "jekyll", "serve", "--host", "0.0.0.0" ]
⁠Node.js PostgreSQL

Node.js PostgreSQL automated Node.js PostgreSQL build Node.js PostgreSQL pulls

Designed to be used as a slim base image for Node.js⁠ build and serve images that require PostgreSQL⁠ build headers. Yarn⁠ is also available.

Try using it in a CI/CD⁠ process, such as Bitbucket Pipelines⁠, as follows:

# Atlassian Pipeline documentation: https://confluence.atlassian.com/x/14UWN
# Validator: https://bitbucket-pipelines.prod.public.atl-paas.net/validator
image: whatishedoing/node-postgresql

pipelines:
  branches:
    feature/develop:
      - step:
          name: Build API
          caches:
            - node
          script:
            - yarn install --frozen-lockfile
            - yarn build
            - yarn test
          artifacts:
            - dist/**

Tag summary

Content type

Image

Digest

Size

757.7 MB

Last updated

almost 7 years ago

docker pull whatishedoing/aws-codebuild-node-cypress