Re: [go-cd] Instructions to downgrade gocd-server

2019-10-07 Thread Ketan Padegaonkar
We recommend that users backup their instane, for specifically this reason.
As far as the DB is concerned, the schema in version 19.9 is incompatible
with the schema in version 19.8. So I'm afraid you're out of luck.

Out of curiosity, why are you trying to rollback?

- Ketan



On Mon, Oct 7, 2019 at 2:05 PM AquilaNiger  wrote:

> Hi everyone,
>
> is there any documentation how a downgrade of GoCD server can be
> performed? We currently have 19.9.0 installed and want to roll back to
> 19.8.0. The configuration XML of the old version could be restored from an
> external repository, however there is no other backup data (database ...)
> of the previous version.
> Would the database of 19.9.0 work in a 19.8.0 server? Which files are
> dependent on the exact version and cannot be used from the current version?
> Any help would be appreciated.Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/7d7bb8cc-f480-494e-a584-c4f00d9b5e9d%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd77fn2Dna%2BDm%2BYi1J1nvxFc3N5opLSmO1in4puxwA%2BaFA%40mail.gmail.com.


Re: [go-cd] GoCD page suddenly asking for client certificate

2019-09-17 Thread Ketan Padegaonkar
Do you mind opening an issue on https://github.com/gocd/gocd so we can take
this conversation there?

- Ketan



On Mon, Sep 16, 2019 at 8:19 PM AquilaNiger  wrote:

> Hi,
>
> since we did an upgrade from GoCD 18.x.x (I don't remember) to 19.7.0 all
> of a sudden, when opening the server page in a totally new browser session,
> GoCD is asking for a client certificate. You can press cancel and use the
> page as usual however this behavior is annoying. Does anyone know why this
> is happening and where I can disable the client certificate request?
>
> Any hint and help would be appreciated.
>
> Thanks in advance!
>
> Regards,
> Julia
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/99452628-1d04-4a4c-8a49-77de02e41d6f%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd5fGqu_JtD8nUWu5iACyuH2kcKf7%3DdQf4H0NDuLEE3i9w%40mail.gmail.com.


Re: [go-cd] GoCD Agent Failing to Clean Working Directory - "Unable to delete file"

2019-09-16 Thread Ketan Padegaonkar
I'm assuming you're running on Windows. This can usually happen because of
open file handles. Could you use the sysinternals tools
 to
identify processes that may be holding onto the files after the build
completes?

- Ketan



On Tue, Sep 17, 2019 at 2:21 AM Jason Smyth 
wrote:

> Hello,
>
> We have several Pipelines that are failing during the "clean working
> directory" task of a Job. The only error message provided is "Unable to
> delete file".
>
> This just started recently but I believe that, until recently, these same
> Jobs did not have the "Clean working directory" attribute set so the issue
> has likely existed for some time and we are just discovering it now. The
> issue affects multiple Pipelines but all affected Pipelines follow the same
> pattern:
>
> Stage 1: 1 job
> Stage 2: 2 jobs
>
> The issue only affects 1 Agent but this is the only Agent we have that is
> capable of running these jobs. The issue never seems to affect Stage 1 but
> what we see is that if Stage 1 completes and then Stage 2 for the same
> Pipeline starts immediately, both jobs fail with the same error message
> about being unable to delete a particular file.
>
> If we rerun Stage 2 a few minutes later, both jobs complete successfully.
> I have reviewed the Agent's log file and there is no additional information
> beyond the same "Unable to delete file" error message shown on the console.
>
> The file is inside GoCD's working directory and the GoCD user has full
> control of the entire directory tree so it should not be a permissions
> issue on the file. The file is a normal file, not a symlink that could lead
> outside the working directory to somewhere GoCD does not have access.
>
> How can we get additional information about why GoCD is failing to clean
> the working directory so that we can resolve the issue?
>
> At the moment we are working around the issue by manually re-running
> failed Stages but this is obviously far from ideal.
>
> Any insight here would be appreciated.
>
> Thank you,
> Jason
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/b060bcb6-7ac6-484a-8ae9-c1eb7136dcbd%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd4-%2B39C0JX%2BSoFNKn43LQF13ghOJBTWoj871o9AsTsVOA%40mail.gmail.com.


Re: [go-cd] Error starting go-agent on v19.7

2019-08-15 Thread Ketan Padegaonkar
What gocd version is your server?

On Thu, 15 Aug, 2019, 11:25 Atul Verma,  wrote:

> Hi
>
> I am getting an error when go agent fails to start. trace log below.
> OS is : Amazon Linux AMI 2018.03
> Java: openjdk version "10.0.2" 2018-07-17
> Go agent version: 19.7.0
>
> tried running it on java 1.8 but it fails with same error. any ideas or
> suggestions
>
> ```
> STATUS | wrapper  | 2019/08/15 15:48:20 | <-- Wrapper Stopped
> STATUS | wrapper  | 2019/08/15 15:49:22 | --> Wrapper Started as Daemon
> STATUS | wrapper  | 2019/08/15 15:49:22 | Java Service Wrapper Standard
> Edition 64-bit 3.5.37
> STATUS | wrapper  | 2019/08/15 15:49:22 |   Copyright (C) 1999-2018 Tanuki
> Software, Ltd. All Rights Reserved.
> STATUS | wrapper  | 2019/08/15 15:49:22 |
> http://wrapper.tanukisoftware.com
> STATUS | wrapper  | 2019/08/15 15:49:22 |   Licensed to ThoughtWorks for
> GoCD Agent On Linux
> STATUS | wrapper  | 2019/08/15 15:49:22 |
> STATUS | wrapper  | 2019/08/15 15:49:22 | Launching a JVM...
> INFO   | jvm 1| 2019/08/15 15:49:22 | WrapperManager: Initializing...
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
> Starting process:
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
>  Working directory: /var/lib/go-agent
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
>  Application arguments: [-serverUrl, https://10.x.x.x:8154/go/]
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
>   GoCD Version: 19.7.0-9567
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
>   Java Version: 12.0.1
> INFO   | jvm 1| 2019/08/15 15:49:22 | [Thu Aug 15 15:49:22 AEST 2019]
>   Operating System: Linux(4.14.114-83.126.amzn1.x86_64)
> INFO   | jvm 1| 2019/08/15 15:49:23 | Could not find file
> `config/agent-bootstrapper-logback.xml'. Attempting to load from classpath.
> INFO   | jvm 1| 2019/08/15 15:49:23 | Using classpath resource
> `jar:onejar:lib/agent-bootstrapper-19.7.0-9567-classes.jar!/config/agent-bootstrapper-logback.xml'.
> INFO   | jvm 1| 2019/08/15 15:49:23 | SLF4J: Class path contains
> multiple SLF4J bindings.
> INFO   | jvm 1| 2019/08/15 15:49:23 | SLF4J: Found binding in
> [jar:onejar:lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> INFO   | jvm 1| 2019/08/15 15:49:23 | SLF4J: Found binding in
> [jar:file:/var/lib/go-agent/data/deps-4303b3af29443eb7-agent-launcher.jar/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> INFO   | jvm 1| 2019/08/15 15:49:23 | SLF4J: See
> http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
> INFO   | jvm 1| 2019/08/15 15:49:23 | SLF4J: Actual binding is of type
> [ch.qos.logback.classic.util.ContextSelectorStaticBinder]
> INFO   | jvm 1| 2019/08/15 15:49:23 | Could not find file
> `config/agent-launcher-logback.xml'. Attempting to load from classpath.
> INFO   | jvm 1| 2019/08/15 15:49:23 | Using classpath resource
> `jar:file:/var/lib/go-agent/data/deps-4303b3af29443eb7-agent-launcher.jar/agent-launcher-18.5.0-6679-classes.jar!/config/agent-launcher-logback.xml'.
> INFO   | jvm 1| 2019/08/15 15:49:25 |
> java.lang.reflect.InvocationTargetException
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown
> Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/java.lang.reflect.Method.invoke(Unknown Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> com.thoughtworks.gocd.Boot.run(Boot.java:89)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> com.thoughtworks.gocd.Boot.main(Boot.java:55)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown
> Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
> Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/java.lang.reflect.Method.invoke(Unknown Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> org.tanukisoftware.wrapper.WrapperJarApp.run(WrapperJarApp.java:451)
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> java.base/java.lang.Thread.run(Unknown Source)
> INFO   | jvm 1| 2019/08/15 15:49:25 | Caused by:
> java.lang.NoClassDefFoundError: javax/xml/bind/DatatypeConverter
> INFO   | jvm 1| 2019/08/15 15:49:25 | at
> com.thoughtworks.go.agent.launcher.DownloadableFile.matchChecksum(DownloadableFile.java:72)
> INFO   | jvm 1| 2019/08/15 15:49:25 | 

Re: [go-cd] Test using virtual machines

2019-08-01 Thread Ketan Padegaonkar
On Thu, Aug 1, 2019 at 6:26 AM Denis Troller 
wrote:

> how do I make it so that the piepline chooses one VM to reset and then
> runs the testing jobs on this particular agent ?
>

A cheap way might be to write a file (or some metadata) to a VM if it has
been acquired by a job, if another job tries to acquire it, it must back
off (or try another VM). A really fancy way would be to have another DB
that records which VMs are available and which have been acquired/released
after a build.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd5Z3vwQYKX%2BKaUg7iP2z2vqWmr8eMvOW1BXbze5Fvjh7w%40mail.gmail.com.


Re: [go-cd] Test using virtual machines

2019-08-01 Thread Ketan Padegaonkar
There are 2 possible ways (that I can think of):

   1. Use a set of scripts that runs on an agent. These scripts will
   connects to a VM provider (vmware, virtualbox, ...) to spin up VMs. Then
   connect to the created VM to install, configure and test whatever you need
   to test.
   2. Write an elastic agent plugin for your VM provider
    (or
   use an existing one ).
   Elastic agents can bring up agents in response to build workloads.

I'd think option 1 is probably what you may want to start with, before
diving into option 2.

- Ketan



On Thu, Aug 1, 2019 at 5:57 AM Denis Troller 
wrote:

> We are using GO-CD to build and test our product under Windows. The
> product is a desktop application.
>
> We have a pipeline that builds the product and we use virtual machines
> (under HyperV) to test it in controlled environments. Each VM hosts a GOCD
> agent to carry out the installation and testing of our product.
>
> The system needs to reset the VMs by applying a snapshot before actual
> deployment and testing can occur.
> It is easy to restore the VMs using powershell.
>
> The big-picture pipelines are:
> - Build
> - Hardware-Tests (on a real machine with hardware attached): Copy files,
> Test Application
> - Software-Tests (on a VM): Restore VM, install Application, test
> - Customer-Specific tests (on a VM): Restore VM, install Application, test
>
> This set of pipelines is replicated for each maintenance branch of the
> product (trunk, v1.0.*, v1.1.*... v2.0.*)
>
> Ideally I would like to be able to have any number of VMs available for
> software and customer tests to allow concurrent builds of different
> versions of the product.
> My problem is in modelling this in GOCD since I do no want two pipelines
> to restore the same VM. GOCD can choose a VM agent to cary out the testing,
> but the agent cannot restore its own VM (since it will then disappear and
> be reset, leading to a pipeline failure).
>
> Any idea on how to deal with such an environment ? Or am I doing this
> wrong ? Has anyone implemented something like this before ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/6c3a3cd3-cfb6-469f-ab4a-2ed35b011e1d%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd6S6t1Pjik3V8eyhHuFnZiRZERRBOH3tL1g2FjShU-Ung%40mail.gmail.com.


Re: [go-cd] Gocd in kubernetes Questions

2019-07-30 Thread Ketan Padegaonkar
On Tue, Jul 30, 2019 at 5:37 PM Aravind SV  wrote:

> 2. Assuming that's true, what you mentioned about the self-signed
> certificate is relevant for GoCD versions less than 19.5.0. Since 19.5.0,
> there is a beta feature which allows you to terminate SSL outside. It is
> mentioned in the release notes: https://www.gocd.org/releases/#19-5-0 -
> you shouldn't even need port 8154 in that case.
>

Update: Beginning with version 19.6 of GoCD, this feature is turned on by
default, you really should not need port 8154 at all. Over the next few
releases, we are considering (no promises) making port 8154 optional.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd6wpvVCUZHaDpB4ye8YVWB56a5%3DOmLQgMZRY%2B%3DJu5TzmQ%40mail.gmail.com.


Re: [go-cd] Re: Release announcement - 19.6.0

2019-07-29 Thread Ketan Padegaonkar
Could you please open an issue on GitHub with more details, logs, steps to
reproduce etc?

On Mon, 29 Jul, 2019, 10:12 Shivani Shinde, 
wrote:

> Hi,
> Following up on the issue. My agent still won't connect to server. I have
> tried both ports and manipulated the url (http/https) like-wise. Yet I
> couldn't figure out what is the issue.
> Can you help?
>
> Thanks
>
> On Fri, Jul 26, 2019 at 10:51 AM Shivani Shinde <
> shivani.shi...@alefedge.com> wrote:
>
>> Hi Ankit,
>> I configured the file by changing port number to 8153, still my agent
>> won't connect to server.
>> Agent was working perfectly with 19.5.0 version of GoCD.
>> --
>> The following are the log details in go-agent.log:
>>
>> 2019-07-26 10:42:34,046 ERROR [scheduler-1] AgentHTTPClientController:103
>> - Error occurred when agent tried to ping server:
>> org.springframework.remoting.RemoteAccessException: Could not access HTTP
>> invoker remote service at 
>> [http://:8153/go/remoting/remoteBuildRepository];
>> nested exception is org.apache.http.client.ClientProtocolException: The
>> server returned status code 403. Possible reasons include:
>>- This agent has been deleted from the configuration
>>- This agent is pending approval
>>- There is possibly a reverse proxy (or load balancer) that is
>> terminating SSL. Hint: use port 8154 of the GoCD server. See
>> https://docs.gocd.org/19.6.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies
>> for details.
>> at
>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:226)
>> at
>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:153)
>> at
>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
>> at
>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:213)
>> at com.sun.proxy.$Proxy10.ping(Unknown Source)
>> at
>> com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:98)
>> at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
>> Method)
>> at
>> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(Unknown
>> Source)
>> at
>> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
>> Source)
>> at java.base/java.lang.reflect.Method.invoke(Unknown Source)
>> at
>> org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:65)
>> at
>> org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
>> at
>> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown
>> Source)
>> at java.base/java.util.concurrent.FutureTask.runAndReset(Unknown
>> Source)
>> at
>> java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown
>> Source)
>> at
>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
>> at
>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
>> at java.base/java.lang.Thread.run(Unknown Source)
>> Caused by: org.apache.http.client.ClientProtocolException: The server
>> returned status code 403. Possible reasons include:
>>- This agent has been deleted from the configuration
>>- This agent is pending approval
>>- There is possibly a reverse proxy (or load balancer) that is
>> terminating SSL. Hint: use port 8154 of the GoCD server. See
>> https://docs.gocd.org/19.6.0/installation/configure-reverse-proxy.html#agents-and-reverse-proxies
>> for details.
>> at
>> com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.validateResponse(GoHttpClientHttpInvokerRequestExecutor.java:112)
>> at
>> com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.doExecuteRequest(GoHttpClientHttpInvokerRequestExecutor.java:79)
>> at
>> org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:137)
>> at
>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:202)
>> "/var/log/go-agent/go-agent.log" 1351L, 144803C
>> --
>>
>> Following are details of go-agent-launcher.log
>>
>> 2019-07-26 10:39:12,568 ERROR [WrapperJarAppMain]
>> ServerBinaryDownloader:82 - Couldn't update admin/agent-launcher.jar.
>> Sleeping for 1m. Error:
>> javax.net.ssl.SSLHandshakeException: Received fatal alert:
>> certificate_unknown
>> at java.base/sun.security.ssl.Alert.createSSLException(Unknown
>> Source)
>> at java.base/sun.security.ssl.Alert.createSSLException(Unknown
>> Source)
>> at 

Re: [go-cd] Automate schedule of the pipeline based on the timer.

2019-06-19 Thread Ketan Padegaonkar
Since the configuration is evaluated on the GoCD server, the timezone used
will be that of the server.

- Ketan



On Wed, Jun 19, 2019 at 1:57 PM Rajshri Baghel 
wrote:

> Hi Ganesh,
>
> Thanks for the reply. We also followed the same docs.
> One question, what time zone these builds are triggered? The pipeline
> trigger did not happen at the time I had given in yml but at a different
> time.
>
> Regards,
> Rajshri
>
>
>
> *From: *Ganesh Patil 
> *Date: *Wed, Jun 19, 2019 at 11:13 AM
> *To: * 
>
> Hi Rajshri,
>>
>> You can find more information about timer triggered pipelines here
>> .
>> The format for specifying the cron expression is mentioned here
>> 
>> .
>> The syntax for defining timer configuration in the GoCD YAML pipeline is
>> documented here .
>> And, Here
>> 
>> is an example of a timer triggered pipeline.
>>
>> Let us know if the above resources help!!
>>
>> Thanks,
>> Ganesh
>>
>>
>> On Wed, Jun 19, 2019 at 10:56 AM Rajshri Baghel <
>> rsbag...@thoughtworks.com> wrote:
>>
>>> Hi,
>>>
>>> I am trying to automate the build of the pipeline to run like a cron job
>>> in every certain interval.
>>> Our GOCD instance is setup in a way that we have to do configurations
>>> via yml files and not directly via UI.
>>> I tried few things in yml for scheduling a timed build but it doesn't
>>> seem to work.
>>>
>>> Can you please provide documentation with example for setting timer in
>>> the gocd yml?
>>>
>>> Regards,
>>> Rajshri
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/go-cd/CAONF_r5O4YDphSwGd%2BEdj1MOeYmicAM2bR681k0BgEZMSRwRKQ%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/go-cd/CAHozDacYkc7xWbL16z2jahHrSW7VtEHg0Qnp1hCp9w_BD_Wauw%40mail.gmail.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/go-cd/CAONF_r5W76a1%3D-%3DCja%2B3XgJ3zb%3Dhav38%3DdUiJ%2Bp%3Drf%2Bkt9Fm%3Dg%40mail.gmail.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/CAMUPJd4g7pMpOdQdE6yqKCNaHDu9v5zd%3DH_Uc3Oiyed5CasvfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Storing git repos when using elasticagents

2019-04-26 Thread Ketan Padegaonkar
Mounting a volume is what you'd be expected to do. Mounting the home volume
is also something you may want to consider doing (in order to cache things
like maven/gradle/npm packages). Additionally there is support for git
shallow clone which may help with reducing the overhead for some
repositories.

- Ketan

On Fri, Apr 26, 2019 at 10:14 PM Roberto Yudice 
wrote:

> It looks like when you are using elasticagents it has to fully clone the
> whole repository on every build since the container is destroyed, we have
> some big repos and this adds to our build time.
>
> What would be the best way to avoid having to reclone the whole repo on
> every build when using elasticagents? I assume mounting a volume would work?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Can a GoCD Agent's Token be Recovered?

2019-04-22 Thread Ketan Padegaonkar
Make sure your guid.txt file does not have a trailing newline/whitespace.

- Ketan



On Fri, Apr 19, 2019 at 12:46 AM Jason Smyth 
wrote:

> Hi Ketan,
>
> Thank you for your reply.
>
> I tried what you suggested (including removing the new line from the end
> of the file) but we are still getting the same error.
>
> Any other suggestions?
>
> If it's relevant, running a script directly against a copy of the database
> is a viable option.
>
> Cheers,
> Jason
>
>
> On Thursday, 18 April 2019 12:02:41 UTC-4, Ketan Padegaonkar wrote:
>>
>> Try:
>>
>> cat guid.txt | openssl dgst -sha256 -hmac
>> "TOKEN_GENERATION_KEY_FROM_CONFIG_XML" -binary | base64 > token
>>
>> You may need to remove the newline from the generated `token` file.
>>
>> - Ketan
>>
>>
>>
>> On Thu, Apr 18, 2019 at 8:48 PM Jason Smyth 
>> wrote:
>>
>>> Hello,
>>>
>>> For some unknown reason one of our agents re-registered with a new GUID.
>>> We would like to revert it to its original GUID so that its history is
>>> maintained but we do not have a backup copy of the token.
>>>
>>> We restored the original GUID but now see token errors in the log when
>>> we try to bring the agent online:
>>>
>>> A token has already been issued for this agent.
>>>
>>> Is there a way we can recover the original token from the server or do
>>> we need to just accept the loss of agent history?
>>>
>>> Thanks in advance,
>>> Jason
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Can a GoCD Agent's Token be Recovered?

2019-04-18 Thread Ketan Padegaonkar
Try:

cat guid.txt | openssl dgst -sha256 -hmac
"TOKEN_GENERATION_KEY_FROM_CONFIG_XML" -binary | base64 > token

You may need to remove the newline from the generated `token` file.

- Ketan



On Thu, Apr 18, 2019 at 8:48 PM Jason Smyth 
wrote:

> Hello,
>
> For some unknown reason one of our agents re-registered with a new GUID.
> We would like to revert it to its original GUID so that its history is
> maintained but we do not have a backup copy of the token.
>
> We restored the original GUID but now see token errors in the log when we
> try to bring the agent online:
>
> A token has already been issued for this agent.
>
> Is there a way we can recover the original token from the server or do we
> need to just accept the loss of agent history?
>
> Thanks in advance,
> Jason
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Backing Up GoCD Server Job via the UI doesn't finish

2019-04-11 Thread Ketan Padegaonkar
On Thu, Apr 11, 2019 at 5:05 PM 'Jiten Patel' via go-cd <
go-cd@googlegroups.com> wrote:

> Hey,
>
> GoCD server backups job when triggered via the UI, doesn't seem to
> complete.
>

Could you clarify what you mean? Do you see errors, if yes, where?

Multiple folders are created within the 'serverBackups' folder.
>

There is one (timestamped) folder created per backup, by design.


> There seems to be an error being thrown to do with sending a confirmation
> email. Once the error is thrown, the process seems to begin all over again.
>

Again, where do you see the error, what is the specific error you see.


> We do not have an email configured for our GoCD instance, is this required
> to be able to trigger backups via the UI?
>
> Would a better approach be if we used the API instead?
>

I don't believe the API would really solve your issue. The backup page and
API use the same underlying code.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] JRUBY and SLF4J warnings upon start up

2019-04-08 Thread Ketan Padegaonkar
These warnings can be ignored.

On Tue, Apr 9, 2019, 4:09 AM J Woo  wrote:

> I am on gocd version 18.12 and using the official docker image on docker
> hub from gocd
>
> When gocd is starting up I see warnings about jruby and SLF4J in the logs:
>
> jruby: warning: unknown property jruby.rack.request.size.threshold.bytes
> SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
> SLF4J: Defaulting to no-operation (NOP) logger implementation
> SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further
> details.
>
> From what i can tell i think this comes from server.sh and wanted to see
> if these warnings are normal or I am missing some configuration that will
> eliminate them.
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] How to upgrade from v16 to latest?

2019-03-29 Thread Ketan Padegaonkar
kHere's what you do:

1. Backup your gocd server from the Admin>Backup menu of your gocd server.
2. Shut down the gocd server.
3. Upgrade the java version to version 11 (Only needed if you're on osx or
linux).
4. Upgrade the gocd server to version 19.1. Depending on the size of your
DB, this might take several minutes as it migrates the database. Don't kill
the server while the DB upgrade is in progress
5. Upgrade the java version on all agents to java 11. We also recommend
that you upgrade the GoCD agents to the latest version, although this is
not strictly needed.

- Ketan



On Fri, Mar 29, 2019 at 11:48 AM Shuo Feng  wrote:

> Hi, by now, I have use gocd for about 3 years, and my version is the
> earliest version of v16, I want to upgrade to latest version, but i found
> that all config files and cipher file type changed and also could not load
> config.xml, more than that, I could find any guideline for this procedure,
> So, is there any doc for this kind of upgrading?
> appreciating !!!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Inconsistent Behaviour when Calling Stage History API

2019-03-28 Thread Ketan Padegaonkar
This should not be the case. Do you mind logging a bug?

On Fri, Mar 29, 2019, 2:42 AM Jason Smyth  wrote:

> Hi all,
>
> Maybe I just don't understand how this API is intended to work and/or be
> used but I am trying to build some things that will leverage it and I am
> having a hard time understanding the results I am seeing. We have a GoCD
> instance that includes maybe a couple hundred pipelines. For my tests thus
> far I have only used 2 pipelines but I can definitely expand on that if it
> would be helpful.
>
> With pipeline 1, when I call the Stage History API (GET
> /go/api/stages/:pipeline_name/:stage_name/history), it returns the *first* 10
> instances in reverse order (i.e. 10, 9, 8...1). If I add an offset of 10,
> it returns the next 10 instances in reverse order (i.e., 20, 19...11).
>
> With pipeline 2 the same call returns the *last* 10 instances, in reverse
> order (e.g. 100, 99, 98...91 [not actual values]) and when I add an offset
> of 10 returns the previous 10 (e.g. 90, 89...81).
>
> So, essentially when I query pipeline 1 the pager moves forward through
> time, starting with the oldest instances and when I query pipeline 2 the
> pager moves backwards through time, starting with the most recent
> instances. The only difference in the API calls I am making are the the
> names of the pipelines and stages I am querying.
>
> For comparison, when calling the Pipeline History API for these same 2
> pipelines, both return the most recent instances, moving backwards if an
> offset is provided.
>
> My expectation was that the Stage History API would always behave the way
> the Pipeline History API does but if this is not necessarily the case then
> I will need to redo the logic around my scripts that are using it.
>
> Is this API expected to be inconsistent like this? If not, does anyone
> have any suggestions on what troubleshooting steps I might take to be able
> to figure out what's going on?
>
> Thank you for your time,
> Jason
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GoCD default login page change o another

2019-02-19 Thread Ketan Padegaonkar
Hi —

This looks like a feature request. Mind opening an issue on github and
explaining some usecases or user interactions that you're thinking about?

- Ketan



On Tue, Feb 19, 2019 at 9:49 PM ihor.rudenko via go-cd <
go-cd@googlegroups.com> wrote:

> Hello all!
> may be some one know how to change login page from gocd server with oauth2
> azure AD login page, or equal google etc, or if I have plugin for oauth2
> azure AD , how to force gocd server use my plugin when I get
> http://gocd.server.ip/8153 instead of internal login page.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Building and testing Yaml Config Plugin...

2019-01-24 Thread Ketan Padegaonkar
The ThoughtWorks team uses Intellij (Ultimate Edition), although I suppose
the community edition should work too.

What sort of errors do you see? If you could paste some error messages on
gist.github.com and send a link over, maybe someone can take a look.

- Ketan



On Fri, Jan 25, 2019 at 3:58 AM Jeff  wrote:

> I'm jumping into the deep end of the pool here to try and learn about
> plugin development as well as maybe contribute an idea or two but I've not
> used Gradle before and my natural dev environment is NetBeans 8.2.
>
> I've cloned https://github.com/tomzo/gocd-yaml-config-plugin.git and
> loaded it in NetBeans but I get a bunch of test failures so I'm now trying
> IntelliJ IDEA (community edition).  I think I have it building but if I run
> tests it says it can't find junit.jar.
>
> If I run 'gradlew test' from the command-line, I see 15 failures.
>
> Any hints as to what I'm missing?
>
> What IDE do others recommend when working with gradle and the GoCD plugin
> source?
>
> Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Gocd

2019-01-20 Thread Ketan Padegaonkar
If you have set the permissions properly so that the go user can talk to
the docker daemon over the socket, then perhaps you need to restart the
go-agent service.

- Ketan



On Mon, Jan 21, 2019 at 10:39 AM  wrote:

> Hi all
>
> i tried docker build command and i got this error
>
>
> [go] Task: docker build --no-cache --tag backup:v1.0 --file Dockerfile
> .took: 0.72sexited: 1
> Cannot connect to the Docker daemon. Is the docker daemon running on this
> host?
>
> i added my go user to docker group
>
> and also gave root privileges to go user but still no use
>
> anyone knows how to rectify the problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Unable to retain context between the stages.

2019-01-16 Thread Ketan Padegaonkar
Seems like a similar problem as described here
.

- Ketan



On Wed, Jan 16, 2019 at 3:08 PM  wrote:

> Hi,
>
> I have created a dev/staging pipeline, which has stages such as install,
> unitTest, contractTest, sonarQube, deploy, apiTest..
> So, my quest is to created a file , append the result of every stage (
> lets say Success/Failure ) in the file and finally to publish as .txt file
> as a last step.
> But, I am not able to retain context between the stages in the file...but
> the same work if we have multiple tasks in the stage.
>
> Can anyone please help me on this or suggest an alternate approach of
> doing it so ?
>
> Thanks
>
> 
>
> Disclaimer:
>
> This email and any files transmitted with it are confidential and may be
> privileged. It is intended solely for the above addressee. If you have
> received it in error please delete it and notify the sender. The
> unauthorised use, disclosure, copying, alteration or dissemination of any
> information in this e-mail is strictly forbidden. AirAsia and its affiliates
>  accepts no liability whatsoever that may arise from or in connection
> with this e-mail and/or its contents.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GOCD and TLS1.2 to Bitbucket

2018-12-05 Thread Ketan Padegaonkar
On Wed, Dec 5, 2018 at 6:46 PM 'David Tyman' via go-cd <
go-cd@googlegroups.com> wrote:

> HG pull doesn't work when I try it as no local repository - I tried to do
> a hg clone and got the same error.
>
> Mercurial HG version is 3.1.2 - maybe updating that would help?
>

I can't say for sure, it may possibly be some missing openssl capabilities.
You may want to perhaps google for the specific error message "abort:
error: _ssl.c:510: error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong
version number" or reach out to bitbucket support.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GOCD and TLS1.2 to Bitbucket

2018-12-05 Thread Ketan Padegaonkar
This is a problem with your `hg` binary. The command that's being executed is
here
<https://github.com/gocd/gocd/blob/master/domain/src/main/java/com/thoughtworks/go/domain/materials/mercurial/HgCommand.java#L57>
:

hg pull -b BRANCH --config paths.default=HG_URL

Can you make sure this executes on your agent/server where you're seeing
this error?

- Ketan



On Wed, Dec 5, 2018 at 4:45 PM 'David Tyman' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi Ketan,
> this is from go-server.log
>
> 2018-12-05 11:13:01,931 WARN  [130@MessageListener for
> MaterialUpdateListener] MaterialDatabaseUpdater:112 - [Material Update]
> Modification check failed for material: URL:
> https://drl...@bitbucket.org/drl_admin/Expert.ReturnsEngineer
> java.lang.RuntimeException: Failed to run hg pull command:
> STDERR: abort: error: _ssl.c:510: error:1408F10B:SSL
> routines:SSL3_GET_RECORD:wrong version number
> at com.thoughtworks.go.util.ExceptionUtils.bomb(ExceptionUtils.java:30)
> at
> com.thoughtworks.go.util.ExceptionUtils.bombIf(ExceptionUtils.java:58)
> at
> com.thoughtworks.go.util.ExceptionUtils.bombUnless(ExceptionUtils.java:69)
> at
> com.thoughtworks.go.domain.materials.mercurial.HgCommand.modificationsSince(HgCommand.java:129)
> at
> com.thoughtworks.go.config.materials.mercurial.HgMaterial.modificationsSince(HgMaterial.java:92)
> at
> com.thoughtworks.go.server.service.materials.HgPoller.modificationsSince(HgPoller.java:36)
> at
> com.thoughtworks.go.server.service.materials.HgPoller.modificationsSince(HgPoller.java:27)
> at
> com.thoughtworks.go.server.service.MaterialService.modificationsSince(MaterialService.java:122)
> at
> com.thoughtworks.go.server.materials.ScmMaterialUpdater.insertLatestOrNewModifications(ScmMaterialUpdater.java:56)
> at
> com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.insertLatestOrNewModifications(MaterialDatabaseUpdater.java:142)
> at
> com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.updateMaterialWithNewRevisions(MaterialDatabaseUpdater.java:134)
> at
> com.thoughtworks.go.server.materials.MaterialDatabaseUpdater$2.doInTransaction(MaterialDatabaseUpdater.java:101)
> at
> com.thoughtworks.go.server.transaction.TransactionCallback.doWithExceptionHandling(TransactionCallback.java:24)
> at
> com.thoughtworks.go.server.transaction.TransactionTemplate.lambda$executeWithExceptionHandling$2(TransactionTemplate.java:44)
> at
> org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:133)
> at
> com.thoughtworks.go.server.transaction.TransactionTemplate.executeWithExceptionHandling(TransactionTemplate.java:41)
> at
> com.thoughtworks.go.server.materials.MaterialDatabaseUpdater.updateMaterial(MaterialDatabaseUpdater.java:98)
> at
> com.thoughtworks.go.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:50)
> at
> com.thoughtworks.go.server.materials.MaterialUpdateListener.onMessage(MaterialUpdateListener.java:30)
> at
> com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:73)
> at
> com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:53)
> at java.lang.Thread.run(Thread.java:745)
>
> David
>
> On Wednesday, 5 December 2018 10:27:22 UTC, Ketan Padegaonkar wrote:
>>
>> Can you provide the exact error message that you see?
>>
>> - Ketan
>>
>>
>>
>> On Wed, Dec 5, 2018 at 3:48 PM 'David Tyman' via go-cd <
>> go...@googlegroups.com> wrote:
>>
>>> Hi everybody
>>>  anyone got a wrapper-properties.conf that will allow me to connect Gocd
>>> 18.11 to Bitbucket using https now that it needs to use TLS1.2 - I've tried
>>> : wrapper.java.additional.16="-Dgo.ssl.protocols.include=TLSv1.2,TLSv1.3"
>>> wrapper.java.additional.17="-Dgo.ssl.protocols.exclude=SSLv3,SSLv2,TLSv1,TLSv1.1"
>>>
>>>
>>> but still get a SSL3 wrong version number error ?
>>>
>>> David
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to go-cd+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GOCD and TLS1.2 to Bitbucket

2018-12-05 Thread Ketan Padegaonkar
Can you provide the exact error message that you see?

- Ketan



On Wed, Dec 5, 2018 at 3:48 PM 'David Tyman' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi everybody
>  anyone got a wrapper-properties.conf that will allow me to connect Gocd
> 18.11 to Bitbucket using https now that it needs to use TLS1.2 - I've tried
> : wrapper.java.additional.16="-Dgo.ssl.protocols.include=TLSv1.2,TLSv1.3"
> wrapper.java.additional.17="-Dgo.ssl.protocols.exclude=SSLv3,SSLv2,TLSv1,TLSv1.1"
>
>
> but still get a SSL3 wrong version number error ?
>
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Need to find goCD consultants to support a large scale program...

2018-12-04 Thread Ketan Padegaonkar
If you write to supp...@thoughtworks.com, we may be able to help you out
(or help find a consultant)

On Wed, Dec 5, 2018, 7:42 AM Bill Royce  any suggestions?
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] How to get GoCD v17.5.0 rpm package?

2018-11-30 Thread Ketan Padegaonkar
You can pull it from the yum repository, or use the following urls:

https://download.gocd.org/binaries/17.5.0-5095/rpm/go-server-17.5.0-5095.noarch.rpm
https://download.gocd.org/binaries/17.5.0-5095/rpm/go-agent-17.5.0-5095.noarch.rpm

I would however not recommend downloading and installing such an old
version — it is unsupported and has a lot of known vulnerabilities.

- Ketan



On Fri, Nov 30, 2018 at 8:00 PM Yang Zhang  wrote:

> Dear all:
>
> Cloud you help to let me know where can I get the go-server and
> go-agent RPM package for version 17.5.0 ?
>
> From the official download website(
> https://www.gocd.org/download/#redhat),the oldest version is 17.12.0.
>
> Thanks for you support.
>
> --
> zhangy
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Update failed because the view is out-of-date. Try refreshing the page.

2018-10-31 Thread Ketan Padegaonkar
It's probably to do with your browser cache, or you're attempting to update
personalization across multiple browser windows. Try reloading before
updating the personalization.

- Ketan



On Wed, Oct 31, 2018 at 2:19 PM 'Jiten Patel' via go-cd <
go-cd@googlegroups.com> wrote:

> Hello,
>
> After recently updating to 18.10.XX of GoCD, I've been having some trouble
> filtering the views due to the error message "Update failed because the
> view is out-of-date. Try refreshing the page." Refreshing doesn't seem to
> help much.
>
> The error in the console is:
>
>1. go/api/internal/pipeline_selection
>2. Request Method:
>PUT
>3. Status Code:
>412 Precondition Failed
>
> I was wondering if there was something special required to be able to
> enable this functionality?
>
> Any help would be greatly appreciated.
>
> Regards,
> JP
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Problem when update or restart gocd server in kubenetes

2018-10-25 Thread Ketan Padegaonkar
Does the volume mount for `/godata` have the right permissions as described
in the readme of the docker image? UID:1000, GID:1000.

On Fri, Oct 26, 2018, 7:13 AM Sasa Mitrovic  wrote:

> Hi,
>
> Using K8s for GOCD. He is deployed using Helm chart.
>
> First deployment always works ok. But if you try update, restart or
> anything related with stopping POD and redeploying ( even using persistent
> volume so config is not changed...) I have this error:
>
> some loading before when starting.
> $ exec /go-server/server.sh
> [Fri Oct 26 01:33:28 GMT 2018] Starting process:
> [Fri Oct 26 01:33:28 GMT 2018] Working directory : /go-working-dir
> [Fri Oct 26 01:33:28 GMT 2018] Application arguments: []
> [Fri Oct 26 01:33:28 GMT 2018] GoCD Version: 18.10.0-7703
> Could not find file `/go-working-dir/config/logback.xml'. Attempting to
> load from classpath.
> Using classpath resource
> `jar:onejar:lib/server-launcher-18.10.0-7703-main.jar!/config/logback.xml'.
> Error trying to validate file cruise-config.xsd:
> java.io.FileNotFoundException: /go-working-dir/config/cruise-config.xsd
> (Invalid argument)
> /go-working-dir/db/h2deltas/10_add_stage_timestamp.sql (Invalid argument)
>
> So he stops there always!
>
> Just to note, files are all there
>
> I'm using GOCD 4y and mostly not have any problems when regular server is
> in question, but with K8s now trying to do some things
>
> Any advice here?
>
> Did someone else experience this error?
>
> Thanks.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] java.security.cert.CertificateException: No subject alternative names present

2018-10-18 Thread Ketan Padegaonkar
Could you send across the output of `openssl s_client -connect HOST:PORT`,
and perhaps I could advice? Also, the full stacktrace please.

On Fri, Oct 19, 2018, 2:34 AM Nikos Skalis  wrote:

> Hi,
>
> I am trying to integrate with my company's LDAP for authentication and
> authorisation.
> Before I make such an attempt,
>
> when clicking on the "Check Connection" it complains about:
> java.security.cert.CertificateException: No subject alternative names
> present
>
> the url looks like this: ldaps://172.31.x.x:636
>
> Could you please advise how to resolve this ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Does gocd have the feature?

2018-10-01 Thread Ketan Padegaonkar
Our recommendation is to simply check in any scripts into version control
and execute that. But if for some reasons you'd prefer to not do that, you
can use the script executor plugin
 to execute arbitrary
commands via shell.


- Ketan



On Mon, Oct 1, 2018 at 11:43 AM Aleksandr Tceluiko  wrote:

> Octopus deploy has excellent feature. You can run arbitrary command in a
> shell on a set of deployment targets. Does gocd have anything like that?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] a trouble with "Fetch Materials" for package repositories

2018-09-25 Thread Ketan Padegaonkar
Most package repo plugins will setup an environment variable containing the
URL of the artifact, along with some additional metadata (version,
co-ordinates, etc). The expectation is that any scripts in the task will
download the artifact and use them as they see fit.

See:

https://github.com/1and1/go-maven-poller#published-environment-variables
https://github.com/1and1/go-maven-poller#downloading-the-package

- Ketan



On Tue, Sep 25, 2018 at 2:42 PM Роман Щербаков <
scherbakov.roman@gmail.com> wrote:

> Hi! I have a package repository (Maven). And I use it as a material for my
> pipeline. Connection with the repo is OK. I turned on the "Fetch Materials"
> option and turned off the "Clean Working Directory" option, but after my
> pipeline starts or done, there are no any files of my package in the
> working directory (/var/lib/go-agent/pipelines/MyPipeline/). What should I
> do to fix it or maybe "Fetch Materials" is designed for something else?
> Thanks for any help
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Help needed with logstash-logback-encoder

2018-09-13 Thread Ketan Padegaonkar
Do you have a stacktrace of the error? What jars did you copy to the lib
dir?

On Thu, Sep 13, 2018, 7:47 PM Allan Benson  wrote:

> Hi
>
> Following these instructions
> ,
> I've downloaded the source code for logstash-logback-encoder, created jar
> files (described here
> )
> and copied them to the goserver\lib dir (on a Windows server). I've added a
> logback-include.xml file (Identical to the one on the instructions, just
> with a different IP in the destination) into the goserver\config dir. When
> I start the service, I get this error (log file attached):
>
> ERROR in ch.qos.logback.core.joran.action.AppenderAction - Could not
> create an Appender of type
> [net.logstash.logback.appender.LogstashTcpSocketAppender].
> ch.qos.logback.core.util.DynamicClassLoadingException: Failed to
> instantiate type net.logstash.logback.appender.LogstashTcpSocketAppender
>
> Does anyone know where I'm going wrong? Are there any downloadable
> versions of the jar files?
>
> Thanks
>
>
>
>
>
> **
> Important Note
> This email (including any attachments) contains information which is
> confidential and may be subject to legal privilege.  If you are not the
> intended recipient you must not use, distribute or copy this email.  If you
> have received this email in error please notify the
> sender immediately and delete this email. Any views expressed in this
> email are not necessarily the views of IRESS Limited.
>
> It is the duty of the recipient to virus scan and otherwise test the
> information provided before loading onto any computer system.
> IRESS Limited does not warrant that the information is free of a virus or
> any other defect or error.
>
> **
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[go-cd] Re: Converting XML Config to YAML Config

2018-09-10 Thread Ketan Padegaonkar
Checkout: https://github.com/ketan/gocd_xml_to_groovy. I would not call
this "complete" or "done", but if anyone is willing to work with me — I'm
happy to accept PRs :)

I'd been hacking on this for some time. It spits out groovy (sorry no YAML
or JSON). The code is not very pretty, (it's just erb templates to generate
groovy code), but seems to work so far.

On Fri, Sep 7, 2018 at 12:51 PM Ashwanth Kumar 
wrote:

> Apologies for cross-posting on both Dev and User mailing list.
>
> Hello,
>
> I was just wondering, is there a tool of sorts which would help us convert
> the existing XML based config to a YAML or JSON based config? We've quite a
> few complex pipelines which we would like convert to JSON for using them
> via config-repo. For the migration we were wondering if there's an existing
> tool or a script someone has written for such migrations already.
>
> --
>
> Ashwanth Kumar / ashwanthkumar.in
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[go-cd] Release Announcement - 18.4.0

2018-05-09 Thread Ketan Padegaonkar
Hey All,

A new version (18.4.0) of GoCD is out.

Know more about the features and bug fixes in this release 
 here or head to our downloads 
 page to try it.

Cheers,
GoCD Team

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Untar'ing a fetched artifact fails - well, kind of...

2018-04-20 Thread Ketan Padegaonkar
You can also turn on some shell logging by using `/bin/sh -xc
YOUR_COMMAND_STRING`

On Fri, Apr 20, 2018 at 2:30 PM Ketan Padegaonkar <
ketanpadegaon...@gmail.com> wrote:

> You may be able to get something by turning on the log level for the
> logger `com.thoughtworks.go.util.command.CommandLine`. More information on
> turning on logging is here
> <https://docs.gocd.org/current/advanced_usage/logging.html>. You should
> turn on this log on the agent, not the server.
>
>
> On Fri, Apr 20, 2018 at 2:20 PM David Joos <david.j...@gmail.com> wrote:
>
>> Anyone got a heads up on how to up the CommandLine component error
>> logging to find out why the custom command fails? Got pulled away on
>> something else, hoping to get some time to dig deeper today.
>>
>> Thanks in advance!
>>
>> 2018-04-17 16:07 GMT+01:00 David Joos <david.j...@gmail.com>:
>>
>>> Also: when changing (just out of desperation) the custom command to a
>>> simple echo, it fails as well - for that project...
>>>
>>> I'll have a look at whether I can get trace logging on the CommandLine
>>> component on the agents, so hopefully something more useful can be
>>> unearthed (FYI: we're using GoCD 18.2)
>>>
>>> Thanks in advance for ideas/pointers!
>>> David
>>>
>>> 2018-04-17 16:03 GMT+01:00 David Joos <david.j...@gmail.com>:
>>>
>>>> Hi guys,
>>>>
>>>> thanks for the feedback!
>>>>
>>>> Re: config XML snippet
>>>> ```
>>>> **
>>>> *  -c*
>>>> *  tar xvzf "#{ARTIFACT_PROJECT_NAME}.tar.gz"*
>>>> *  *
>>>> **
>>>> ```
>>>> FYI: this is part of a template used successfully across other projects.
>>>>
>>>> Re: /bin/sh
>>>> ...when SSH'ing in and running `/bin/sh -c "tar xvzf project.tar.gz"`
>>>> on the GoCD agent (FYI: it fails on different agents for this pipeline -
>>>> agents that fetch and untar other pipelines without any issues in the same
>>>> environment) it works as expected. That is what baffles me the most.
>>>>
>>>> If there would be at least a bit more to go on somewhere than from the
>>>> console tab:
>>>> *[go] Task: fetch artifact [project.tar.gz] => [] from
>>>> [build_project/package/package]took: 0.224s*
>>>> *[go] Task: /bin/sh -c "tar xvzf \"project.tar.gz\""took: 0.0s*
>>>>
>>>> *[go] Task status: failed, took: 0.0s[go] Current job status: failed*
>>>>
>>>> Thanks!
>>>> David
>>>>
>>>>
>>>>
>>>> 2018-04-17 15:49 GMT+01:00 Aravind SV <arv...@thoughtworks.com>:
>>>>
>>>>> Hello David,
>>>>>
>>>>> Can you share the XML snippet from the config? I'd expect it to be
>>>>> something like this:
>>>>>
>>>>> 
>>>>>   -c
>>>>>   tar xvzf "artifact.tar.gz"
>>>>> 
>>>>>
>>>>> Is it?
>>>>>
>>>>> It shouldn't be like this:
>>>>>
>>>>> 
>>>>> 
>>>>>
>>>>> since that is telling it to look for a command with that filename.
>>>>>
>>>>> Cheers,
>>>>> Aravind
>>>>>
>>>>>
>>>>> On Tue, Apr 17, 2018 at 10:37 AM, David Joos <david.j...@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Anyone got any ideas on how to bump the GoCD agent's error log to
>>>>>> trace so to hopefully get some more background info as to what is going 
>>>>>> on?
>>>>>> FYI: when replacing tar with any other custom command, it fails as
>>>>>> well for this specific pipeline (template used on other pipelines without
>>>>>> any issues) - not sure what is causing this, hence more noisy error logs
>>>>>> would be really helpful :-)
>>>>>>
>>>>>> Thanks in advance!
>>>>>> David
>>>>>>
>>>>>> 2018-04-13 18:17 GMT+01:00 David Joos <david.j...@gmail.com>:
>>>>>>
>>>>>>> Hi there,
>>>>>>>
>>>>>>> I've got a pipeline template where after fetching an artifact (eg.
>>>>>>> artifact.tar.gz) successfully, we untar th

Re: [go-cd] Untar'ing a fetched artifact fails - well, kind of...

2018-04-20 Thread Ketan Padegaonkar
You may be able to get something by turning on the log level for the logger
`com.thoughtworks.go.util.command.CommandLine`. More information on turning
on logging is here
. You should
turn on this log on the agent, not the server.


On Fri, Apr 20, 2018 at 2:20 PM David Joos  wrote:

> Anyone got a heads up on how to up the CommandLine component error logging
> to find out why the custom command fails? Got pulled away on something
> else, hoping to get some time to dig deeper today.
>
> Thanks in advance!
>
> 2018-04-17 16:07 GMT+01:00 David Joos :
>
>> Also: when changing (just out of desperation) the custom command to a
>> simple echo, it fails as well - for that project...
>>
>> I'll have a look at whether I can get trace logging on the CommandLine
>> component on the agents, so hopefully something more useful can be
>> unearthed (FYI: we're using GoCD 18.2)
>>
>> Thanks in advance for ideas/pointers!
>> David
>>
>> 2018-04-17 16:03 GMT+01:00 David Joos :
>>
>>> Hi guys,
>>>
>>> thanks for the feedback!
>>>
>>> Re: config XML snippet
>>> ```
>>> **
>>> *  -c*
>>> *  tar xvzf "#{ARTIFACT_PROJECT_NAME}.tar.gz"*
>>> *  *
>>> **
>>> ```
>>> FYI: this is part of a template used successfully across other projects.
>>>
>>> Re: /bin/sh
>>> ...when SSH'ing in and running `/bin/sh -c "tar xvzf project.tar.gz"` on
>>> the GoCD agent (FYI: it fails on different agents for this pipeline -
>>> agents that fetch and untar other pipelines without any issues in the same
>>> environment) it works as expected. That is what baffles me the most.
>>>
>>> If there would be at least a bit more to go on somewhere than from the
>>> console tab:
>>> *[go] Task: fetch artifact [project.tar.gz] => [] from
>>> [build_project/package/package]took: 0.224s*
>>> *[go] Task: /bin/sh -c "tar xvzf \"project.tar.gz\""took: 0.0s*
>>>
>>> *[go] Task status: failed, took: 0.0s[go] Current job status: failed*
>>>
>>> Thanks!
>>> David
>>>
>>>
>>>
>>> 2018-04-17 15:49 GMT+01:00 Aravind SV :
>>>
 Hello David,

 Can you share the XML snippet from the config? I'd expect it to be
 something like this:

 
   -c
   tar xvzf "artifact.tar.gz"
 

 Is it?

 It shouldn't be like this:

 
 

 since that is telling it to look for a command with that filename.

 Cheers,
 Aravind


 On Tue, Apr 17, 2018 at 10:37 AM, David Joos 
 wrote:

> Anyone got any ideas on how to bump the GoCD agent's error log to
> trace so to hopefully get some more background info as to what is going 
> on?
> FYI: when replacing tar with any other custom command, it fails as
> well for this specific pipeline (template used on other pipelines without
> any issues) - not sure what is causing this, hence more noisy error logs
> would be really helpful :-)
>
> Thanks in advance!
> David
>
> 2018-04-13 18:17 GMT+01:00 David Joos :
>
>> Hi there,
>>
>> I've got a pipeline template where after fetching an artifact (eg.
>> artifact.tar.gz) successfully, we untar the artifact via a custom command
>> (`/bin/sh -c "tar xvzf \"artifact.tar.gz\""`).
>>
>> On a new project we're only seeing failures in GoCDs console tab:
>> ```
>>
>> [go] Task: /bin/sh -c "tar xvzf \"artifact.tar.gz\"" took: 0.23s
>> [go] Task status: failed, took: 0.23s
>>
>> ```
>> ...without any further information on why / what is happening exactly.
>>
>> When executing  `/bin/sh -c "tar xvzf \"artifact.tar.gz\""` command
>> as the 'go' user on the GoCD agent itself via the cli
>> (/var/lib/go-agent/pipelines/artifact_pipeline_name), the command untars
>> the file perfectly, as expected. `echo $?` also underlines the command
>> exited cleanly (0), so I'm unsure why we don't get to see this when GoCD
>> runs the task...
>>
>> Is there any more verbose logging I could turn on/dig into on the
>> GoCD agent to get to the bottom of this issue? This has been baffling me
>> for too long now :-)
>>
>> Thanks in advance for your help!
>>
>> Kind regards,
>> David
>>
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to go-cd+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google
> Groups "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit 

Re: [go-cd] Purged flyweight directory

2018-04-18 Thread Ketan Padegaonkar
I'd suggest stopping the server, moving the flyweight out of its current
location (to back it up) and bringing back the server back online. It may
take several minutes after the server comes online for the material checks
to happen. If there are specific errors that you see, we suggest that you
run those commands in the flyweight directory to make sure they can execute
(they may indicate issues with credentials, and bad urls, incorrect branch
names, among other things).



On Wed, Apr 18, 2018 at 9:05 PM Christopher Yocum <
christopher.yo...@gmail.com> wrote:

> Relatively new to GOCD and inherited our environment after the previous
> engineer left the company. Seeing disk space issues on the partition that
> the flyweight dir is stored so, after reading a topic here that it was safe
> and would be rebuilt, I purged most of the unique dirs from within the
> flyweight dir. Chaos has since ensued and I'm lost. Tons of errors in the
> log about "modificatuion check failed" due to "error performing command":
>
> 2018-04-18 15:09:18,249  WARN [100@MessageListener for
> MaterialUpdateListener] MaterialDatabaseUpdater:115 - [Material Update]
> Modification check failed for material: URL: 
> g...@foo.net:docker/elastalert.git,
> Branch: master
> java.lang.RuntimeException: Error performing command: --- Command ---
> git config remote.origin.url
>
> 2018-04-18 15:09:18,383  WARN [99@MessageListener for
> MaterialUpdateListener] MaterialDatabaseUpdater:115 - [Material Update]
> Modification check failed for material: URL: 
> g...@foo.net:payments/customer-portal-env-config.git,
> Branch: ci_test
> com.thoughtworks.go.util.command.CommandLineException: Error performing
> command: --- Command ---
> git log -1 --date=iso --pretty=medium origin/ci_test
>
> The flyweight directory is not rebuilding/recloning as I expected it would
> and this has halted development entirely.
>
> I've restarted the go-server and go-agent services, I've tried to enable
> debug logging for the git material, etc, but I'm totally lost and in a
> really bad situation.
>
> Any/all help is greatly appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Untar'ing a fetched artifact fails - well, kind of...

2018-04-17 Thread Ketan Padegaonkar
I'd probably run `/bin/sh -c env` to dump all the environment variables to
check if there's something in there that may be causing issues.

Sometimes it's just the wrong PATH, or LD_LIBRARY_PATH, or a dozen other
variables that can cause this to not work as expected.

I'd also try using `/bin/bash` instead of `/bin/sh`. `/bin/sh` on some
linux distributions is a minimal shell with very little in the way of
showing error messages when things go as expected.

On Fri, Apr 13, 2018 at 10:47 PM David Joos  wrote:

> Hi there,
>
> I've got a pipeline template where after fetching an artifact (eg.
> artifact.tar.gz) successfully, we untar the artifact via a custom command
> (`/bin/sh -c "tar xvzf \"artifact.tar.gz\""`).
>
> On a new project we're only seeing failures in GoCDs console tab:
> ```
>
> [go] Task: /bin/sh -c "tar xvzf \"artifact.tar.gz\"" took: 0.23s
> [go] Task status: failed, took: 0.23s
>
> ```
> ...without any further information on why / what is happening exactly.
>
> When executing  `/bin/sh -c "tar xvzf \"artifact.tar.gz\""` command as the
> 'go' user on the GoCD agent itself via the cli
> (/var/lib/go-agent/pipelines/artifact_pipeline_name), the command untars
> the file perfectly, as expected. `echo $?` also underlines the command
> exited cleanly (0), so I'm unsure why we don't get to see this when GoCD
> runs the task...
>
> Is there any more verbose logging I could turn on/dig into on the GoCD
> agent to get to the bottom of this issue? This has been baffling me for too
> long now :-)
>
> Thanks in advance for your help!
>
> Kind regards,
> David
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Agent Health API endpoint

2018-04-06 Thread Ketan Padegaonkar
I suspect that you're accessing the endpoint remotely. For security reasons
— the endpoint is only bound to the local-loop interface (localhost/
127.0.0.1). So you'll have to invoke with `localhost/127.0.0.1` instead of
whatever host/ip you're using.

If you'd like to bind this to a different IP or all IPs on the machine, for
external use by an external LB, or monitoring tool, for example — then you
probably need to go through this documentation
.

If you're seeing some other issues — then you probably need to provide a
few steps on how one can go about reproducing the issue.

On Fri, Apr 6, 2018 at 8:40 PM Paul Ryan 
wrote:

> I have a server and agent running v18.2.0.  Running the Agent Health
> endpoint as documented in the GoCD API Reference
>  returns a 404. Other API
> endpoints and my pipelines are all running fine.  I have tried both
>
> `/health/v1/isConnectedToServer` and `/health/latest/isConnectedToServer'
> as detailed in the reference.
>
> If anyone has got this to work, some tips would be much appreciated.
>
>
> disclaimer 
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Go git repo has grown to 60k+ commits

2018-03-21 Thread Ketan Padegaonkar
Is a long commit history being a problem for you that you need it to be
pruned out? Usually this should not be needed.



On Wed, Mar 21, 2018 at 10:35 PM Gopal Singhal 
wrote:

> Hi,
>
> Our Go servers git repo's commit history has grown to over 60k commits. Is
> it possible to purge or flatten all the commits older than an year or so?
>
> Thanks,
> Gopal
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] How to know which upstream pipeline triggered my pipeline ?

2018-03-13 Thread Ketan Padegaonkar
Release 18.2 added a bunch of `GO_MATERIAL_*_HAS_CHANGED` variables to
indicate which of the materials have changed. Check the release notes for
more.

On Tue, Mar 13, 2018 at 6:17 PM Ajay Prasanna  wrote:

> Dear All,
>
> Good day!
> I am new to gocd and already tried searching for a solution. No help.
>
> I have the following scenario:
>
> Pipe1---|---MyPipe
> Pipe2---|
> Pipe3---|
>
> MyPipe has 3 upstream pipes. Changes in Pipe1,2 or 3 triggers MyPipe.
>
> I want to know which out of the 3 upstream pipe triggered MyPipe. Based on
> this information, I will fetch only that artifact and build my software
> (only for that PipeX specific arguments) and do further things in MyPipe
>
> How can I get this information in MyPipe ?
>
> Thanks in advance.
>
> Kind Regards,
> Ajay
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Dependent Pipelines that share Git Material

2018-03-12 Thread Ketan Padegaonkar
You're using a mono repo. Use this plugin
.

On Tue, Mar 13, 2018 at 11:04 AM  wrote:

> Hi, I am not sure of the actual expected behaviour, but I can't see an
> obvious way to work around the issue if it is expected.
>
> The setup is:
>
> A single git repository, with two sub directories:
>
> g...@github.com:example/example
>   project-a
>   project-b
>
>
> There is a pipeline for project-a, that uses the git repository as
> material. It has a whitelist such that it _only_ triggers if there is a
> change for project-a. The project-a pipeline publishes an artifact.
>
> There is a pipeline for project-b, again it uses the git repository as
> material, this time having a whitelist such that it _only_ triggers if
> there is a change for project-b. It depends on the artifact from the
> project-a pipeline.
>
> If a change is made to project-a, its pipeline is triggered, when it
> passes, project-b kicks off as a dependency, which works as expected.
>
> If a change is made to project-b, nothing is triggered (I am guessing
> because it wants to share material with project-a that hasn't been
> triggered). This means that changes to project-b never get built until
> someone changes project-a as well, which is not what is desired. What we
> would like to happen, is project-b kicks off with the changes and uses the
> last artifact published by project-a (which is what would happen if
> project-a and project-b were in different repositories, basically want the
> pipelines to be independent).
>
> Is there anyway to get this set-up working as desired?
>
> Cheers
> Mark
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] custom command with quotes in argument on windows go-agent

2018-03-12 Thread Ketan Padegaonkar
The stuff in `` may need XML escaping as appropriate, I'm just
providing an example below. Consider putting in powershell code in a
powershell script and invoking that script instead, since it's much more
straight forward to do.


  analyze
  /TargetExecutable="c:\Program Files (x86)\NUnit
2.6.4\bin\nunit-console.exe"
  ...


On Sat, Mar 10, 2018 at 5:11 AM Marat <195...@gmail.com> wrote:

> I am running code coverage job on windows go agent and trying to pass
> dotcover custom command with following arguments:
>
> analyse
> /TargetExecutable="c:\Program Files (x86)\NUnit
> 2.6.4\bin\nunit-console.exe"
> /TargetArguments="/nologo /noshadow /include=Test /xml=result.xml
> src\bin\Test.dll"
> /Output=Test.html
> /ReportType=HTML
> /Filters=-:module=Test
>
> Gives following error
>
> [go] Task: dotcover analyse "/TargetExecutable=\"c:\Program Files
> (x86)\NUnit 2.6.4\bin\nunit-console.exe\"" "/TargetArguments=\"/nologo
> /noshadow /include=Test /xml=result.xml src\bin\Test.dll\""
> /Output=report\Test.html /ReportType=HTML
> /AttributeFilters=*.ExcludeFromCodeCoverage /Filters=-:module=Test
> took: 0.390s
> JetBrains dotCover Console Runner 2017.3.3. Build 111.0.20180302.72821
> Copyright (c) 2009-2018 JetBrains s.r.o. All rights reserved.
> Failed to parse xml parameters
> Configuration file is not found
> Type 'dotCover help' for usage.
>
> I have tried so many different options to escape those quotes, but still
> cannot make it work.
>
> What can I try to pass it correctly? Any suggestions are appreciated.
>
> Thank you.
>
> similar cases:
> https://github.com/fsharp/FAKE/issues/1091
> https://github.com/gocd/gocd/issues/2153
> https://github.com/gocd/gocd/issues/4173
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[go-cd] Release announcement 18.2

2018-03-08 Thread Ketan Padegaonkar
Hey All,

A new version (18.2) of GoCD is out.

Know more about the features and bug fixes in this release 
 here or head to our downloads 
 page to try it.

Cheers,
GoCD Team

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Jenkins-style "Configuration Matrix"

2018-02-21 Thread Ketan Padegaonkar
I've been working on a groovy based DSL to define your pipeline. Since it's
all code, you can create the usual programming constructs to generate a
matrix.

The code and some binaries are available, please read this note

before you use it.


On Wed, Feb 21, 2018 at 4:30 AM David Rice  wrote:

> Perhaps pipeline templates
>  and
> parameters
> 
> could help you? (Both are supported by YAML cofig repo if you still wanted
> to go that route.)
>
> On Tue, Feb 20, 2018 at 2:17 PM, Andrew Jones 
> wrote:
>
>> Our build pipeline includes builds of our main project in multiple
>> configuration/platform combinations (eg: Release/x64, Debug/x64,
>> Release/RISC, Debug/RISC). We currently handle this by duplicating the
>> contents of the job (each copy setting environment variables differently),
>> but this creates a maintenance issue when we need to make changes to the
>> job. I believe I could use the YAML config repo to do this but support for
>> anchors & aliases in gocd-yaml-config-plugin is undocumented. How have
>> others handled similar requirements in their build pipelines?
>>
>> Because of the size of our solution building all configuration/platform
>> combinations within a single job (via a batch file or similar scripting)
>> would not work.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Does GoCD supports webhooks from Gitea?

2018-02-01 Thread Ketan Padegaonkar
GoCD currently does not have this support. But if you have an instance of
of gitea running, it should be fairly straight forward to implement it. Here

is the that implemented bitbucket support which might be useful to
implement. You'd basically be expected to implement some callbacks to
extract some information to construct the repo URL and branch information
and to verify the authenticity of the payload (to make sure that someone
pretending as gitea don't end up triggering your pipelines).



On Thu, Feb 1, 2018 at 3:21 PM 'Peter Scheler' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi,
>
> I use GoCD and Gitea behind a firewall. Does go support webhooks from
> Gitea  like it handles them from
> Github?
>
> If not, can you add this API?
>
> Greetings Peter
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GOCD Local account is not getting authenticated.

2018-01-18 Thread Ketan Padegaonkar
You may need to create the local password user in the new GoCD server,
after the restore operation. You can also look at the ldap and password
plugin logs to see if there are any errors there.

On Thu, Jan 18, 2018 at 1:42 PM  wrote:

> Hi,
>
> We are using GOCD 17.2 version in our Production system and which is
> integrated with ldap. So all user accounts was created and authenticated
> using ldap. As we are in aprocess of migrationg gocd from the current
> server to another server, we have created a local account first in GOCD by
> using the GOCD password file process.
>
> Then we have taken the GOCD backup and restored  in new server, but we
> cant login using the local account which we created. So how can make login
> to the migrated server now. as its b;locking further setup of migration.
>
> Please help us with a quick assistance here
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] flyweight - what is it and is it safe to delete?

2018-01-10 Thread Ketan Padegaonkar
*tl;dr;*

Yes the flyweight directory is safe to delete. Make sure to shutdown your
server to avoid any issues later. Depending on the number size of
materials, your server may take several minutes to clone these again at
startup.



*The long version*

For some centralized SCMs like subversion and TFS, it's possible to do an
update-check on a remote repository URL. For distributed SCMs like git and
mercurial, the only way to check if new there are any new commits (and see
the contents of the commits) is to clone the repository. These clones live
in the flyweight directory. The server currently does not purge the
contents of the flyweight directory when a material is removed.



On Thu, Jan 11, 2018 at 9:44 AM Gopal Singhal 
wrote:

> Hi,
>
> In our Go server, flyweight
> directory /var/lib/go-server/pipelines/flyweight has grown to over 200Gb
> with some directories even older than 2 years.
>
> Is it safe to remove old directories may be like any directory older than
> 6 months?
>
> What is the significance of flyweight directories. e.g.
> (3927bc06-d4a7-4a25-a6bc-4e3e1e96d07f)? What I could make out is it is
> somewhere related to materials and polling.
>
> Thanks,
> Gopal
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] logback to a logstash server

2018-01-10 Thread Ketan Padegaonkar
This script <https://gist.github.com/ketan/66af4070900ef22437e279be71288b35>
worked for me, I was able to confirm that logs were sent to logback.

On Wed, Jan 10, 2018 at 8:51 PM 'Barry Greenwood' via go-cd <
go-cd@googlegroups.com> wrote:

> Thanks for the update
>
> That folder didnt exist on our server, I have added with go permissions,
> I've added the files but it still isnt working.
>
> as this isnt the first issue i've had regarding this recently implemented
> feature can you please confirm that it works and should the logs show it
> being loaded ?
>
> Many thanks
>
> Barry
>
>
> On Wednesday, 10 January 2018 13:56:09 UTC, Ketan Padegaonkar wrote:
>
>> The `libs` dir is relative to the working directory of the server/agent.
>> This should typically be `/var/lib/go-server/libs` or
>> `/var/lib/go-agent/libs`. I'll update the documentation to clarify this.
>>
>>
>> On Wed, Jan 10, 2018 at 6:29 PM 'Barry Greenwood' via go-cd <
>> go...@googlegroups.com> wrote:
>>
> Hi all
>>>
>>> I've now got logback able to log to local files with access requests and
>>> other logs, I am now hoping to ship these to an external logstash server
>>>
>>> reading
>>> https://docs.gocd.org/current/advanced_usage/logging.html#advanced-logging-features
>>> this should be possible, however its a little abiguous with "download
>>> all logstash-logback-encoder jars and dependencies into libs dir:"
>>>
>>> I presume its a java library folder as these are jar files but testing
>>> with these in several places that are in the java.library.path, it isn't
>>> working.
>>>
>>> Has anyone else tried to get this working and had success ?
>>>
>>> Regards
>>>
>>> Barry
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to go-cd+un...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] logback to a logstash server

2018-01-10 Thread Ketan Padegaonkar
The `libs` dir is relative to the working directory of the server/agent.
This should typically be `/var/lib/go-server/libs` or
`/var/lib/go-agent/libs`. I'll update the documentation to clarify this.


On Wed, Jan 10, 2018 at 6:29 PM 'Barry Greenwood' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi all
>
> I've now got logback able to log to local files with access requests and
> other logs, I am now hoping to ship these to an external logstash server
>
> reading
> https://docs.gocd.org/current/advanced_usage/logging.html#advanced-logging-features
> this should be possible, however its a little abiguous with "download all
> logstash-logback-encoder jars and dependencies into libs dir:"
>
> I presume its a java library folder as these are jar files but testing
> with these in several places that are in the java.library.path, it isn't
> working.
>
> Has anyone else tried to get this working and had success ?
>
> Regards
>
> Barry
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Fan-In from multiple Git repos.

2018-01-09 Thread Ketan Padegaonkar
Can you provide the full VSM for an instance of the pipeline
Deploy_Orchestrator_Pre_Prod?

On Wed, Jan 10, 2018 at 2:56 AM Prasanna  wrote:

>
> Hi,
>
> I was referring this doc for fan-in
>  configuration
> of GoCD to set up something like the image shown below.
>
>
>
> 
>
>
> I was expecting that "Deploy_Orchestrator_Pre_Prod" to be called once
> after all the 3 functional tests run successfully. However, each successful
> runs of the functional tests are triggering a deployment.
>
> So, if one of the functional tests fails, still the deployment happens
> twice.
>
>
> One thing that may be an issue here is that all 3 functional tests
> pipelines have their own git repository. Is it the case? How can I go about
> resolving this?
>
>
> I would like to deploy only after all 3 build is green. Let me know if you
> need further details.
>
>
> Thank you,
>
> Prasanna
>
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GoCD support for Subject Alternative Name (SAN) in certificate

2018-01-08 Thread Ketan Padegaonkar
SSL connections between the server and agent is managed by the
underlying httpcomponents library. The current implementation (4.5.4) seems
to prefer verifying the SAN over before verifying the CN. You can take a
look at the code here

.

All of this only kicks in, if you've turned on end-to-end SSL
,
otherwise everything falls back to an insecure "trust all" mode.



On Tue, Jan 9, 2018 at 2:41 AM Vinod Damle  wrote:

> Hello team,
>
> Does gocd support DNS name in Subject Alternative Name (if present) in
> certificates? If so,
>
> (1) Does Subject Alternate Name take precedence over Common Name in the
> Subject field of the cert?
> (2) What is the basis for selection of one of many Subject Alternative
> Names that maybe present? Does gocd select the entry that matches the
> hostname on which it is running on (by trying each, until a match is found)?
>
> Thanks,
> Vinod
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] trying to configure logback and access logs

2018-01-04 Thread Ketan Padegaonkar
I ran these sequence of commands
 and it
worked for me.



On Thu, Jan 4, 2018 at 10:32 PM 'Barry Greenwood' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi
>
>  I have tied these its a little better in the file is now being created,
>
> but i'm still not getting any access logs in the file
>
> i've tried both
> cat /var/lib/go-server/config/logback-include.xml
> 
> 
>class="ch.qos.logback.core.rolling.RollingFileAppender">
> /var/log/go-server/lbinclude.log
>  class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>   lbinclude.%d{-MM-dd}.log.gz
> 
> 7
> 1GB
> true
> 
>   %date{ISO8601} - %-4relative [%thread] %-5level %logger{35}
> - %msg%n
> 
>   
>
>   
>
>   
> 
>   
>
> 
>
> and
>
>
>   
> 
>   
>
> the first generates some data in the file the second leaves the file empty.
>
> logback access comes from the documentation on
> https://logback.qos.ch/access.html which is linked from
> https://github.com/logstash/logstash-logback-encoder
>
> Many thanks
>
> Barry
>
> On Tuesday, 2 January 2018 19:24:20 UTC, Aravind SV wrote:
>
>> Just FYI. Yes, it looks like doing this will work:
>>
>> mkdir config
>> chown go:go config
>> ln -s /etc/go/logback-include.xml /var/lib/go-server/config/
>>
> On Tue, Jan 2, 2018 at 11:17 AM, Aravind SV 
>> wrote:
>>
> Hello Barry,
>>>
>>
>>> On Tue, Jan 2, 2018 at 9:49 AM, 'Barry Greenwood' via go-cd <
>>> go...@googlegroups.com> wrote:
>>>
 Thanks for the help however i am still having issues.

 /etc/default/logback-include.xml as described but with a with a file
 appender in it does not create the file, that implies this isn't being read

>>>
>>> You're right. It's a bug. It'll be fixed in the next release (probably
>>> through this PR ). Meanwhile,
>>> temporarily, can you see if moving the file logback-include.xml into
>>> /var/lib/go-server/config/ works?
>>>
>>> Here's what I tried, to ensure that this works:
>>>
>>> $ ls -l /var/lib/go-server/config/
>>> total 4
>>> -rw-r--r-- 1 go go 759 Jan  2 18:58 logback-include.xml
>>> $ cat /var/lib/go-server/config/logback-include.xml
>>> 
>>> 
>>>   >> class="ch.qos.logback.core.rolling.RollingFileAppender">
>>> /var/log/go-server/test.log
>>> 
>>>   %date{ISO8601} %-5level [%thread] %logger{0}:%line -
>>> %msg%n
>>> 
>>>
>>> >> class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">
>>>
>>> /var/log/go-server/test.log.%d{-MM-dd}.%i.gz
>>>   10 MB
>>>   10
>>>   512 MB
>>> 
>>>   
>>>
>>>   
>>> 
>>>   
>>> 
>>>
>>> Once 18.1 is released, this will stop working and you can move it back
>>> to its correct place, /etc/go/logback-include.xml. Or, you can see if a
>>> symbolic link from /var/lib/go-server/config/logback-include.xml to
>>> /etc/go/logback-include.xml works.
>>>
>>> Cheers,
>>> Aravind
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] trying to configure logback and access logs

2017-12-20 Thread Ketan Padegaonkar
The logs do not mention any logback-access.xml anywhere. To get access logs
—

* create a file called `/etc/default/logback-include.xml`, with the
following contents



  



On Wed, Dec 20, 2017 at 4:51 PM 'Barry Greenwood' via go-cd <
go-cd@googlegroups.com> wrote:

> Hi Varsha
>
> I've tried in the  logback.xml
>
>  class="ch.qos.logback.core.rolling.RollingFileAppender">
> /var/log/go-server/lbaccess.log
>  class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>   lbaccess.%d{-MM-dd}.log.zip
> 
> 7
> 1GB
> true
> 
>   combined
> 
>   
>
>   
> 
>   
>
> and that generates the file but no logs appear.
>
> The docs imply i need to use a logback-access.xml but i cant get that to
> import.
>
> Thanks
>
> Barry
>
>
> On Wednesday, 20 December 2017 05:31:40 UTC, Varsha Varadarajan wrote:
>>
>> @Barry - Are you looking for request logs? This can be setup using
>> org.eclipse.jetty.server.RequestLog. Checkout the docs that Ketan pointed
>> to - https://docs.gocd.org/current/advanced_usage/logging.html
>>
>>
 --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] trying to configure logback and access logs

