Time triggered pipelines with dependent/upstream pipelines - possible?
We want to solve this type of use case:
Stage pipeline deploys on every commit, prod pipeline deploys nightly on latest green commit that passed the stage pipeline. Both pipelines has the same Git repo as input material. Prod pipeline is dependent on Stage pipeline.
However, when triggered according to timer GoCD picks the latest git repo hash of the material and not the latest successful commit that ran in the stage pipeline. This is nothing that is solved by GoCD or? Has someone implemented tooling for this use case? Other ideas?
We're currently running an older GoCD version (20.1) because of various reasons (missing installers for ARM processors), but can upgrade if it helps.
Hello GoCD Community,
I am Rahul Khinchi and I want to use GoCD for my project. I just wanted to clear some doubts before integrating it. What benefit does GoCD have on automating the release process? Point to the actual step(s) that a GoCD will help to automate.
Your response is appreciated. Please reply for the same
I have a very very basic question related to pricing of GoCD, do we have any enterprise version of GoCD?
jar:onejar:lib/agent-22.1.0-13913-classes.jar!/config/agent-logback.xml'. 2022-04-25 17:43:54,823 - [Mon Apr 25 17:43:54 IST 2022] Starting process: 2022-04-25 17:43:54,824 - [Mon Apr 25 17:43:54 IST 2022] Working directory : /var/lib/go-agent 2022-04-25 17:43:54,824 - [Mon Apr 25 17:43:54 IST 2022] Application arguments: [-serverUrl, https://server-name/go, -sslVerificationMode, FULL] 2022-04-25 17:43:54,824 - [Mon Apr 25 17:43:54 IST 2022] GoCD Version: 21.3.0-13067 2022-04-25 17:43:54,824 - [Mon Apr 25 17:43:54 IST 2022] Java Version: 17.0.2 2022-04-25 17:43:54,824 - [Mon Apr 25 17:43:54 IST 2022] Operating System: Linux(5.13.0-40-generic) 2022-04-25 17:43:55,242 - Could not find fileconfig/agent-logback.xml'. Attempting to load from classpath.
@xunyao4dev you can pretty much do anything in GoCD that you can on the command line.
“Deploy a jar” could mean many things. In the simplest form, it might only mean “upload the jar via SCP or HTTP POST, move the jar to a known location and start the JVM with
java -jar myproject.jar. If it’s Tomcat, there are many tutorials online to use their deployment API with
curl or similar tool.
If it’s not that, check for the same on /bin/bash.
Also, if neither works, make sure both of those binaries are actually correct and not a text file that was accidentally copied over it. This can happen accidentally if you’ve built an image and running in a container