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

Make a new command to trigger a pipeline #430

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

marcomorain
Copy link
Contributor

No description provided.

@pete-woods pete-woods force-pushed the pipeline-trigger branch 2 times, most recently from a5daeef to c803413 Compare October 2, 2020 14:26
@codecov
Copy link

codecov bot commented Oct 2, 2020

Codecov Report

Attention: 60 lines in your changes are missing coverage. Please review.

Comparison is base (bf399b8) 28.00% compared to head (d39fbfd) 26.89%.
Report is 377 commits behind head on develop.

❗ Current head d39fbfd differs from pull request most recent head 19ce1e9. Consider uploading reports for the commit 19ce1e9 to get more accurate results

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #430      +/-   ##
===========================================
- Coverage    28.00%   26.89%   -1.12%     
===========================================
  Files           42       37       -5     
  Lines         4795     4763      -32     
===========================================
- Hits          1343     1281      -62     
- Misses        3267     3355      +88     
+ Partials       185      127      -58     
Files Coverage Δ
api/rest/client.go 67.69% <ø> (-1.96%) ⬇️
cmd/root.go 58.97% <100.00%> (+6.83%) ⬆️
paths/paths.go 100.00% <100.00%> (ø)
cmd/open.go 35.29% <0.00%> (-20.27%) ⬇️
api/pipelines/pipelines.go 76.00% <76.00%> (ø)
cmd/pipeline/pipeline.go 25.35% <25.35%> (ø)

... and 38 files with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@pete-woods pete-woods force-pushed the pipeline-trigger branch 2 times, most recently from 41132e0 to 6279463 Compare October 2, 2020 14:50
@pete-woods
Copy link
Contributor

@marcomorain I took the liberty of tweaking this a bit, adding some tests, using the (hopefully going to be) common REST client

@pete-woods pete-woods force-pushed the pipeline-trigger branch 2 times, most recently from c97bbfd to d39fbfd Compare October 5, 2020 14:08
@JulesFaucherre JulesFaucherre changed the base branch from main to develop October 17, 2023 09:57
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.

3 participants