2017-12-19 Thread Ketan Padegaonkar
>
> On Tue, Dec 19, 2017 at 10:27 PM 'Barry Greenwood' via go-cd <
> go-cd@googlegroups.com> wrote:
>
>> I am on 17.12, I have got logback working for application logs however
>> the access logs state i need to import an logback-access.xml
>>
>
> I don't believe there is any GoCD document that says so.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] trying to configure logback and access logs

2017-12-19 Thread Ketan Padegaonkar
Assuming you're on version 17.11+ — checkout these docs
.

For versions older than 17.10, you'd likely have a log4j.properties file
and you'd be expected to uncomment this line

.



On Tue, Dec 19, 2017 at 9:26 PM 'Barry Greenwood' via go-cd <
go-cd@googlegroups.com> wrote:

>
>-
>
>Hi I am trying to configure logback and access logs but this doesnt
>appear to work. following the documentation i've come up with the below
>jetty.xml. However the logback-access.xml doesn't ever seem to be read.
>-
>
>
>
>
>
>
>
>class="ch.qos.logback.access.jetty.RequestLogImpl">
>/etc/go/logback-access.xml
>
>
>
>
>
>
>
> the below is the logback.xml (which appears to be needed but is missing
> from the documentation.
>
>-
>
>
>
>
>
>class="ch.qos.logback.classic.net.SocketAppender">
>SD-LOGSTASH.sysdev.zen.co.uk
>3319
>1
>true
>
>%h %l %u [%t] "%r" %s %b "%i{Referer}"
>"%i{User-Agent}"
>
>
>
>
>/var/log/go-server/lbfile.log
>class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>lbfile.%d{-MM-dd}.log.zip
>
>7
>3GB
>true
>
>true
>
>
>%-4relative [%thread] %-5level %logger{35} - %date{ISO8601} -
>%msg%n
>
>
>
>class="ch.qos.logback.core.rolling.RollingFileAppender">
>/var/log/go-server/lbaccess.log
>class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>lbaccess.%d{-MM-dd}.log.zip
>
>7
>1GB
>true
>
>combined
>
>
>
>
>
>-
>
>finally the below is the logback-access.xml which doenst seem to be
>imported (the base log file isnt created)
>
>
>
>class="ch.qos.logback.core.status.OnConsoleStatusListener" />
>
>class="ch.qos.logback.core.rolling.RollingFileAppender">
>/var/log/go-server/lb-access.log
>class="ch.qos.logback.core.rolling.TimeBasedRollingPolicy">
>lbaccess.%d{-MM-dd}.log.zip
>
>
>
>combined
>
>
>
>
>
>-
>
>Many Thanks for any help, Barry
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Issue with GOCD Environment Variables in Maven settings.xml

2017-11-30 Thread Ketan Padegaonkar
On Thu, Nov 30, 2017 at 8:46 PM ShaneG  wrote:

> I did try that and it wouldn't retrieve the value, t works fine for
> ${GO_REPO_USER} so i can't see why it would be any different for
> ${GO_REPO_PASSWORD}
>

Maybe a typo in environment variable name, or perhaps a special character
in the password needs xml escaping?

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Is it possible to add config-repos using the api?

2017-11-30 Thread Ketan Padegaonkar
The config repo API  is coming
up in the upcoming version of GoCD.


On Thu, Nov 30, 2017 at 8:10 PM  wrote:

> I am trying to write some tooling so we can add new repositories with a
> single command. Is it possible to add a config-repo to be used by the yaml
> parsing plugin?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Setting an env variable accessible to the gocd pipeline

2017-11-23 Thread Ketan Padegaonkar
Sorry, ignore my response. Sending an environment from an agent to a
pipeline is not possible, by design.

On Thu, Nov 23, 2017 at 4:29 PM Ketan Padegaonkar <
ketanpadegaon...@gmail.com> wrote:

> You'd add these environment variables to `/etc/default/go-agent` and
> restart your instance.
>
>
> On Thu, Nov 23, 2017 at 4:28 PM Mukesh Murali <mukesh.mur...@gmail.com>
> wrote:
>
>> Much appreciate the response, however GoCD environment variables are not
>> what i can use in my scenario. The use case is to make this work other way
>> around. To make a environment variable in an agent available to the
>> pipeline that runs on that agent. Any pointers will help. Thanks.
>>
>>
>> On Wednesday, 22 November 2017 16:10:08 UTC, Ken Mugrage wrote:
>>
>>>
>>> Hello, looks like
>>> https://docs.gocd.org/current/faq/environment_variables.html should be
>>> helpful.
>>>
>>> Regards
>>>
>> On Wed, Nov 22, 2017 at 5:00 AM, Mukesh Murali <mukesh...@gmail.com>
>>> wrote:
>>>
>> I have a need to be able to update a environment variable from the linux
>>>> gocd agents . This environment variable should be accessible from within
>>>> any pipeline that runs on the agent. Documentation i have read so far talks
>>>> about using the environment variables created in the gocd environment.
>>>> However this is not my requirement.
>>>>
>>>>
>>>> I have tried the following steps so far:
>>>>
>>>>
>>>>
>>>>1. Logged into the agent as go user and set an environment variable
>>>>( export VARA=XXX)  ;
>>>>2. Tried to echo this variable from a pipeline in gocd that prints
>>>>this variable, in vain.
>>>>3. Also tried specifying the variable in bash_profile, bashrc and
>>>>executed the source command in the same gocd task that echoes the 
>>>> variable
>>>>
>>>> For some reason, gocd pipeline doesnt seem to see this variable. Please
>>>> let me know if you have any pointers.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "go-cd" group.
>>>>
>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to go-cd+un...@googlegroups.com.
>>>
>>>
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>>> Ken Mugrage - thoughtworkskmug...@thoughtworks.com@kmugrage
>>>
>>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Setting an env variable accessible to the gocd pipeline

2017-11-23 Thread Ketan Padegaonkar
You'd add these environment variables to `/etc/default/go-agent` and
restart your instance.


On Thu, Nov 23, 2017 at 4:28 PM Mukesh Murali 
wrote:

> Much appreciate the response, however GoCD environment variables are not
> what i can use in my scenario. The use case is to make this work other way
> around. To make a environment variable in an agent available to the
> pipeline that runs on that agent. Any pointers will help. Thanks.
>
>
> On Wednesday, 22 November 2017 16:10:08 UTC, Ken Mugrage wrote:
>
>>
>> Hello, looks like
>> https://docs.gocd.org/current/faq/environment_variables.html should be
>> helpful.
>>
>> Regards
>>
> On Wed, Nov 22, 2017 at 5:00 AM, Mukesh Murali 
>> wrote:
>>
> I have a need to be able to update a environment variable from the linux
>>> gocd agents . This environment variable should be accessible from within
>>> any pipeline that runs on the agent. Documentation i have read so far talks
>>> about using the environment variables created in the gocd environment.
>>> However this is not my requirement.
>>>
>>>
>>> I have tried the following steps so far:
>>>
>>>
>>>
>>>1. Logged into the agent as go user and set an environment variable
>>>( export VARA=XXX)  ;
>>>2. Tried to echo this variable from a pipeline in gocd that prints
>>>this variable, in vain.
>>>3. Also tried specifying the variable in bash_profile, bashrc and
>>>executed the source command in the same gocd task that echoes the 
>>> variable
>>>
>>> For some reason, gocd pipeline doesnt seem to see this variable. Please
>>> let me know if you have any pointers.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to go-cd+un...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> Ken Mugrage - thoughtworkskmug...@thoughtworks.com@kmugrage
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Help me on this!!! Not able to connect Go-Agent from Go-Server.

2017-10-06 Thread Ketan Padegaonkar
What go server URL have you configured with the agent?

On Sat, Oct 7, 2017, 12:26 AM  wrote:

> I just started with gocd and I am trying to connect agent to server.  I am
> running into the same issue you ran into (log pasted below).
> I am using ec2 instances for both server and agent.  I tried start agent
> on the same host as the server first, which was failing with the same error.
> So, I tried starting agent on different ec2, still getting the same error.
>
> I also tried the suggestion of removing keystore and restarting the server.
> I didnot find guid.txt or agent.jks in /var/lib/go-agent folder or its
> subfolder.
>
> Since this thread is an year old, so I thought of checking if you were
> able to find any resolution.
>
> 2017-10-05 21:52:31,885 ERROR [main] ServerBinaryDownloader:80 - Couldn't
> update admin/agent-launcher.jar. Sleeping for 1m. Error:
> javax.net.ssl.SSLException: Unrecognized SSL message, plaintext connection?
> at
> sun.security.ssl.InputRecord.handleUnknownRecord(InputRecord.java:710)
> at sun.security.ssl.InputRecord.read(InputRecord.java:527)
> at
> sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:983)
> at
> sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1385)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1413)
> at
> sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1397)
> at
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:394)
> at
> org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:353)
> at
> org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:141)
> at
> org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:353)
> at
> org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:380)
> at
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236)
> at
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:184)
> at
> org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:88)
> at
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at
> com.thoughtworks.go.agent.launcher.ServerBinaryDownloader.fetchUpdateCheckHeaders(ServerBinaryDownloader.java:96)
> at
> com.thoughtworks.go.agent.launcher.ServerBinaryDownloader.downloadIfNecessary(ServerBinaryDownloader.java:72)
> at
> com.thoughtworks.go.agent.launcher.AgentLauncherImpl.launch(AgentLauncherImpl.java:79)
> at
> com.thoughtworks.go.agent.bootstrapper.AgentBootstrapper.go(AgentBootstrapper.java:84)
> at
> com.thoughtworks.go.agent.bootstrapper.AgentBootstrapper.main(AgentBootstrapper.java:65)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at com.thoughtworks.gocd.Boot.run(Boot.java:58)
> at com.thoughtworks.gocd.Boot.main(Boot.java:42)
>
> Thank You,
> Ranjith
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Working package plugin? Yum deprecated...

2017-09-25 Thread Ketan Padegaonkar
I've logged an issue to improve this support
https://github.com/gocd/gocd-yum-repository-poller-plugin/issues/3

On Mon, Sep 18, 2017 at 10:21 PM Magnus Lyckå 
wrote:

> I'm taking a look at the Yum Repository Poller. It's not that I need Yum,
> I just wanted to understand package plugins better, and I thought the Yum
> plugin would be the one which worked out of the box... :-)
>
> I get this in the plugin-yum.log:
>
> 2017-09-18 18:11:09,444  INFO [qtp321142942-22] RepoQueryCommand:49 -
> Error while querying repository with path '
> http://fedora.uib.no/fedora/linux/releases/22/Everything/x86
> _64/os/' and package spec '2ping'. Error Message:
> Yum-utils package has been deprecated, use dnf instead.
> See 'man yum2dnf' for more information.
>
> 2017-09-18 18:11:09,446  WARN [qtp321142942-22] PackageRepositoryPoller:59
> - Could not find any package that matched '2ping'.
>
>
> I tried an older CentOS repo too, in case that wasn't as uptodate, but to
> no avail. Yum seems passé.
>
> Any idea about a simple workaround or some other package plugin which is
> easy to get up and running.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GoCD Agent Upgrades

2017-09-18 Thread Ketan Padegaonkar
If you are on a version of GoCD >= 16.7, the agent config
`/etc/default/go-agent` will not have a JVM path in it. If you have a JVM
path in it, you likely upgraded from an older agent, please remove it
before upgrading and the agent and server should pick up the JVM on the
$PATH.

If you have several JVMs and want to force the agent to use a specific JVM,
use GO_JAVA_HOME to point to the JVM you'd like the agent to use.


On Mon, Sep 18, 2017, 6:37 PM  wrote:

> We are looking to upgrade some of our RHEL 7.2 boxes to RHEL 7.3. these
> servers are GoCD Agents. I wanted to know what the best practice is for
> this process with regards to GoCD agents (we have the GoCD server on
> Windows 2012 R2). We typically upgrade all packages via yum during this
> process, this would include Java. If we do this the GoCD agent will fail to
> start as it has a specified java path in the configuration. Could you
> confirm what the best practice is with regards to handling package updates
> on Linux and GoCD? I assume it's 1 of 2 ways:
>
>
> 1. Exclude Java has part of our update and let GoCD upgrade the Java as
> part of upgrading the GoCD server.
> 2. Upgrade Java using yum it and re-point the GoCD agent at the new
> version.
>
>
> How have the community handled kernel upgrades with a GoCD Agent?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] 8443 redirect after changing GO_SERVER_SSL_PORT to 8080

2017-09-14 Thread Ketan Padegaonkar
On Thu, Sep 14, 2017 at 7:50 PM David Newhook  wrote:

> Both are set to 8080
>
> Input Arguments "-Dcruise.server.ssl.port\u003d8080"
> System Properties "cruise.server.ssl.port": "8080",
>
> There is no problem with the initial redirect.
>
>
> curl --cacert ca.crt -v https://gocd-server:8080
> redirects to
> Location: /go/home
>
> but then
> curl --cacert ca.crt -v https://gocd-server:8080/go/home
> redirects to
> Location: https://gocd-server:8443/go/auth/login
>
> The 2nd redirect is fully qualified.  Is this an issue with the
> authentication plugin integration?  No issue with ports 8081, 9000 or 8154
> (of course).
>

I can't say for sure. There's usually multiple reasons this can happen:

* bad reverse proxy
 (not
forwarding the right headers)
* incorrect `siteUrl` or `secureSiteUrl` setting in your config.xml
* bad redirect urls in one of your auth plugins

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] 8443 redirect after changing GO_SERVER_SSL_PORT to 8080

2017-09-14 Thread Ketan Padegaonkar
If you make a request for http://your-server:8153/go/api/support and look
for "*System Properties*"  and "*Input Arguments*", do you see the property
*cruise.server.ssl.port* set to port 8080, if not there's likely a problem
reading /etc/default/go-server.

On Thu, Sep 14, 2017 at 7:14 PM David Newhook  wrote:

