Re: [go-cd] GoCD Agent Upgrades
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.
[go-cd] GoCD Environment variable substitution options...
As far as I can tell, when wanting to pass environment variable values as
input to a task, the only way I'm aware of for this to work correctly is to
use the 'bash -c' command. For all of my tasks, I'm usually calling Groovy
scripts and passing command-line options using the 'bash -c' method makes
for a long and messy looking command. Here is an example:
-c
../continuous-deployment/src/OrchestrateFlywayDB.groovy
-propertyFile ../materials/pipeline.properties -env $DEPLOY_ENV -user
$FLYWAYDB_USER -password $FLYWAYDB_PASSWORD
It would be really nice if there was a syntax for referencing environment
variables that GoCD would use to do the environment variable substitution
(similar to how parameters work) so I can call the tool (e.g., groovy)
directly instead of wrapping it in a bash call. Possibly the syntax
${MY_ENV} which is similar to parameters.
This would allow the tool to be called directly and the task definition
would look more like:
../continuous-deployment/src/OrchestrateFlywayDB.groovy
-propertyFile
../materials/pipeline.properties
-env
${DEPLOY_ENV}*//<--ENVIRONMENT substitution by GoCD*
-user
${FLYWAYDB_USER} *//<--ENVIRONMENT substitution by GoCD*
-password
${FLYWAYDB_PASSWORD} *//<--ENVIRONMENT substitution by GoCD*
Is there a way to do this today that I'm missing? If not, I've entered Issue
#3863 in case and wondered what
the potential is for getting this feature added.
Thanks!
-Jeff
--
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] Working package plugin? Yum deprecated...
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.
[go-cd] GoCD Agent Upgrades
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.
