Ok, great. Thanks for helping! Then I know how to fix this with the latest 
version of GoCD.

/Tobias

Den onsdag 11 mars 2020 kl. 10:33:24 UTC+1 skrev Kritika Singh:
>
> Hi Tobias,
>
> Yes you can update an agent's config while it is building. Any change in 
> environment, resources would not effect the current building job. But the 
> next job assigned to that agent will be on basis of environments, 
> resources, etc.
>
> Thanks
>
> On Wednesday, March 11, 2020 at 2:50:59 PM UTC+5:30 [email protected] 
> wrote:
>
>> Hi.
>>
>> Ok, then I understand why this was removed. Thanks.
>>
>> I will have to change my code and use Agents API. A question about this 
>> API then, can I update an agent (for example adding environments) while 
>> that agent is building?
>>
>> /Tobias
>>
>> Den onsdag 11 mars 2020 kl. 09:50:17 UTC+1 skrev Kritika Singh:
>>>
>>> Hello Tobias,
>>>
>>> You can find the discussion around this on: 
>>> https://github.com/gocd/gocd/issues/911
>>>
>>> To give you a brief: Agents were originally stored in the 
>>> cruise-config.xml. Every time any change occurs, the whole config used to 
>>> be updated. This takes up a lot of time considering bigger configs. Hence, 
>>> we decided to move them to DB.
>>>
>>> Since, environments are still stored in the config -  Addition of agent 
>>> via environment API would have required a lock on both config and DB - 
>>> which could have lead to all sorts of lock and rollback issues. Hence the 
>>> decision to keep them separate.
>>>
>>> From 19.9.0 onwards please use the Agents API (
>>> https://api.gocd.org/current/#agents) to update the same. You can also 
>>> do via UI from Agents Page and Environments Page.
>>>
>>> Hope this helps!
>>>
>>> Thanks
>>> Kritika
>>>
>>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/go-cd/5b923cdc-6326-4a52-8c22-67e9d3c0f174%40googlegroups.com.

Reply via email to