1 reply
I see a new elastic agent getting created for every 2 mins, how can I understand this behavior please ?
Here is the console snippet:
Hello All,
I am new to GOCD and i want to make complex workflow as given bellow so how can i build that pipeline please guide me or if any one on discord please give discord id so i can explain what i want make
scenario 1:
my client have 3 server A.primery B.Secondry C.Backup. i want to take data base backup from A to C or B to C (folder to folder). while taking backup i want to deploy my build in parallel
scenario 2:
My client have only one server so i have to stop webserver and taking backup of database (folder to folder) after completing backup process. the pipeline should deploy the build
scenario 3:
My client have only one server so i have to stop webserver and taking backup of database (as Dump) after completing backup process. the pipeline should deploy the build
(Artifact will Build by developers and put in shared drive so i want to copy from there)
-> for this all i want to create single pipeline
-> i want to define at starting of pipeline that i want to take backup or direct deploy the build
Please help me to Build This Process Pipeline
Regards
Nayan Makwana
I've written/am writing a plugin that produces an HTML file in the working directory. On a subsequent call, I now see that cleaning the working directory (with the built-in toggle option) fails because the (created HTML) file can't be removed.
Is there something I can change in the creation of the file (currently it's just using Java's FileWriter class) to make this work properly? I'd have expected the plugins to run as the same or a less privileged 'user' than the clean directory built-in command.
In case it's target specific, this is GoCD 22.1.0 on Windows (agent and server. Probably in future agents will also be in Windows Docker containers, but this error is occurring on the Windows host agent, and in Docker containers I can just use a new container, so no need to clean I guess)
4 replies
In the HTML templates for plugin views, is it possible to (inline, or I guess otherwise) define some reuseable parameterized block, so that the rest of the file could use something more like
<mydivtype propertyName="NameOfPropToBind" required="true"></mydivtype>instead of a large number of repeated (changing in few ways, mostly just the repeated use of "NameOfPropToBind")
<div class="form_item_block">
<label ng-class="{'is-invalid-label': GOINPUTNAME[NameOfPropToBind].$error.server}">label text</label>
<input ng-class="..." type="text" ng-model="NameOfPropToBind" ng-required="true" ... />
<span class="form_error form-error" ng-class="{.....}" ng-show=".....">{{GOINPUTNAME[NameOfPropToBind].$error.server}}</span>
</div>
1 reply
Hi!
I am the author of the CI/CD tool summary: Find your best CI/CD Tool I am planning to update this report soon and I wonder if you would like to verify the information contained therein regarding your tools.
During the creation of this report, I tried to find all the necessary information. However, I think that you as the author of this tool have the most verified information.
I would appreciate your help in this matter.
1 reply
:point_up: Edit: Hi All,
I have a GoCD groovy file as above, and elasticProfileId doesn't take any effect in there.
Per this https://github.com/gocd/pr-pipelines-workflow/blob/master/.gocd/build.gocd.groovy it should work.
Any inputs will be greatly appreciated. Many thanks.
1 reply
thats ☝️my elastic profile id, and it works in yaml files and this is the very first time im trying with goovy files.
Also, my commit with elasticProfileId change triggered the job, but was just waiting for the agent to be launched.
You should be seeing that error on the Config Repositories page for the Groovy repo and also probably flagged as an error on the dashboard header as well.
Yes, Im see that error on the UI but was thinking it was old and not refreshed.
Sorry, you're not really describing a problem I can comment on. It looked like your server was running just fine, it just won't process the update to your Groovy configuration repo until you fix the errors in it, and will keep the previous configuration.
Better to understand and fix errors that are displayed rather than assume they are unrelated, especially when reported against the thing you are looking into (your Groovy config repo)
Hi @chadlwilson Thank you for your time today; its actually working;
As I said, I introduced it in a wrong way to begin with and server thrown an error; I have committed another change (that supposed to be the right way) but server keeps mentioning about the error with the first change and did not proceed to my second change; after I fixed the error server proceeded further with my second change and it worked;
Sure, will keep an eye on the UI errors (which I think am discarding until now)
Thanks again
Good weekend.