> Hi there,
>
> I don't seem to be able to change the SSL listen port to 8080 for GOCD
> server deployed with RPMs on RHEL 7.3 (GOCD 17.10 tested).
>
> I have configured GO_SERVER_SSL_PORT to be 8080 in /etc/default/go-server
> as follows:
>
> GO_SERVER_PORT=8153
> GO_SERVER_SSL_PORT=8080
> SERVER_WORK_DIR=/var/lib/go-server
> DAEMON=Y
>
> I am using my own SSL cert as documented in
> https://docs.gocd.org/17.10.0/installation/ssl_tls/custom_server_certificate.html
> but have observed the same behaviour in an experimental build of 17.11
> 
> where I used the default self-signed certificate.  Using Firefox or curl -
> I'm always redirected from the 8080 port set to 8443 when not
> authenticated.  The following curl statement is run on the gocd server.
> 'gocd-server' in /etc/hosts points to the IP address of the GOCD server
> (192.168.178.15).  No proxies configured.
>
> gocd-server:root:/root # curl --cacert ca.crt -v https://gocd-server:8080/
> go/home
> * About to connect() to gocd-server port 8080 (#0)
> *   Trying 192.168.178.15...
> * Connected to gocd-server (192.168.178.15) port 8080 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> *   CAfile: ca.crt
>   CApath: none
> * NSS: client certificate not found (nickname not specified)
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
> * Server certificate:
> *   subject: CN=gocd-server
> *   start date: Sep 06 12:22:28 2017 GMT
> *   expire date: Sep 06 12:22:28 2022 GMT
> *   common name: gocd-server
> *   issuer: CN=My CA
> > GET /go/home HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: gocd-server:8080
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Thu, 14 Sep 2017 13:12:14 GMT
> < Set-Cookie: JSESSIONID=orh3ia1v4s1dpnefhc2v2evp;Path=/go;Expires=Thu,
> 28-Sep-2017 13:12:14 GMT;Secure;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < Location: https://gocd-server:8443/go/auth/login
> < Content-Length: 0
> <
> * Connection #0 to host gocd-server left intact
>
> Strangely no problem with other ports (9000 and 8081 tested).
> gocd-server:root:/root # curl --cacert ca.crt -v https://gocd-server:8081/
> go/home
> * About to connect() to gocd-server port 8081 (#0)
> *   Trying 192.168.178.15...
> * Connected to gocd-server (192.168.178.15) port 8081 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> *   CAfile: ca.crt
>   CApath: none
> * NSS: client certificate not found (nickname not specified)
> * SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
> * Server certificate:
> *   subject: CN=gocd-server
> *   start date: Sep 06 12:22:28 2017 GMT
> *   expire date: Sep 06 12:22:28 2022 GMT
> *   common name: gocd-server
> *   issuer: CN=Puppet CA: config.shared.sp.vodafone.com
> > GET /go/home HTTP/1.1
> > User-Agent: curl/7.29.0
> > Host: gocd-server:8081
> > Accept: */*
> >
> < HTTP/1.1 302 Found
> < Date: Thu, 14 Sep 2017 13:34:05 GMT
> < Set-Cookie: JSESSIONID=1dt9ank0ghnd7aluwlheptn3f;Path=/go;Expires=Thu,
> 28-Sep-2017 13:34:05 GMT;Secure;HttpOnly
> < Expires: Thu, 01 Jan 1970 00:00:00 GMT
> < Location: https://gocd-server:8081/go/auth/login
> < Content-Length: 0
> <
> * Connection #0 to host gocd-server left intact
>
> SELinux is running in permissive mode - not seeing anything in the audit
> log.  Is this just an issue with my environment?
>
> Kind Regards,
>
> David
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GoCD 17.9 server crash on startup

2017-09-08 Thread Ketan Padegaonkar
This was reported here https://github.com/gocd/gocd/issues/3834. This
problem affects a small proportion of users, and we recommend that you
rollback to 17.8. We'll be putting out release 17.10 early next week with a
fix for this issue.

On Fri, Sep 8, 2017 at 9:20 PM Magnus Lyckå  wrote:

> Upgrading to 17.9 from 17.4, the go-server crashes on startup with
> messages like below.
>
> Any idea why this happens?
>
> When I upgraded to 17.8 instead, the go-server started up nicely.
>
> Upgrading from 17.8 -> 17.9 crashes like before, so it doesn't seem to be
>  migration from 17.4 which is the problem.
>
> The non-standard thing we have in the config is
> https://github.com/1and1/go-maven-poller
>
> 2017-09-08 11:34:07,385  INFO [main] Jetty9Server:178 - Configuring Jetty
> using /etc/go/jetty.xml
> 2017-09-08 11:34:07,415  INFO [main] GoServer:98 - Including addons:
> 2017-09-08 11:34:09,590 ERROR [main] ContextLoader:307 - Context
> initialization failed
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'userSqlMapDao' defined in file
> [/var/lib/go-server/work/jetty-
> 0.0.0.0-8153-cruise.war-_go-any-/webapp/WEB-INF/classes/com/thoughtworks/go/server/dao/UserSqlMapDao.class]:
> Unsatisfied dependency expressed through construct
> or argument with index 0 of type [org.hibernate.SessionFactory]: : Error
> creating bean with name 'sqlMapClient' defined in ServletContext resource
> [/WEB-INF/ap
> plicationContext-dataLocalAccess.xml]: Unsatisfied dependency expressed
> through constructor argument with index 0 of type
> [com.thoughtworks.go.server.database.
> DatabaseStrategy]: : Error creating bean with name
> 'goAuthenticationProviderFactory' defined in ServletContext resource
> [/WEB-INF/applicationContext-acegi-secu
> rity.xml]: Unsatisfied dependency expressed through constructor argument
> with index 0 of type [com.thoughtworks.go.server.service.UserService]: :
> Error creatin
> g bean with name 'userService' defined in file
> [/var/lib/go-server/work/jetty-0.0.0.0-8153-cruise.war-_go-any-/webapp/WEB-INF/classes/com/thoughtworks/go/serve
> r/service/UserService.class]: Unsatisfied dependency expressed through
> constructor argument with index 0 of type
> [com.thoughtworks.go.server.dao.UserDao]: : Er
> ror creating bean with name 'userSqlMapDao': Requested bean is currently
> in creation: Is there an unresolvable circular reference?; nested exception
> is org.spr
> ingframework.beans.factory.BeanCurrentlyInCreationException: Error
> creating bean with name 'userSqlMapDao': Requested bean is currently in
> creation: Is there a
> n unresolvable circular reference?; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'userSe
> rvice' defined in file
> [/var/lib/go-server/work/jetty-0.0.0.0-8153-cruise.war-_go-any-/webapp/WEB-INF/classes/com/thoughtworks/go/server/service/UserService.cl
> ass]: Unsatisfied dependency expressed through constructor argument with
> index 0 of type [com.thoughtworks.go.server.dao.UserDao]: : Error creating
> bean with n
> ame 'userSqlMapDao': Requested bean is currently in creation: Is there an
> unresolvable circular reference?; nested exception is
> org.springframework.beans.facto
> ry.BeanCurrentlyInCreationException: Error creating bean with name
> 'userSqlMapDao': Requested bean is currently in creation: Is there an
> unresolvable circular
> reference?; nested exception is
> org.springframework.beans.factory.UnsatisfiedDependencyException: Error
> creating bean with name 'goAuthenticationProviderFactor
> y' defined in ServletContext resource
> [/WEB-INF/applicationContext-acegi-security.xml]: Unsatisfied dependency
> expressed through constructor argument with inde
> x 0 of type [com.thoughtworks.go.server.service.UserService]: : Error
> creating bean with name 'userService' defined in file
> [/var/lib/go-server/work/jetty-0.0.
> 0.0-8153-cruise.war-_go-any-/webapp/WEB-INF/classes/com/thoughtworks/go/server/service/UserService.class]:
> Unsatisfied dependency expressed through constructor
> argument with index 0 of type [com.thoughtworks.go.server.dao.UserDao]: :
> Error creating bean with name 'userSqlMapDao': Requested bean is currently
> in creati
> on: Is there an unresolvable circular reference?; nested exception is
> org.springframework.beans.factory.BeanCurrentlyInCreationException: Error
> creating bean w
> ith name 'userSqlMapDao': Requested bean is currently in creation: Is
> there an unresolvable circular reference?; nested exception is
> org.springframework.beans.
> factory.UnsatisfiedDependencyException: Error creating bean with name
> 'userService' defined in file
> [/var/lib/go-server/work/jetty-0.0.0.0-8153-cruise.war-_go-
> any-/webapp/WEB-INF/classes/com/thoughtworks/go/server/service/UserService.class]:
> Unsatisfied dependency expressed through constructor argument with index 0 o
> f type 

Re: [go-cd] Re: Garbage Collecition in GO

2017-08-31 Thread Ketan Padegaonkar
On Thu, Aug 31, 2017 at 1:31 PM Chris Tamlyn  wrote:

> Since I raised this issue we've actually switched to a Linux server so the
> mechanism is slightly different.  When I view my support page I see:
>
>   "-Dgo.config.repo.gc.periodic\u003dY",
>   "-Dgo.config.repo.gc.cron\u003d0 0 7 1/1 \\* \\?",
>
> Those are CLI args string escaped. You probably need to look at the
section under "System Properties" to see the unescaped values and see if
they are valid expressions understood by quartz (
http://www.quartz-scheduler.org/api/2.2.1/org/quartz/CronExpression.html)

I'm seeing this on the build server at build.gocd.org:

$ curl -s -uUSER:PASS https://build.gocd.org/go/api/support | jq
'.["Runtime Information"]["System Properties"]["go.config.repo.gc.cron"]'
*"0 0 7/12 1/1 * ?"*

The file /etc/default/go-server contains:

export GO_SERVER_SYSTEM_PROPERTIES="-Dgo.config.repo.gc.periodic=true
-Dgo.config.repo.gc.cron='0 0 7/12 1/1 * ?' -Dgo.config.repo.gc.expire=10"

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Garbage Collecition in GO

2017-08-29 Thread Ketan Padegaonkar
Would you mind logging an issue on github with the contents of your
wrapper-server.conf file so someone can take a look?

On Tue, Aug 29, 2017 at 9:57 PM <keithlim2...@gmail.com> wrote:

> Thanks Ketan,
>
> I used the instruction and did these steps, must have missed something
> subtle.
>
> 1) in \config\wrapper-server.conf
> un-commented the line
> #include config/wrapper-properties.conf
> to
> include config/wrapper-properties.conf
>
> 2) created a new file wrapper-properties.conf
> with the following content:
>
> tried
> 1)
> wrapper.java.additional.16=-Dgo.config.repo.gc.periodic=Y
> wrapper.java.additional.17=-Dgo.config.repo.gc.cron='0 0 3 * * *'
>
> 1b) with double quotes
> wrapper.java.additional.16="-Dgo.config.repo.gc.periodic=Y"
> wrapper.java.additional.17="-Dgo.config.repo.gc.cron='0 0 3 * * *'"
>
> 1c) (with escape key?)
> wrapper.java.additional.16="-Dgo.config.repo.gc.periodic=Y"
> wrapper.java.additional.17="-Dgo.config.repo.gc.cron='0 0 3 \* \* \*'"
>
> 2)
> go.config.repo.gc.periodic=Y
> go.config.repo.gc.cron='0 0 3 * * *'
>
> None of the above works for me.  Must be something subtle.
>
> Any help appreciated,
>
> Thanks,
> Keith
>
> On Monday, August 28, 2017 at 6:43:16 PM UTC-7, Ketan Padegaonkar wrote:
>
>> See this page (
>> https://docs.gocd.org/current/installation/install/server/windows.html#overriding-default-startup-arguments-and-environment)
>> for details on setting up system properties.
>>
>> On Tue, Aug 29, 2017, 5:58 AM <keithl...@gmail.com> wrote:
>>
> I have the same issue and am not able to get the setting to work.  I
>>> use https://:8154/go/api/support  to verify if the
>>> properties but did not see the properties.
>>> Anyone has the answer please share.   I am on MS Windows as well.
>>>
>>>
>>> Thanks,
>>> Keith
>>>
>>>
>>> On Tuesday, May 24, 2016 at 1:27:20 AM UTC-7, Chris Tamlyn wrote:
>>>>
>>>> Thanks Varsha, sounds like we did everything right then.  I don't see
>>>> that any garbage collection occurred at the scheduled time and we still
>>>> have the error reporting in the GUI.  So not sure how to explain that.
>>>>
>>>> On Tuesday, 24 May 2016 04:42:04 UTC+1, Varsha Varadarajan wrote:
>>>>>
>>>>> Hi Chris
>>>>>
>>>>> The above properties that you mentioned are system properties that
>>>>> alter how the garbage collection behaviour in the configuration 
>>>>> repository.
>>>>> They must be added to the wrapper-properties.conf file.
>>>>>
>>>>> Here is the documentation for appending these properties:
>>>>> https://docs.go.cd/current/installation/install/server/windows.html#overriding-default-startup-arguments-and-environment
>>>>>
>>>>> Make sure you restart the Go server after changing the same.
>>>>>
>>>>> Thanks.
>>>>> Varsha
>>>>>
>>>>> On Thursday, 19 May 2016 13:26:55 UTC+5:30, Chris Tamlyn wrote:
>>>>>>
>>>>>> We started to get an error in GO around Garabge collection which
>>>>>> directs us to this link:
>>>>>>
>>>>>> https://docs.go.cd/current/advanced_usage/config_repo.html
>>>>>>
>>>>>> Has anyone else implemented this in Go before?  I'm not sure that I'm
>>>>>> reading the documentation correctly on how to set it up for GO.  I've 
>>>>>> read
>>>>>> it as you need to add those properties to your 'wrapper-properties' file
>>>>>> (we run on Windows).  So I've added the following 3 settings:
>>>>>>
>>>>>> go.config.repo.gc.periodic=Y
>>>>>> go.config.repo.gc.aggressive=Y
>>>>>> go.config.repo.gc.cron=0 0 7 ? * SUN
>>>>>>
>>>>>> But I wasn't sure if this was the correct place of if they should be
>>>>>> Windows Environment variables.  Has anyone got any experience setting 
>>>>>> this
>>>>>> up and could help guide us?
>>>>>>
>>>>>> Many Thanks
>>>>>>
>>>>>> Chris
>>>>>>
>>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to go-cd+un...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Does GoCD support parallel builds?

2017-08-29 Thread Ketan Padegaonkar
You can specify your jobs to run on multiple agents
.
The build will run with 2 additional environment variables GO_JOB_RUN_INDEX
and GO_JOB_RUN_COUNT to indicate the number of agents, and the index of the
current agent. You may use these variables to partition your tests as you
see fit.

For reference, the GoCD team uses this code
 to
partition tests across several agents.

On Tue, Aug 29, 2017 at 3:14 PM Michael Baldry  wrote:

> And by this I mean, I mean something similar to CircleCI, where you can
> say a project has 4 agents and then it runs each one with an ENV variable
> set to say what agent number it is and you can split your tests by the
> number, to run a single test suite in a quarter of the time (in theory).
>
> If not, is there another way to achieve this goal?
>
> Many thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Garbage Collecition in GO

2017-08-28 Thread Ketan Padegaonkar
See this page (
https://docs.gocd.org/current/installation/install/server/windows.html#overriding-default-startup-arguments-and-environment)
for details on setting up system properties.

On Tue, Aug 29, 2017, 5:58 AM  wrote:

> I have the same issue and am not able to get the setting to work.  I
> use https://:8154/go/api/support  to verify if the
> properties but did not see the properties.
> Anyone has the answer please share.   I am on MS Windows as well.
>
>
> Thanks,
> Keith
>
>
> On Tuesday, May 24, 2016 at 1:27:20 AM UTC-7, Chris Tamlyn wrote:
>>
>> Thanks Varsha, sounds like we did everything right then.  I don't see
>> that any garbage collection occurred at the scheduled time and we still
>> have the error reporting in the GUI.  So not sure how to explain that.
>>
>> On Tuesday, 24 May 2016 04:42:04 UTC+1, Varsha Varadarajan wrote:
>>>
>>> Hi Chris
>>>
>>> The above properties that you mentioned are system properties that alter
>>> how the garbage collection behaviour in the configuration repository. They
>>> must be added to the wrapper-properties.conf file.
>>>
>>> Here is the documentation for appending these properties:
>>> https://docs.go.cd/current/installation/install/server/windows.html#overriding-default-startup-arguments-and-environment
>>>
>>> Make sure you restart the Go server after changing the same.
>>>
>>> Thanks.
>>> Varsha
>>>
>>> On Thursday, 19 May 2016 13:26:55 UTC+5:30, Chris Tamlyn wrote:

 We started to get an error in GO around Garabge collection which
 directs us to this link:

 https://docs.go.cd/current/advanced_usage/config_repo.html

 Has anyone else implemented this in Go before?  I'm not sure that I'm
 reading the documentation correctly on how to set it up for GO.  I've read
 it as you need to add those properties to your 'wrapper-properties' file
 (we run on Windows).  So I've added the following 3 settings:

 go.config.repo.gc.periodic=Y
 go.config.repo.gc.aggressive=Y
 go.config.repo.gc.cron=0 0 7 ? * SUN

 But I wasn't sure if this was the correct place of if they should be
 Windows Environment variables.  Has anyone got any experience setting this
 up and could help guide us?

 Many Thanks

 Chris

>>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Go Session Timing out after 30 minutes after upgrading to 17.8

2017-08-23 Thread Ketan Padegaonkar
When you file an issue, make sure to provide a copy of the snippet from
your config file that sets up LDAP (with sensitive information redacted),
and any other relevant details (LDAP implementation, version etc)

On Thu, Aug 24, 2017 at 7:15 AM Ketan Padegaonkar <
ketanpadegaon...@gmail.com> wrote:

> Would you mind logging an issue on github? We've moved to a new LDAP
> plugin and that could be the root cause. Someone can let you know the steps
> to rollback to the old LDAP implementation on the current version of LDAP
> on the github issue.
>
>
> On Thu, Aug 24, 2017 at 12:40 AM <james.ha...@nexlendcapital.com> wrote:
>
>> I forgot to mention, this is using LDAP authentication.
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "go-cd" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to go-cd+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Release Announcement - 17.8.0

2017-08-17 Thread Ketan Padegaonkar
You will need to define a   with a  material.
https://docs.gocd.org/current/configuration/configuration_reference.html#tfs

On Fri, Aug 18, 2017, 2:14 AM  wrote:

> I am really excited about the support for pipeline as code in this
> release.   My company uses TFS as code repository.   Does the config repo
> plugin support storing the pipeline code in TFS?  If supported, any sample
> would be appreciated.
>
> Thanks,
> Keith
>
> On Wednesday, August 2, 2017 at 3:27:29 AM UTC-7, go-cd wrote:
>>
>> Hey All,
>>
>> A new version (17.8.0) of GoCD is out.
>> Know more about the features and bug fixes in this release here
>>  or head to our downloads
>>  page to try it.
>>
>> Cheers,
>> GoCD Team
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Go-cd with VSTS

2017-08-14 Thread Ketan Padegaonkar
With visualstudio.com, I believe you're expected to use your personal
access token, and not your password.

On Mon, Aug 14, 2017 at 7:39 PM Firas Rashid  wrote:

> What is the values you specified in the Material section when you tried to
> connect to VSTS?
>
> For me, I provided the following:
>
>1. *Material Type:* "Team Foundation Server"
>2. *URL:* https://ourvso.visualstudio.com
>3. *Domain:* I left this one empty
>4. *Username:* firas.r (extracted from fira...@ourdomain.com)
>5. *Password:* my VSTS password
>6. *Project Path:* the correct project path (am sure about it)
>
> But I keep getting the error message: *"Access denied connecting to TFS
> server https://ourvso.visualstudio.com/ 
> (authenticating as fira...@ourdomain.com )"*
>
> One I tried the specific values:
> *Domain:* ourdomain
> *Username:* fira...@ourdomain.com
>
> I get the error message: *"This server requires federated authentication
> but no mechanism was available to handle it."*
>
> Can you help with that?
>
> Firas
>
> On Sunday, August 21, 2016 at 12:54:58 AM UTC+3, Scott Ma wrote:
>>
>> seems to fix my issue by using https://> domain>:@.visualstudio.com/.../_git/
>>
>>
>>
>> On Saturday, August 20, 2016 at 4:37:07 PM UTC-5, Scott Ma wrote:
>>>
>>> Have anyone successfully used GO-CD with VSTS-Git? Locally I use window
>>> credential manager but there is no such option in the GO-CD setting. This
>>> issue is a show-stopper for me if I cannot even get the source code.
>>>
>>> Scott.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] GoCD deployed as Docker stack

2017-08-02 Thread Ketan Padegaonkar
On Wed, Aug 2, 2017 at 4:16 PM Steve Atkinson 
wrote:

> Is there any mechanism to tell the server up front before it starts what
> key to use?
>

You'd have to use volume mounts and pre-populate that directory with a
cruise-config.xml with a key of your choice.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: Access Denied Error for Agent

2017-07-27 Thread Ketan Padegaonkar
Reverse proxies are not supported for the agent server communication.
Please connect your agents to port 8154 directly.

On Thu, Jul 27, 2017, 4:22 PM Alexander Partsch 
wrote:

> EDIT: Found this message in the go-agent.log
>
> No mapping found for HTTP request with URI
>> [/go/remoting/remoteBuildRepository]] in DispatcherServlet with name
>> 'spring-
>> cruise-remoting'
>>
>
> On Thursday, July 27, 2017 at 12:02:08 PM UTC+2, Alexander Partsch wrote:
>>
>> Hi,
>>
>> I have my GoCD Server and Agent running on the same server. GoCD Server
>> is behind an nginx proxy with the name build.example.com. I set the
>> GO_SERVER_URL in the /etc/default/go-agent file to
>> https://build.example.com/go ... the service starts without an error, I
>> could see the agent in the agents list on my GoCD Server Web App, I enabled
>> it and then it says Status=LostContact. Looking into the go-agent.log I see
>> the following error:
>>
>> 2017-07-27 11:56:18,063 [pingThread] ERROR
>>> thoughtworks.go.agent.AgentHTTPClientController:84 - Error occurred when
>>> agent tried to ping server:
>>> org.springframework.remoting.RemoteAccessException: Could not access
>>> HTTP invoker remote service at [
>>> https://build.example.com/go/remoting/remoteBuildRepository]; nested
>>> exception is org
>>> .apache.http.NoHttpResponseException: Did not receive successful HTTP
>>> response: status code = 403, status message = [Access Denied]
>>>at
>>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.convertHttpInvokerAccessException(HttpInvokerClientInterceptor.java:212)
>>>
>>>at
>>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:145)
>>>
>>>at
>>> org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
>>>
>>>at
>>> org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
>>>
>>>at com.sun.proxy.$Proxy6.ping(Unknown Source)
>>>at
>>> com.thoughtworks.go.agent.AgentHTTPClientController.ping(AgentHTTPClientController.java:80)
>>>
>>>at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
>>>at
>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>>
>>>at java.lang.reflect.Method.invoke(Method.java:498)
>>>at
>>> org.springframework.util.MethodInvoker.invoke(MethodInvoker.java:273)
>>>at
>>> org.springframework.scheduling.support.MethodInvokingRunnable.run(MethodInvokingRunnable.java:65)
>>>
>>>at
>>> org.springframework.scheduling.timer.DelegatingTimerTask.run(DelegatingTimerTask.java:70)
>>>
>>>at java.util.TimerThread.mainLoop(Timer.java:555)
>>>at java.util.TimerThread.run(Timer.java:505)
>>> Caused by: org.apache.http.NoHttpResponseException: Did not receive
>>> successful HTTP response: status code = 403, status message = [Access
>>> Denied]
>>>at
>>> com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.validateResponse(GoHttpClientHttpInvokerRequestExecutor.java:86)
>>>
>>>at
>>> com.thoughtworks.go.agent.GoHttpClientHttpInvokerRequestExecutor.doExecuteRequest(GoHttpClientHttpInvokerRequestExecutor.java:64)
>>>
>>>at
>>> org.springframework.remoting.httpinvoker.AbstractHttpInvokerRequestExecutor.executeRequest(AbstractHttpInvokerRequestExecutor.java:136)
>>>
>>>at
>>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:192)
>>>
>>>at
>>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.executeRequest(HttpInvokerClientInterceptor.java:174)
>>>
>>>at
>>> org.springframework.remoting.httpinvoker.HttpInvokerClientInterceptor.invoke(HttpInvokerClientInterceptor.java:142)
>>>
>>>... 12 more
>>>
>>>
>> I enabled basic auth with password file on the server, but that shouldn't
>> matter right? Gitlab OAuth Plugin is also enabled.
>>
>> Appreciate any help on this!
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Can you log code output when the plugin runs on an Agent?

2017-07-24 Thread Ketan Padegaonkar
The plugin logs stuff where it runs. So a plugin that logs on the agent
will write the logs on the agent log dir

On Fri, Jul 21, 2017, 9:03 PM <ppogo...@thoughtworks.com> wrote:

> Sorry, I meant a log file on the server.
> However, that reminds me, even using the JobConsoleLogger.printLine()
> method returns nothing
>
>
> On Friday, July 21, 2017 at 3:44:35 PM UTC+1, Ketan Padegaonkar wrote:
>
>> When you say "code output" do you mean showing something that shows up on
>> the "console" tab of a job?
>>
>> On Fri, Jul 21, 2017 at 8:10 PM <ppog...@thoughtworks.com> wrote:
>>
> Hi,
>>> as part of debugging my task Plugin I've created LOG.info statements at
>>> critical points in my executor class.
>>>
>>> Now, while all logging set up in the plugin class that runs on the
>>> Server work, I cannot get the logging to work thats runs on an Agent.
>>>
>>> I'm testing on OS X using GoCD 17.7.0.
>>>
>>> I've based my plugin from the curl plugin at
>>> https://github.com/gocd/sample-plugins/tree/master/curl-plugin
>>>
>>> I'd be very surprised if you cannot use the 
>>> com.thoughtworks.go.plugin.api.logging.Logger
>>> to log on the Agent, so can someone help me in finding out what I'm doing
>>> wrong, please?
>>>
>>> Cheers,
>>> PP
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "go-cd" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to go-cd+un...@googlegroups.com.
>>
>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] How do you retrieve a Pipeline's environment variables from a custom Task Plugin

2017-07-24 Thread Ketan Padegaonkar
The execute message should have all the variables available for your task
to consume as you see fit.
https://developer.gocd.org/current/writing_go_plugins/task/version_1_0/execute.html
if you are not receiving those, perhaps logging a bug may be your best
option

On Mon, Jul 24, 2017, 7:52 PM  wrote:

> Hi,
> I'd like to be able to extend the capability of Go's Authorisation by
> invoking some XACML requests.
> To make this as automated as possible, I don't want the use to enter
> values into the task that has been defined as an environment variable for
> the Pipeline.
>
> How do I use the GoApplicationAccessor to request the list of pipeline
> environment variables, both defined by the user and the default ones
> like GO_ENVIRONMENT_NAME?
>
> PP
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Can you log code output when the plugin runs on an Agent?

2017-07-21 Thread Ketan Padegaonkar
When you say "code output" do you mean showing something that shows up on
the "console" tab of a job?

On Fri, Jul 21, 2017 at 8:10 PM  wrote:

> Hi,
> as part of debugging my task Plugin I've created LOG.info statements at
> critical points in my executor class.
>
> Now, while all logging set up in the plugin class that runs on the Server
> work, I cannot get the logging to work thats runs on an Agent.
>
> I'm testing on OS X using GoCD 17.7.0.
>
> I've based my plugin from the curl plugin at
> https://github.com/gocd/sample-plugins/tree/master/curl-plugin
>
> I'd be very surprised if you cannot use the 
> com.thoughtworks.go.plugin.api.logging.Logger
> to log on the Agent, so can someone help me in finding out what I'm doing
> wrong, please?
>
> Cheers,
> PP
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Agent connecting to Server over internet, using custom TLS certificate

2017-07-19 Thread Ketan Padegaonkar
The end-to-end transport security was implemented in release 16.7
<16.7https://www.gocd.org/releases/#16.7.0> to get rid of that initial
handshake over HTTP. It's recommended that you turn it on, especially so
when going over an untrusted network.

On Wed, Jul 19, 2017 at 10:08 PM Stefan Smith 
wrote:

> Hi,
>
> I'm looking to have a GoCD agent connect over the internet to a GoCD
> server. The agent and server are in different networks. Is this safe,
> assuming a custom TLS certificate is used as per
> https://docs.gocd.org/current/installation/ssl_tls/custom_server_certificate.html
> and
> https://docs.gocd.org/current/installation/ssl_tls/end_to_end_transport_security.html?
> The agent will also have the server's auto-register key.
>
> I know that in the past, the agent connected via HTTP as part of initial
> registration, before using an HTTPS connection for all subsequent
> communcation. Is this still the case? Does this expose any possible
> security holes?
>
> Thanks,
>
> Stef
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Bug: New authorization plugins never actually let me log in

2017-07-05 Thread Ketan Padegaonkar
If all you want to do is quickly get a production like server up and
running with least amount of fuss, I've provided an example here along with
the config and password file.

https://github.com/gocd/gocd/issues/3618#issuecomment-311545904

On Wed, Jul 5, 2017 at 4:11 PM Ketan Padegaonkar <ketanpadegaon...@gmail.com>
wrote:

> On Tue, Jul 4, 2017 at 7:17 PM Chris Northwood <cnorthw...@gmail.com>
> wrote:
>
>> Hi Aravind,
>>
>> I'm still having issues using the Vagrant box, and getting it set up with
>> 17.7. When I try to create a pipeline (before adding the authorization
>> plugin), I get a CSRF error.
>>
>
> That's usually an indication that you have another server running on the
> same host but different ports causing all sorts of weirdness. Could you
> confirm that you only have one server running on "localhost", or whatever
> you're using for development?
>
>
>> If I add the authorization plugin, I can never get past the login screen
>> (similar to https://groups.google.com/forum/m/#!topic/go-cd/Qe_tEdgQhTg).
>> I'm curious if there's any obvious environment issues between us, as the
>> Vagrant box should give us the same environment :/ Alternatively, could the
>> gocd demo Vagrant box get updated to the latest version of GoCD, so I can
>> use that as a base instead of rolling my own?
>>
>
> What demo vagrant box are you referring to? We use the box built out of
> the Vagrantfile <https://github.com/gocd/gocd/blob/master/Vagrantfile>
> checked into the gocd repository. Alternatively:
>
> docker run -it --rm -v $(pwd):/gocd -v
> $HOME/.gradle:/go/.gradle gocdcontrib/gocd-dev-build:v1.0.23 /bin/bash
>
> The docker example is a lot easier to work with, since it involves not
> having to download and install stuff on a network. If you run that docker
> command in the directory containing your gocd sourcecode, it's mounted in
> `/gocd` inside the docker container.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Bug: New authorization plugins never actually let me log in

2017-07-05 Thread Ketan Padegaonkar
On Tue, Jul 4, 2017 at 7:17 PM Chris Northwood  wrote:

> Hi Aravind,
>
> I'm still having issues using the Vagrant box, and getting it set up with
> 17.7. When I try to create a pipeline (before adding the authorization
> plugin), I get a CSRF error.
>

That's usually an indication that you have another server running on the
same host but different ports causing all sorts of weirdness. Could you
confirm that you only have one server running on "localhost", or whatever
you're using for development?


> If I add the authorization plugin, I can never get past the login screen
> (similar to https://groups.google.com/forum/m/#!topic/go-cd/Qe_tEdgQhTg).
> I'm curious if there's any obvious environment issues between us, as the
> Vagrant box should give us the same environment :/ Alternatively, could the
> gocd demo Vagrant box get updated to the latest version of GoCD, so I can
> use that as a base instead of rolling my own?
>

What demo vagrant box are you referring to? We use the box built out of the
Vagrantfile  checked
into the gocd repository. Alternatively:

docker run -it --rm -v $(pwd):/gocd -v
$HOME/.gradle:/go/.gradle gocdcontrib/gocd-dev-build:v1.0.23 /bin/bash

The docker example is a lot easier to work with, since it involves not
having to download and install stuff on a network. If you run that docker
command in the directory containing your gocd sourcecode, it's mounted in
`/gocd` inside the docker container.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: go is running all tasks in a job continously in a loop

2017-06-28 Thread Ketan Padegaonkar
Could you open an issue on github and attach the server and agent logs from
the time window that the the job was re-running.

On Thu, Jun 29, 2017 at 10:27 AM Pankaj Lal  wrote:

> Doesn't look like as I don't see any exception and I did try the
> workaround of converting artifacts to build artifact. But nothing changed.
> It's quite weird to see it run for 15 times and the finish succesfully.
> It's not an infinite loop too or a loop that closes after any needed
> resources exhaust. It just does it for certain number of times and stops.
>
>
> On Wednesday, June 28, 2017 at 2:07:09 AM UTC+5:30, Darren Rowley wrote:
>>
>> We ran into this issue when upgrading to 17.4 also, although we had hit
>> it before.
>>
>> On a particular job our agent started going:
>>
>> 2017-06-07 07:53:02,095 [loopThread] ERROR
>> springframework.scheduling.timer.MethodInvokingTimerTaskFactoryBean:68 -
>> Invocation of method 'loop' on target class [class
>> com.thoughtworks.go.agent.AgentHTTPClientController] failed
>>
>> java.lang.OutOfMemoryError: GC overhead limit exceeded
>>
>>
>>
>> It is related to this bug..
>>
>> https://github.com/gocd/gocd/issues/1202
>>
>> Worked around it by changing the clobbing on our test artifact archiving..
>>
>> Could be your issue too?
>>
>> D.
>>
>>
>> On Tuesday, June 27, 2017 at 11:21:06 PM UTC+12, Pankaj Lal wrote:
>>>
>>> I just upgraded to 17.5 yesterday. I am seeing this very funny
>>> behaviour. All the tasks in a job are executing in a loop. They are
>>> supposed to execute only once. Why is this happening.
>>>
>>> See the attached image. You would notice the same things multiple times.
>>>
>>>
>>> 
>>>
>>> - Pankaj
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] resources question

2017-06-19 Thread Ketan Padegaonkar
On Mon, Jun 19, 2017 at 8:36 PM Roy Nielsen  wrote:

> On the other hand, could a plugin do this?
>

You probably want to look at elastic agent plugins
 that can determine
agent assignment based on arbitrary rules.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] resources question

2017-06-19 Thread Ketan Padegaonkar
You're probably looking for agent autoregistration
.

On Mon, Jun 19, 2017 at 7:53 PM Roy Nielsen  wrote:

> Hello,
>
> I guess what I'm thinking is - would it be possible for an agent to
> self-identify a bunch of these resources to the server when connecting, or
> when the server polls for resources?
>
> If you are familiar with puppet - kind of like puppet facts.
>
> Regards,
> -Roy
>
>
> *What man is a man who does not make the world better?*
> *- Balien of Ibelin, Kingdom of Heaven*
>
>
> On Mon, Jun 19, 2017 at 8:06 AM, Roy Nielsen 
> wrote:
>
>> Hello,
>>
>> I'm new to good - maybe this question is clearly answered elsewhere, but
>> a quick search didn't find the answer.
>>
>> If I were to say a job needs 16 Gb of memory, or 24, or 64 memory
>> available, I could create a tag/resource, right?  What about hard drive, #
>> of CPUs, CPU properties, network capability, operating system, os version,
>> etc, etc.
>>
>> That starts to be a lot of tags/resources.
>>
>> Would it be possible to have some json or yaml describe the requirements
>> for a specific job,  Maybe it already is available?
>>
>> Is it or could it be possible to have gocd understand an extended set of
>> environmental (HW/OS/compiler availability/etc) conditions when choosing an
>> agent to run jobs on?  Using resources/tags could get complicated fast.
>>
>> Thank you,
>> -Roy Nielsen
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "go-cd" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/go-cd/LToOPUdoXgs/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> go-cd+unsubscr...@googlegroups.com.
>
>
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] goCD API - The resource you requested was not found!

2017-06-15 Thread Ketan Padegaonkar
On Thu, Jun 15, 2017 at 11:38 AM  wrote:

> Thanks for the real quick reply, Ketan
>
> Changing v2 -> v4 worked for /go/api/agents, but not for /go/api/users
> (the same resource not found error). Am I missing something here?
>

Every api call uses a different version header, because their change cycles
are different. Please consult the API docs before you use any APIs.

I would like to suggest to make the message useful - rather than 'resource
> not found', 'unsupported version' or 'resource not found due to unsupported
> version header - currently supported versions - (list of versions)', etc.
> Also, some warning messages to log files?
>

Can you submit an issue on GitHub?

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] goCD API - The resource you requested was not found!

2017-06-14 Thread Ketan Padegaonkar
On Thu, Jun 15, 2017 at 11:13 AM  wrote:

> Go Version: 17.5.0 (5095-3130b5ba96f8155ae86fefb261a559d4c7493326).
>
> curl -u ":" -H 'Accept: application/vnd.go.cd.v2+json' -H
> 'Content-Type: application/vnd.go.cd.v2+json; charset=utf-8'
> http://localhost:8153/go/api/agents
> =>
> {
>   "message": "The resource you requested was not found!"
> }
>

Version v2 of the API has been removed as 17.5.0. Please check the API docs
 for the correct version header you
need should specify.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Can't connect to newly installed go-server

2017-06-07 Thread Ketan Padegaonkar
You're likely using openjdk9(that is the default jdk that gets pulled in on
Ubuntu 16.4). Please downgrade to openjdk8 instead.

On Thu, Jun 8, 2017, 5:39 AM  wrote:

> Hi
>
> I used to use GoCD a couple of years ago, then stopped. Now I'd like to
> use it again.
>
> I installed go-server on Ubuntu 16.04 server, by following:
>
> https://docs.gocd.org/current/installation/install/server/linux.html#debian-based-distributions-ie-ubuntu
>
> It installed Version 17.5.0-5095.
>
> After installation and start by doing "/etc/init.d/go-server start", I
> issued:
>
> telnet localhost 8154
> telnet localhost 8153
>
> And it seems to me there is nothing to listen those ports.
>
> Could anyone point me what am I missing ?
>
> Additional questions. IIRC, go-server used to use DB and my choice of DB
> was PostgreSql. I couldn't find any database requirement from the new
> documentation. Do I need database? Where can I find DB configuration
> documentation?
>
>
> Thanks!
>
> - J
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[go-cd] Release Announcement - GoCD 17.5.0

2017-06-02 Thread Ketan Padegaonkar
Hey All,

A new version (17.5.0) of GoCD is out.
Know more about the features and bug fixes in this release here 
 or head to our downloads 
 page to try it.

Cheers,
GoCD Team

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[go-cd] Moving domains to gocd.org

2017-06-01 Thread Ketan Padegaonkar
Hi there,
 
We wanted to let you know that GoCD has moved domains from gocd.io to 
gocd.org today. You can read more about the move on our blog 
.

This switch will have no impact on any of our existing users. We will be 
setting up redirects from gocd.io to gocd.org. Any link to either gocd.io 
or go.cd will continue to work as-is and redirect you to gocd.org. However 
we do encourage any third party apps or sites to use gocd.org going forward.

Thank you for supporting GoCD!


-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] how to file a gocd bugreport?

2017-04-27 Thread Ketan Padegaonkar
We were swamped with closing out and testing things before the release for
the last few days. I'll review this PR today.

On Thu, Apr 27, 2017 at 2:28 PM Chris Northwood <cnorthw...@gmail.com>
wrote:

> Hi,
>
> I've raised a pull request to address this, as we're also hitting this
> issue: https://github.com/gocd/gocd/pull/3426 (applying the phoenix
> server pattern to all our infrastructure, including GoCD, so being able to
> mount remote storage for persistence is important to us, currently we lose
> all artifacts on every deploy). I'm not sure what the process to get this
> PR reviewed is?
>
>
> On Wednesday, 19 October 2016 16:06:12 UTC+1, richard@nordcloud.com
> wrote:
>>
>> Thanks, I have filed a bug report on Github:
>>
>> #2797
>>
>> Gr Richard
>>
>> On Wednesday, October 19, 2016 at 4:05:48 PM UTC+2, Ketan Padegaonkar
>> wrote:
>>>
>>> Not that it helps —
>>> https://forums.aws.amazon.com/thread.jspa?threadID=234928
>>>
>>>
>>> On Wed, Oct 19, 2016 at 7:30 PM Ketan Padegaonkar <ketanpad...@gmail.com>
>>> wrote:
>>>
>>>> Could you file a bug report over at GitHub? On initial investigation,
>>>> it appears that the amount of disk space on the efs volume (8 exa bytes) is
>>>> too much for a long data type and the value rolls over to a negative
>>>> number, which makes it look like we're running out of disk space.
>>>>
>>>> [root@ip-172-31-57-237 efs]# df -h
>>>> FilesystemSize  Used Avail
>>>> Use% Mounted on
>>>> devtmpfs  488M   60K  488M
>>>>   1% /dev
>>>> tmpfs 498M 0  498M
>>>>   0% /dev/shm
>>>> /dev/xvda17.8G  1.3G  6.5G
>>>>  16% /
>>>> us-east-1b.fs-1ac11453.efs.us-east-1.amazonaws.com:/  8.0E 0  8.0E
>>>>   0% /root/efs
>>>>
>>>>
>>>> [root@ip-172-31-57-237 efs]# ~/jruby-9.1.5.0/bin/jruby -e "puts
>>>> java.io.File.new('/').getUsableSpace; puts
>>>> java.io.File.new('/root/efs').getUsableSpace"
>>>> 6924935168
>>>> -9223372036854775808
>>>>
>>>> On Wed, Oct 19, 2016 at 6:57 PM <richard@nordcloud.com> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I think Im running into a gocd bug wrg to available diskspace on an
>>>>> AWS efs volume. As soon as I have my artifacts dir pointed to a efs mount
>>>>> (which have a capacity of EXAbytes...) , after a gocd restart, it will
>>>>> throw an error in the gocd console:
>>>>>
>>>>> Go Server has run out of artifacts disk space. Scheduling has been
>>>>> stopped [Oct-19 13:23:17]
>>>>> Go has less than 100Mb of disk space available. Scheduling has
>>>>> stopped, and will resume once more than 100Mb is available.
>>>>>
>>>>>
>>>>>
>>>>> Thanks, Richard
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "go-cd" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to go-cd+un...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] go-agent missing in the "Agents" tab

2017-04-12 Thread Ketan Padegaonkar
Can you log an issue on github with the complete stack trace?

On Thu, Apr 13, 2017 at 4:46 AM Santhosh Basavaraju <
e.patra.benk...@gmail.com> wrote:

> Hi ,
>
> All the agents from the Agents tab disappeared suddenly and when i click
> in the "Agents" tab i got the below error in go server logs. Go server
> restart didn't help.
>
> 2017-04-12 17:08:10,952 FATAL [qtp999661724-6576104] Rails:? -
>
> ActionController::UrlGenerationError (No route matches {:action=>"update",
> :controller=>"api_v4/agents", :uuid=>""} missing required keys: [:uuid]):
>
>   app/controllers/application_controller.rb:196:in `url_for'
>
>   app/presenters/api_v4/agent_representer.rb:27:in `AgentRepresenter'
>
>   app/presenters/api_v3/base_representer.rb:102:in `to_hash'
>
>   app/presenters/api_v3/base_representer.rb:102:in `to_hash'
>
>   app/controllers/api_v4/agents_controller.rb:27:in `index'
>
>   lib/jetty_weak_etag_middleware.rb:35:in `call'
>
>   lib/catch_json_parse_errors.rb:8:in `call'
>
>
> I realized it was a UI issue and the agents were all working fine as my
> pipelines worked without any issue.
>
>
> In what case do we face this issue?
>
>
> Regards
>
> San
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] StageStatusChange: sample messages

2017-03-21 Thread Ketan Padegaonkar
Badri,

We don't have a schema available (because we don't validate or test against
the schema). But to answer your specific question about the possible values
of the fields —

This code

is
what is responsible for rendering the stage JSON. It seems like we're
stringifying some

enums

from core. Would you mind submitting a PR to improve the documentation?


On Wed, Mar 22, 2017 at 5:48 AM Badri Janakiraman 
wrote:

> Hello
>
> I am trying to understand a couple of things about the StageStatusChange
> message.
>
>1. Does it get sent when a stage starts AND finishes - or is it only
>sent when one finishes? I assume both - but I wanted to check.
>2. Are there samples for the content and structure of this message for
>when the stage starts? Or if it gets re-run?
>
> I noticed that there is an example here:
> https://plugin-api.gocd.io/current/notifications/#stage-status-changed -
> but that seems to be for a simple stage completion for a stage with with
> exactly one job. How can we know what values to expect for the various
> fields like state and status at the stage and job levels? Is this just
> something that we have to run and see? Is there a JSON schema somewhere
> that gives us some information about the expected structure - similar to
> the plugin.xml schema that is published here
> 
> ?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


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

2017-03-16 Thread Ketan Padegaonkar
Going from 15.2 to 17.2 is a huge jump. I suggest going through the release
notes to see breaking changes and known issues may affect you. The biggest
one being that you now need java 8 on the agent and server machines.

On Thu, Mar 16, 2017 at 5:07 PM Diogo Oliveira <
diogo.olive...@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 Server and Agents. All of them
> communicate through 80/443 instead of 8153/8154. Are these changes
> preserved in the upgrade? Since the Go configurations changed in versions
> after 15.2 (I checked that), will this still work?
>

If you're doing this by setting the variables GO_SERVER_PORT and
GO_SERVER_SSL_PORT variables. The server should upgrade smoothly without
any issues. We recommend that you compare the copy of
/etc/default/go-server with the current one

that we have to see if anything needs changing.


> 2 --> All of my Go 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?
>

The agent CLI has changed significantly since 15.2. The GO_SERVER
and GO_SERVER_PORT variables that were used to connect the agent to the
server have been deprecated - use GO_SERVER_URL instead. Additionally see
this

to
improve security.

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Unable to install on Ubuntu 16.04

2017-02-25 Thread Ketan Padegaonkar
OpenJDK 9 is currently not supported. Please use openjdk 8 instead.

On Sat, Feb 25, 2017 at 3:03 PM thelordmortis  wrote:

> Hey there,
>
> I've just followed the directions here
> 
>  to
> install the Go-CD server and I have encountered two errors:
>
> The first is that OpenJDK 9 appears to have deprecated the PermSize config
> directive. After tweaking the startup file I get the following error:
>
> 2017-02-25 16:58:31,272 ERROR [main] ContextLoader:307 - Context
> initialization failed
> org.springframework.beans.factory.BeanDefinitionStoreException: Failed to
> load bean class: com.thoughtworks.go.util.TimeProvider; nested exception is
> java.io.FileNotFoundException: class path resource [java/lang/Object.class]
> cannot be opened because it does not exist
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:293)
> at
> org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:227)
> at
> org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:623)
> at
> org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:454)
> at
> org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:383)
> at
> org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:283)
> at
> org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:111)
> at
> org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
> at
> org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
> at
> org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
> at
> org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)
> at
> org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1342)
> at
> org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:741)
> at
> org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:505)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:132)
> at org.eclipse.jetty.server.Server.start(Server.java:387)
> at
> org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:114)
> at
> org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:61)
> at org.eclipse.jetty.server.Server.doStart(Server.java:354)
> at
> org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
> at
> com.thoughtworks.go.server.Jetty9Server.start(Jetty9Server.java:93)
> at
> com.thoughtworks.go.server.GoServer.startServer(GoServer.java:71)
>
> And I'm at a complete loss as to why java/lang/Object.class can't be
> found.
>
> Here is my DPKG output, the system has 4GB of ram.
>
> Desired=Unknown/Install/Remove/Purge/Hold
> |
> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name   Version  Architecture Description
>
> +++-==---==
> ii  accountsservice0.6.40-2ubuntu11 amd64query and
> manipulate user account information
> ii  adduser3.113+nmu3ubuntu all  add and
> remove users and groups
> ii  apparmor   2.10.95-0ubuntu2 amd64user-space
> parser utility for AppArmor
> ii  apt1.2.19   amd64commandline
> package manager
> ii  apt-transport-https1.2.19   amd64https
> download transport for APT
> ii  apt-utils  1.2.19   amd64package
> management related utility programs
> ii  aptitude 

Re: [go-cd] Setting up gocd development environment

2017-01-17 Thread Ketan Padegaonkar
; at
> com.thoughtworks.go.build.ExecuteUnderRailsTask.super$5$exec(ExecuteUnderRailsTask.groovy)
> at
> com.thoughtworks.go.build.ExecuteUnderRailsTask.exec(ExecuteUnderRailsTask.groovy:82)
> at
> org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:75)
> at
> org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.doExecute(DefaultTaskClassInfoStore.java:133)
> at
> org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:126)
> at
> org.gradle.api.internal.project.taskfactory.DefaultTaskClassInfoStore$StandardTaskAction.execute(DefaultTaskClassInfoStore.java:115)
> at
> org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:623)
> at
> org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:606)
> at
> org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:80)
> at
> org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:61)
> ... 68 more
>
>
> BUILD FAILED
>
> Total time: 1 mins 41.747 secs
>
> Entire log : output.log
>
>
> On Tuesday, 17 January 2017 15:29:26 UTC+5:30, Ketan Padegaonkar wrote:
>
> The task assets:precompile ususlly fails when nodejs is not installed, if
> you have installed nodejs, can you provide the complete ruby stacktrace in
> a github gist <https://gist.github.com>? The stacktrace you've provided
> is not adequate since it prints the bottom of the stack, not the top.
>
>
> On Tue, Jan 17, 2017 at 2:42 PM Aditya Byreddy <mr.adit...@gmail.com>
> wrote:
>
> Hi, I'm trying to setup gocd development environment on Ubuntu 14.04 fresh
> operating system. I've followed the steps as mentioned in the
> https://developer.gocd.io/current/2/2.1.html . But when I tried to issue
> ./gradlew clean agentGenericZip serverGenericZip
> process is failed saying
>
> s'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:102:in
>  `top_level'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:80:in
>  `run'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:178:in
>  `standard_exception_handling'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:77:in
>  `run'
> ./bin/rake:4:in `(root)'
> Tasks: TOP => assets:precompile => requirejs:precompile:external
> :server:compileAssets FAILED
> :server:compileAssets (Thread[Daemon worker Thread 4,5,main]) completed. Took 
> 54.003 secs.
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':server:compileAssets'.
> > Process 'command '/home/gocd/Desktop/gocd/tools/rails/bin/jruby'' finished 
> > with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --debug option 
> to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 39.411 secs
> Stopped 0 compiler daemon(s).
> Received result Failure[value=org.gradle.initialization.ReportedException: 
> org.gradle.internal.exceptions.LocationAwareException: Execution failed for 
> task ':server:compileAssets'.] from daemon DaemonInfo{pid=14520, 
> address=[8079580b-5bac-4fcc-8aa5-e7d0127017fd port:35122, 
> addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=true, 
> lastBusy=1484597259833, 
> context=DefaultDaemonContext[uid=9072120a-cda2-4ff5-83d3-1c876d6a58cf,javaHome=/usr/lib/jvm/java-8-oracle,daemonRegistryDir=/home/gocd/.gradle/daemon,pid=14520,idleTimeout=1080,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]}
>  (build should be done).
>
>
> Can anyone help me out in resolving this ??
>
> Thanks,
> Aditya
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+un...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Setting up gocd development environment

2017-01-17 Thread Ketan Padegaonkar
The task assets:precompile ususlly fails when nodejs is not installed, if
you have installed nodejs, can you provide the complete ruby stacktrace in
a github gist ? The stacktrace you've provided is
not adequate since it prints the bottom of the stack, not the top.


On Tue, Jan 17, 2017 at 2:42 PM Aditya Byreddy 
wrote:

> Hi, I'm trying to setup gocd development environment on Ubuntu 14.04 fresh
> operating system. I've followed the steps as mentioned in the
> https://developer.gocd.io/current/2/2.1.html . But when I tried to issue
> ./gradlew clean agentGenericZip serverGenericZip
> process is failed saying
>
> s'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:102:in
>  `top_level'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:80:in
>  `run'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:178:in
>  `standard_exception_handling'
> /home/gocd/Desktop/gocd/server/webapp/WEB-INF/rails.new/vendor/bundle/jruby/1.9/gems/rake-11.2.2/lib/rake/application.rb:77:in
>  `run'
> ./bin/rake:4:in `(root)'
> Tasks: TOP => assets:precompile => requirejs:precompile:external
> :server:compileAssets FAILED
> :server:compileAssets (Thread[Daemon worker Thread 4,5,main]) completed. Took 
> 54.003 secs.
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Execution failed for task ':server:compileAssets'.
> > Process 'command '/home/gocd/Desktop/gocd/tools/rails/bin/jruby'' finished 
> > with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --debug option 
> to get more log output.
>
> BUILD FAILED
>
> Total time: 1 mins 39.411 secs
> Stopped 0 compiler daemon(s).
> Received result Failure[value=org.gradle.initialization.ReportedException: 
> org.gradle.internal.exceptions.LocationAwareException: Execution failed for 
> task ':server:compileAssets'.] from daemon DaemonInfo{pid=14520, 
> address=[8079580b-5bac-4fcc-8aa5-e7d0127017fd port:35122, 
> addresses:[/0:0:0:0:0:0:0:1%lo, /127.0.0.1]], idle=true, 
> lastBusy=1484597259833, 
> context=DefaultDaemonContext[uid=9072120a-cda2-4ff5-83d3-1c876d6a58cf,javaHome=/usr/lib/jvm/java-8-oracle,daemonRegistryDir=/home/gocd/.gradle/daemon,pid=14520,idleTimeout=1080,daemonOpts=-XX:MaxPermSize=256m,-XX:+HeapDumpOnOutOfMemoryError,-Xmx1024m,-Dfile.encoding=UTF-8,-Duser.country=IN,-Duser.language=en,-Duser.variant]}
>  (build should be done).
>
>
> Can anyone help me out in resolving this ??
>
> Thanks,
> Aditya
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Renaming agents using the API

2017-01-13 Thread Ketan Padegaonkar
Sorry, I replied to the wrong email thread :-(

On Fri, Jan 13, 2017 at 4:15 PM Carl Reid <carlandrewr...@gmail.com> wrote:

> It was me who opened the issue on GitHub and I have no problem with the
> renaming agents, the functionality works very well.
>
>
> On Friday, 13 January 2017 10:10:28 UTC, Ketan Padegaonkar wrote:
>
> The "agent name" currently maps directly to the "hostname" attribute in
> XML. This is something that can be updated via the API
> <https://api.gocd.io/current/#update-an-agent>.
>
> Additionally, during auto-registeration
> <https://docs.gocd.io/current/advanced_usage/agent_auto_register.html>,
> it's possible to setup a hostname of your choice by setting the
> autoregister property *agent.auto.register.hostname*.
>
> This property was specifically introduced to be able to identify multiple
> agents on the same machine. I believe you were the one who opened the
> ticket <https://github.com/gocd/gocd/issues/124> :)
>
> Are you suggesting that this behaviour is now broken?
>
> On Mon, Dec 8, 2014 at 8:18 PM Carl Reid <carland...@gmail.com> wrote:
>
> As I understand it, it is not possible to specify the name of a GO Agent
> when the agent is being installed.
> This is a shame as we have the agent install and auto-registration
> completely scripted including environments and resources however the agent
> name needs to have meaning rather than just the hostname. This is
> especially so when you have multiple agents per machine in which case they
> all get the same name.
>
> Currently we have to install the agent and then edit the xml
> configuration, changing the host name to something meaningful. This is a
> highly manual operation and is subject to the usual problems of time taken
> and the possibility of mistakes.
>
> I was wondering whether there is a another way or renaming the agent?
> Perhaps via the API? Looking through the documentation
> http://www.go.cd/documentation/user/current/api/agent_api.html it does
> not seem like this is possible.
>
> Anyone have any ideas for this problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+un...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Renaming agents using the API

2017-01-13 Thread Ketan Padegaonkar
The "agent name" currently maps directly to the "hostname" attribute in
XML. This is something that can be updated via the API
.

Additionally, during auto-registeration
,
it's possible to setup a hostname of your choice by setting the
autoregister property *agent.auto.register.hostname*.

This property was specifically introduced to be able to identify multiple
agents on the same machine. I believe you were the one who opened the ticket
 :)

Are you suggesting that this behaviour is now broken?

On Mon, Dec 8, 2014 at 8:18 PM Carl Reid  wrote:

> As I understand it, it is not possible to specify the name of a GO Agent
> when the agent is being installed.
> This is a shame as we have the agent install and auto-registration
> completely scripted including environments and resources however the agent
> name needs to have meaning rather than just the hostname. This is
> especially so when you have multiple agents per machine in which case they
> all get the same name.
>
> Currently we have to install the agent and then edit the xml
> configuration, changing the host name to something meaningful. This is a
> highly manual operation and is subject to the usual problems of time taken
> and the possibility of mistakes.
>
> I was wondering whether there is a another way or renaming the agent?
> Perhaps via the API? Looking through the documentation
> http://www.go.cd/documentation/user/current/api/agent_api.html it does
> not seem like this is possible.
>
> Anyone have any ideas for this problem?
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Configuración proxy SSL

2017-01-10 Thread Ketan Padegaonkar
Sorry I don't speak spanish — but it looks like connections to github are
being silently dropped by a firewall or a proxy. Are you in an environment
where github access is disallowed. Try running that command locally?

git ls-remote https://github.com/

On Wed, Jan 11, 2017 at 2:37 AM Zuzy Robalino 
wrote:

> Por favor alguien puede ayudarme, al tratar de realizar el tutorial de
> ejemplo, aparece el siguiente error:
>
>
> 
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: go.cd website is down

2017-01-01 Thread Ketan Padegaonkar
We don't know when the domain will come back. When it does, we're going to
ensure that gocd.io will remain the de-facto hostname — or setup gocd.io to
redirect to the correct domain names.

On Sun, Jan 1, 2017 at 4:51 PM Moritz Lenz  wrote:

> Hi,
>
>
> On Wednesday, 28 December 2016 23:55:56 UTC+1, Aravind SV wrote:
>
> Hello,
>
> There's now an alternate domain in place. Our efforts to reach across
> oceans to get the old domain back have not yet succeeded. Here are the
> details of the new domain:
>
> Site:
>   gocd.io
>
>
> Thanks. Will the old domain come back eventually?
>
> I'm asking because I used it in a book manuscript that's in the layout
> phase right now, and I don't want to ship a bunch of broken links :(
>
> Cheers,
> Moritz
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [go-cd] Re: go.cd website is down

2016-12-28 Thread Ketan Padegaonkar
The team is currently working on setting up an alternative domain name and
migrating over all content to that domain. We expect be online in a few
hours.

Please bear with us until then.

On Thu, Dec 29, 2016 at 1:03 AM tedder  wrote:

> So, uh, Lubaina, why not use an alternate domain?  It seems like having a
> domain backup for political unrest in Congo would be a good thing. There's
> a reason bitly quit using their .ly domain.
>
>
> On Monday, December 26, 2016 at 11:49:32 PM UTC-6, Lubaina Rangwala wrote:
>
> Hi Bala,
>
> Unfortunately, we don't have an ETA yet for when it will be up. We've
> raised a ticket with the registrar and we are waiting to hear back from
> them. For now, this mail thread would be the best place to get the latest
> update.
>
> - Lubaina
>
> On Tue, Dec 27, 2016 at 11:06 AM, Balasubramaniam B 
> wrote:
>
> It is still down. Is there an ETA for when it will be up?
>
> Please let me know if there is any other place where we can get the latest
> updates on this issue.
>
>
> On Friday, December 23, 2016 at 10:33:19 PM UTC+5:30, Ravi Kumar
> Pasumarthy wrote:
>
> Hi,
>
> It looks like www.go.cd website is down. Could you please take a look
> into it?
>
> Incident reported at: 12:58 am SGT.
> curl -i https://www.go.cd
> >> curl: (6) Could not resolve host: www.go.cd
>
> Thanks,
> Ravi
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+un...@googlegroups.com.
>
>
> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
>
> Lubaina Rangwala
> ThoughtWorks - Product Marketing | GoCD
> +91 97 413 813 88
> lubainasr on skype | @lubaina on twitter
>
> --
> You received this message because you are subscribed to the Google Groups
> "go-cd" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to go-cd+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to go-cd+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


  1   2   >