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

Format pipeline yaml and tweak application name #1204

Closed

Conversation

simonbaird
Copy link
Member

No description provided.

As per the commentary, I want to use yq to modify the pipelines (see
hack/cut-release.sh in another PR. This changes means we don't get
unrelated formatting diffs.
The idea is that we want to do a TAP build for everything in main.
Let's call the application "ec-main-ci" and have it triggered by
changes to "main" branch.
@simonbaird
Copy link
Member Author

The formatting idea was suggested in #1203 , which I'll rebase on this one.

The app name change is so we can set up a TAP application that runs a build on all changes to main branch.

Copy link

codecov bot commented Dec 11, 2023

Codecov Report

Merging #1204 (677089a) into main (23e2e64) will not change coverage.
The diff coverage is n/a.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #1204   +/-   ##
=======================================
  Coverage   84.31%   84.31%           
=======================================
  Files          67       67           
  Lines        5338     5338           
=======================================
  Hits         4501     4501           
  Misses        837      837           
Flag Coverage Δ
acceptance 69.19% <ø> (ø)
generative 4.31% <ø> (ø)
integration 18.10% <ø> (ø)
unit 76.45% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@simonbaird simonbaird marked this pull request as draft December 11, 2023 16:41
@simonbaird
Copy link
Member Author

The new version of #1203 makes this obsolete.

@simonbaird simonbaird closed this Dec 11, 2023
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