[go-cd] Upgrade Go Server / Agents with some custom changes

Agents are running through command line and not as a service, because I need them to be interactive. This is blocking for the upgrade somehow? Thanks for your time :-) Best Regards, Diogo Oliveira -- You received this message because you are subscribed to the Google Groups "g

[go-cd] Behavior when trying to sync two pipelines with dependencies and a shared material

red by ancestor pipelines. So, my question is: what is the expected behavior here? :) Thanks in advance! Best Regards, Diogo Oliveira -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving ema

Re: [go-cd] Behavior when trying to sync two pipelines with dependencies and a shared material

clear that it is :) Thanks a lot for your time making this clear! Best Regards, Diogo Oliveira On Thursday, April 13, 2017 at 8:40:14 PM UTC+1, Aravind SV wrote: > > It's a little trickier than that. Another way of drawing your dependencies >

[go-cd] Re: Can we automatically navigate to the last green run of a pipeline?

Hi Sanjay, If you check the Go API documentation, you can retrieve a pipeline history and then be able to fetch its last successful execution. This serves what you are trying to achieve? https://api.gocd.io/current/#get-pipeline-history Best Regards, Diogo Oliveira quinta-feira, 6 de Abril

Re: [go-cd] Upgrade Go Server / Agents with some custom changes

d java 8 on the agent and server machines. > > On Thu, Mar 16, 2017 at 5:07 PM Diogo Oliveira <diogo.o...@outsystems.com > > wrote: > >> Hi everyone, >> Still, I have some questions before I even attemp to test this upgrade: >> >> 1 --> I have custom ports on my

[go-cd] Re: GoCD no compatible revisions were identified?

Hi Vamshi, Please keep in mind that the subsequent pipeline is only triggered after a successful execution the one that it depends on. I'm afraid that I would need more details to be able to help you out. Can you provide more information? Best Regards, Diogo Oliveira segunda-feira, 10 de

[go-cd] Fan In and SVN Externals

Hi guys, I was trying to achieve a fan in behavior while using SVN externals, but the behavior I observed is either a limitation or I'm doing something wrong. So, let me first tell you about my test scenario setup: SVN Branch SVN1: SVN branch which only contains externals inside it (to other

[go-cd] Re: Multiples Pipelines Referring To A Single Material?

Hi, Pipelines are self-contained and they should checkout to their own folders (each pipeline has its own sandbox in what concerns file system, let's say). So, short answer: you cannot do what you're asking by using Go. Still, you can try other things (which I wouldn't recommend anyway): have

[go-cd] Issue upgrading from 17.2.0 to both 18.5.0 or 17.10.0

Hey there, I'm trying to upgrade a Go Server I have using version 17.2.0 to the version 18.5.0. When the server was starting it looked like it got stuck during database initialization. To mitigate the risk of upgrading to a much newer version I tried also to upgrade to 17.10.0 first, and the

[go-cd] Re: Behavior change - users asked for authentication when accessing artifacts via URL

Relevant info: this only happens when the URL contains a folder (which is produced as an artifact). If pointing directly to a file inside that folder it works. On Tuesday, May 22, 2018 at 3:57:09 PM UTC+1, Diogo Oliveira wrote: > > Hey there, > > We were using GoCD 16.2.1

[go-cd] Behavior change - users asked for authentication when accessing artifacts via URL

Hey there, We were using GoCD 16.2.1 and upgraded to 17.10.0 Before, users could access artifacts generated by the pipelines via URL, but now they are prompted to authenticate. We have no authentication configured. Is this expected? Any way we can disable this authentication prompt? Cheers,

Re: [go-cd] Re: Behavior change - users asked for authentication when accessing artifacts via URL

t's the same, open an > issue? Someone can look at whether it was done for a reason. > > Thanks, > Aravind > > On Tue, May 22, 2018 at 10:59 AM Diogo Oliveira <diogo.o...@outsystems.com > > wrote: > >> Relevant info: this only happens when the URL contain

[go-cd] Change SSL Server Certificate - "Keystore was tampered with, or password was incorrect"

Hey there, I have tried to change the SSL Certificate of my Go Server (Windows) but somehow I am not able to get it working. I followed all the instructions here (https://docs.gocd.org/current/installation/ssl_tls/custom_server_certificate.html) adapted to Windows, so basically end up

[go-cd] Re: Change SSL Server Certificate - "Keystore was tampered with, or password was incorrect"

... the password actually becomes 'serverKeystorepa55w0rd' (with ' ' included in the password). So, removing those from the command will do it :) (using GnuWin32 to execute openssl) On Tuesday, February 6, 2018 at 3:49:48 PM UTC, Diogo Oliveira wrote: > > Hey there, > > I have tri

[go-cd] Agents going Lost Contact after a while and warnings in the server about remoteBuildRepository

(Note: I originally opened this as an issue in GitHub, thanks @Aravind SV for pointing me to the right place) We migrated our Go Server to a new server with a PostgreSQL database (without migrating any data), and we created agents with a fresh installation of GoCD Agent. Both server and agents