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

Added Azure DevOps pipeline #151

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

Sukriva
Copy link

@Sukriva Sukriva commented Feb 16, 2021

This pipeline extends the base pipeline and defines CI and PR triggers in GitHub

@sonarcloud
Copy link

sonarcloud bot commented Feb 16, 2021

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@codecov
Copy link

codecov bot commented Feb 16, 2021

Codecov Report

Merging #151 (022d6e4) into develop (8a8368c) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff            @@
##           develop     #151   +/-   ##
========================================
  Coverage    84.29%   84.29%           
========================================
  Files          147      147           
  Lines         5080     5080           
========================================
  Hits          4282     4282           
  Misses         798      798           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8a8368c...022d6e4. Read the comment docs.

@vikoivun
Copy link
Member

Is there something to prevent the whole pipeline (up to prod!) from running automatically with this? I think the Azure side would need be to changed first, to prevent this from happening. I understand you've been talking about splitting the pipelines for the different environments.
Also, given that this is a public repository, potentially used by other cities in the future: would it be possible to have this file named something like Helsinki-pipelines.yml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants