Skip to content
#

pipelines

Here are 462 public repositories matching this topic...

vito
vito commented Feb 3, 2021

Summary

#6369 tracks the user who created the build (either manual trigger or rerun) and also tweaked the api/v1/user endpoint to contain a new display_user_id field. The new field should be used to show the user in the top bar, since it reflects the same value that Concourse tracks as the build creator.

We should be able to replace [this function](https://github.com/concourse/concour

jrhizor
jrhizor commented Mar 9, 2021

We should check for the existence of a value for something like a --config flag and if the flag represents a file, we should check for its existence at the base level.

Example:

# jrhizor in ~/code/airbyte/airbyte-webapp on git:master ● [10:16:24]
→ docker run --rm airbyte/source-exchangeratesapi-singer:0.1.9 check --config

# jrhizor in ~/code/airbyte/airbyte-webapp on git:master ● [
zenml
hamzamaiot
hamzamaiot commented Feb 10, 2021

Describe the bug
ZenML fails with custom step on no commit git repo.

To Reproduce
Steps to reproduce the behavior:

git init
zenml init
python run.py  # run any pipeline with a custom step

Expected behavior
If there is no commit, make the pipeline un-pinned.

Screenshots

Stack Trace

** Context (please complete the following information):**

  • OS: U
onepanel

The open and extensible integrated development environment (IDE) for computer vision with built-in modules for model building, automated labeling, data processing, model training, hyperparameter tuning and workflow orchestration.

  • Updated Mar 8, 2021
  • Go
remivoirin
remivoirin commented Apr 27, 2020

Hi!

When using the unprivileged image, it's not possible to load custom configurations.

# podman run -p 8080:8080 -e GITLAB_MONITOR_CONFIG=/tmp/config.json timoschwarzer/gitlab-monitor:unprivileged
/wrapper.sh: line 4: can't create /usr/share/nginx/html/config.json: Permission denied

Indeed, root is needed to create a new file in /usr/share/nginx/html, and it looks like wrapper.s

skaegi
skaegi commented Jul 21, 2020

In the docs -- https://github.com/tektoncd/triggers/blob/master/docs/eventlisteners.md#serviceaccountname -- it states that ServiceAccountName is required. In our environment an EventListener author would never know what ServiceAccounts are available so we would like to use "default" in this case or better still follow Tekton Pipelines logic -- https://github.com/tektoncd/pipeline/blob/db66eca6112

Improve this page

Add a description, image, and links to the pipelines topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the pipelines topic, visit your repo's landing page and select "manage topics."

Learn more