This is a long shot, but can you ssh into the failing agent machine, kill
the go-agent process and restart it? After that try assigning the failing
job to that agent and see if it works.
On Mon, Jun 21, 2021, 10:47 PM Sushma Gangaiah
wrote:
> Hi Jason,
>
> The builds in these agents were
Hi Jason,
The builds in these agents were successful til these days and there is no
script change done, all of a sudden builds started failing. As I have
mentioned earlier error is regarding not able to archive the application (
know the solution to fix) whereas I am able to build the app locally
Hi Sushma,
I think we may need the actual error message if we are going to be able to
help.
The situation you describe suggests that there is something specific to the
configuration of these 2 Agents that is causing an issue but without the
specific error it will be very difficult to
Hi Jason,
1. Error on go-server is regarding ,not able to archive the
application.(but in agent manually and through command line I can build
the app)
2.yes, we are trying to build android and iOS app, one of the agent is not
able to build android and the other iOS.
3.Yes,All the pipelines on
Hello Sushma,
What errors are you seeing on the Agents? Is the error the same every time?
Are both Agents failing with the same error or are the errors different?
Are all Pipelines failing on these 2 Agents or just some of them?
We are not likely to be able to help without more details around
All,
Hope you are doing fine.
This is very strange scenario,
We have around 8 agents with same configuration. We use pipeline as a code
to run pipeline from Go Server and all of our builds were running
successfully. But since few days only in 2 agents builds are failing
whereas to debug when
