-
**OWASP Release:** 11.0.0
**Gradle version:** 7.6.4
**Problem:** Task `dependencyCheckAggregate` fails. Both locally on Windows and TeamCity on Linux agent.
**Log:**
```
[14:24:20] : [Step 2…
-
#### I'm opening this issue because:
- [x] npm is crashing.
- [ ] npm is producing an incorrect install.
- [ ] npm is doing something I don't understand.
- [ ] Other (_see below for feat…
-
Hi,
I have a build configuration that doesn't need a "Node.js NVM Installer" step but yet it cannot run and I have the message stated in the title of this issue when I hover over the little bubble ic…
-
We run the scripts in hack/, build/ and the Makefile itself in a Docker container. This adds unnecessary complexity.
The original reason to do that was that we were sharing Teamcity agents with other…
sttts updated
8 years ago
-
I have a following helmfile.yaml
```
environments:
{{- range $index,$item := readDirEntries "./environments" }}
{{ $item.Name }}:
{{- end }}
# Comments:
# You should use ( createNames…
-
Questions:
My requirement is to deploy the artifacts (created in teamcity while compiling the code) via teamcity to dev server through ssh deployer using SFTP , my build agent is runing on windows m…
-
Attempting to use a TeamCity configuration parameter for the Unity version in a build step causes agent requirements to fail with a message below (assuming %unityVersion% is the defined parameter), ra…
-
I was assuming that once I switched my checkout mode from Automatically on Server to Automatically on Agent, the repository + all git info would be pulled for GitVersion to work properly, but that was…
-
It seems to me that setting priority is analogous to setting agent requirements, and should be available on a per-config basis, not just at the project level.
-
Starting today without any changes on our side, this plugin fails to parse the response from PUT, plugin is on version 2.2.1
`
Response received:
Failed while reading the response from: PUT
j…