Skip to content
#

pipeline

Here are 2,737 public repositories matching this topic...

andrewm-aero
andrewm-aero commented Aug 2, 2021

Describe the bug

In the official docs, the page for Helm notes that variables can be substituted using the $ character, but do not specify how to escape them. The user should not have to dig through the source code for this information. If this is not a supported feature, then the docs should state this very clearly.

To Reproduce

See https://argo-cd.readthedocs.io/en/stable/user-g

goldmann
goldmann commented Jul 8, 2021

Feature request

Consider this example Task:

apiVersion: tekton.dev/v1beta1
kind: Task
metadata:
  name: resource-example
spec:
  description: Sample Task to show issues with passing parameters to resources.
  params:
    - name: RESOURCE_MEMORY_REQUEST
      type: string
      default: 1Gi
    - name: RESOURCE_MEMORY_LIMIT
      type: string
      default: 2Gi
  ste
Aylr
Aylr commented Dec 28, 2020

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

  1. make a batch from a long query string
  2. run validation
  3. render result to data docs
  4. See screenshot
    <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4
kedro
jx
msvticket
msvticket commented Nov 2, 2018

Summary

When creating docker images for Java applications in the current setup in Jenkins-X the application and all dependencies are all placed in one jar file, meaning it will be in one layer in the docker image.

This means that when new versions of the application are created the unchanged dependencies can't be reused.

It would be a great enhancement if the application code where p

timbaileyjones
timbaileyjones commented Aug 12, 2019

While testing another PR, I found that mu pipeline logs command displays information from the pipelines, but also shows this error:

$ mu pipeline logs
[... normal, expected output ...]
func1 ▶ ERROR  ResourceNotFoundException: The specified log group does not exist.
	status code: 400, request id: f7260741-7f69-4772-b4cc-7c6a9c22d264

This error does not occur with the `-f

Improve this page

Add a description, image, and links to the pipeline 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 pipeline topic, visit your repo's landing page and select "manage topics."

Learn more