Looks like its been broken since gocd/gocd#7872 got shipped last year.
User created gocd/helm-chart#12
3 months ago but there's been no response.
is gocd still a thing?
Yes, GoCD is still a thing. In personally don’t have experience with the helm chart so I may be of limited help.
The team is spread across time zones so not everyone is online at a given time.
FWIW, the agent should work with http URL. We use that in development and no longer bake in TLS termination on the server and leave that up to the user to set up with a reverse proxy.
ok figured it out. the docker image for the agent in https://docs.gocd.org/current/gocd_on_kubernetes/importing_a_sample_workflow.htmlgocddemo/gocd-agent-dind:webinar is running an old version 18.3.0-6540 of the gocd-agent
The tutorial needs to be updated.
USER CASE: a job is running on an agent. This is a long job and require hours. At certain point of the job the agent has problem (nw connection, running out of resources, OS crash). Is there a possibility to move the rest of the job in another agent WITHOUT restart it from the beginning?
@lucaferrarihotmail I’m not sure how that would work in general, GoCD or not. Not saying it isn’t possible, just not straightforward or obvious.
How would a single OS process that crashes in midway be picked up by another process in another host from where it left off? There would have to be some state saved, synchronously, and that would have to be to the new host after recovering from the initial crash. Right?
If you are talking about picking up jobs that didn’t finish in a stage, the GoCD already does this; it doesn’t need to reexecute jobs that have already completed within a stage if the stage fails midway, and can run the jobs that were unfinished or pending.
However, at the task level, this is not possible to continue unfinished tasks on another agent after the original one dies.
2 replies
You cannot use an IP address? But the error indicates a resolution problem.
Anyhow, what do you mean by proxy? Reverse http proxy, forward proxy, or something like SOCKS proxy?
If your DNS is happening over proxy, you might check there first since you got a resolution error.
@lucaferrarihotmail sorry, I don’t know how that would work.
GoCD does not have native support for such a thing, as I imagine no other software would either. This sounds like some custom functionality specific to your application. Sorry about that, nothing we can do here to that specific solution.
Feel free to elaborate on some specifics of your problem to see if there are alternative approaches to solve your problem, other than what you hypothesized.
4 replies
Hi R.Rajalakshmi it would be more helpful to pose a specific question rather than just say that you need help.
Try to be as specific as possible:
- what are you trying to accomplish?
- how did you try to do the above? what approaches did you try so far?
- what actually happened that was different from your expectations?
- were you following the docs and were their parts that were unclear or incorrect? Please link the doc you were referencing.
- is there any useful output, error message, or log that you can post here?
1 reply
Hello! Can a task stop the pipeline without being shown as failed? My use case is a pipeline which deploys on a special staging server whenever there are new commits in the main branch. The pipeline is placed behind our testing pipeline so that it is triggered only when all the tests where successful. This is the task that checks for the main branch:
source ./app_env_vars
if [[ "$APP_CURRENT_BRANCH" == "main" ]]; then
echo "Yes, it's the main branch!"
exit 0
else
echo "That's not the main branch: $APP_CURRENT_BRANCH"
exit 1
fiIt works but it's distracting that the pipeline is shown as failed when the latest tested commits where not in main.
I would like to devise a way to generate a historical test report of common test failures from our test stage in a pipeline. This would be for trend analysis to help us spot and resolve either flakey tests or inconsistent failures which may be genuine but difficult to spot. I have not seen any features on GoCD documentation that lends itself as a solution to this - would anyone on this thread know of any possible solutions to this problem other than building a process from scratch (which may be my option otherwise!) :)
Thanks
2 replies