| name: Show secrets | |
| on: [push] | |
| jobs: | |
| debug: | |
| name: Debug | |
| runs-on: ubuntu-latest | |
| steps: | |
| - name: Check out code |
| #!/usr/bin/env bash | |
| ### | |
| # You will need a file `repos` with the list of repos in the next format: | |
| # https://bitbucket.org/workspace/repo-slug/src/master/ | |
| ### | |
| ### VARS ### | |
| clientId="wu" # get from bb oauth consumer | |
| clientSecret="TY" # get from bb oauth consumer | |
| callbackUrL="http://localhost:8000/callback" # do not touch. Set this as a callback url in the bitbucket oauth consumer. | |
| appPassword="ATBB" # get from bb personal settings |
| FROM golang:1-alpine as build | |
| WORKDIR /src | |
| RUN apk update && apk add --no-cache ca-certificates git | |
| COPY go.mod go.sum ./ | |
| RUN go mod download | |
| COPY . . | |
| WORKDIR /src/cmd/ccc | |
| RUN CGO_ENABLED=0 GOOS=linux go build -o /app/ccc | |
| WORKDIR /src/cmd/ccc-cli | |
| RUN CGO_ENABLED=0 GOOS=linux go build -o /app/ccc-cli |
| Import-Module SqlServer | |
| $DatabaseInstances = @( | |
| "SQL2017", | |
| "SQL2019" | |
| ) | |
| $ServerNameUserFriendly = "web" | |
| $DaysToStore = 4 | |
| $CurrentDate = $(Get-Date -Format "dd-MM-yyyy") | |
| $BackupPathGeneral = "\\u123456.your-storagebox.de\backup\DataBases\$ServerNameUserFriendly\$CurrentDate" |
| param ( | |
| [Parameter(ParameterSetName="Task", Mandatory)] | |
| [string]$Task | |
| ) | |
| Import-Module WebAdministration | |
| function ExportConfigurations { | |
| param ( | |
| $WebsiteList | |
| ) |
| FROM golang:1-alpine as build | |
| WORKDIR /app | |
| RUN apk update && apk add --no-cache ca-certificates | |
| COPY go.mod go.sum ./ | |
| RUN go mod download | |
| COPY . . | |
| WORKDIR /app/cmd/tkp | |
| RUN CGO_ENABLED=0 GOOS=linux go build -o /app/tkp | |
| FROM python:3.10 as integration |
Surprisingly, all the articles that describe setting up CI/CD using Azure DevOps end up at the deployed-somewhat-to-somewhere status. I mean, they take csproj or sln, build it using MSBuild, and transfer the artifact to the release pipeline, in which the artifact is deployed to the web app. But often, this is not the result that we really want to get.
Most likely, we are configuring the CI/CD to provide a unified build and
| #!/usr/bin/env bash | |
| keybasepath="$HOME/.ssh/" | |
| cat $HOME/.ssh/config | awk -v RS= -v FS=\\n -v IGNORECASE=1 -v keybasepath="$keybasepath" ' | |
| { | |
| ip = "" | |
| alias = "" | |
| id_file = "" | |
| username = "" | |
| port = "" | |
| result = "" |
| parameters: | |
| - name: Environment | |
| displayName: Environment | |
| type: string | |
| default: 'Development' | |
| values: | |
| - Development | |
| - Staging | |
| - Production |