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
I have a GoCD groovy file as above, and elasticProfileId doesn't take any effect in there.
I would appreciate any suggestions.
: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.
:point_up: Edit: Hi @chadlwilson Thank you for your time today;
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.
:point_up: Edit: Hi @chadlwilson Thank you for your time today;
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 ...)
Thanks again
Good weekend.
Hi Team,
Wondering if someone has already solved this behaviour -
During the build process, it pulls and downloads the image each-time (screenshot attached). Since the image size is huge, this process takes up around 3-4 minutes. Is there a way avoid this process on every build? Or any other way to speed up the build process?
3 replies
1 reply
In my current specific case, I'm publishing artifacts and found that the package list is corrupted by presumably multiple containers publishing artifacts at the same time, and mangling the repository (which is a shared resource).
If there's no mechanism in GoCD, I can probably implement something directly in the publish method of the plugin, and acquire/release some server-side locking token, but I figured there might be something built-in? Or a common way to handle this.
2 replies
Hi,
I am trying to perform gocd-server backup.
My gocd-server version is - 18.10.0
when hit perform back up I am seeing below error-
Failed to perform backup. Reason: Could not create the backup directory.
when i run below command on server -
ls ${ARTIFACT_REPOSITORY_LOCATION}
I can see serverBackups directory exists but shows in red.
Any idea how can we fix this?
3 replies
Can someone confirm my understanding of config-repo rules? I'm interpolating the doco, the unit tests, and my own testing.
1) Pipelines defined in the same config repo can refer to each-other without restriction.
2) When allowing a config-repo to "refer" to a pipeline group, that just means it can create/change pipelines within that pipeline group. It does NOT allow for a pipeline in the config repo to depend on the specified pipeline group.
3) To allow one pipeline to depend on another, you must allow it to refer to the specific pipeline.
I recently upgraded, and the config-repos which define pipelines with non-trivial visual-stream-maps all broke. Specifyng they can refer to the other pipeline-group didn't fix it, I have to be explicit about the pipeline.
Does that sounds about right?
19 replies
Hi All,
I'm trying to come up with a notification plugin that will call a webhook with enough information to determine if a pipeline is queued, in_progress or complete.
The https://github.com/digitalocean/gocd-webhook-notification-plugin plugin is close but the stage updates are for individual stages and don't include enough information to determine if the pipeline is complete or not without knowing the pipeline on the receiving side.
Am I holding this wrong? I was looking into creating my plugin for this, but looking at the docs it seems like plugins don't have access to the gocd API, is that correct or am I missing something?
1 reply