Summary

If there is a global default-get-timeout set on the web node, it is not possible to override that timeout for the implicit get step that is used to pull the image_resource configured on a task.

Steps to reproduce

Start up Concourse with default-get-timeout set very low

$ wget https://concourse-ci.org/docker-compose.yml

$ echo "      CONCOURSE_DEFAULT_GET

JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.

http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.

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.

Not sure what the error is, but lint passes in the CI and locally even if exported structs dont have comments.
Most probably, it's an issue with the golangci yaml config we use.

Also we use revive instead of golint (which is deprecated), may be some setting in revive needs to be enabled?

If we check the goreport card, we can see the issues: https://goreportcard.com/report/github.com/jenkins

Currently when calling the MSBuild alias with an MSBuildSettings, we need to set the target using the WithTarget extension method.

MSBuild("./my-app.sln", new MSBuildSettings
{
    Configuration = "Release",
    ToolVersion = MSBuildToolVersion.VS2019,
}.WithTarget("Build")); // <<<###

It would be nice if we could use a property, with a string, which would make it more na

Docker volumes are supported in GH via yaml definitions. We should tell this instead of just throwing an unsupported error.

Since drf_yasg2 is not being maintained anymore, we are left with two options:

1. Move back to drf_yasg, we can do that, but it does not support Openapi 3.0, so really we are left with one option to use https://github.com/tfranzel/drf-spectacular