Yeah, to be totally honest, I already thought we did this! 😅 This is the intended behavior, so we'll need to fix that. Thanks for reporting!

Originally posted by @simskij in containrrr/watchtower#647 (reply in thread)

Goal

Implement --team for remaining fly commands. fly/integration tests should be updated. Cases should be added to the error_handling file as well https://github.com/concourse/concourse/blob/587483424a47f3eebb2ed8e861687b60cccb9ec7/fly/integration/error_handling_test.go#L92

# use default team
fly -t ci <command> <command-options>
# use another team
fly -t ci <command>

Show number of pod restarts in the argo ui.

Motivation

Showing number of pod restart counts in the argo ui will help us to see which pods were restarted and how many times without going to any other monitoring dashboards or running kubectl commands. This will be very helpful feature.

Proposal

By getting the number of restart count, we can add this count at the bottom of each pod as

We are using font-awesome V4 and should migrate to font-awesome V5 which comes with its own vue.js module: https://github.com/FortAwesome/vue-fontawesome

Migration includes removing old font-awesome V4 module and changing all existing icons to new vue.js tag.

This is blocked until #114 is merged which comes with first initial integration.

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

First of all: thanks for working on this project and making it accessible to us!

Context

We are starting the unleash server in the same process as our backend server, using unleash.start().
When we receive a SIGINT or SIGTERm, we want to shutdown cleanly so that node exits on it's own because of an empty event loop.

What we tried

Our current attempt to do this boils down t

Environment

Liquibase Version: 4.0.0

Liquibase Integration & Version: spring boot 2.3.2

Liquibase Extension(s) & Version:

Database Vendor & Version: MySql 8.0.15

Operating System Type & Version: Ubuntu 18.04.3

Description

Fail when t

I was thinking that we could extract the eslint config file into his own module so that we can easily reuse this across any OC related repo in the form of eslint extends.

This because we now have the @opencomponents organization and quite few repos, and i

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

What happened:

Join feature introduced "CREATED" status builds which is a holder build for storing intermediate status of upstream builds which can trigger this job. However UI shows "CREATED" as status for such events and users are able to navigate to such builds and get confused on job's status.

What you expected to happen:

UI should ignore builds with CREATED status.
Users