[
https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37588#comment-37588
]
Daniel Belenky commented on OVIRT-2359:
---------------------------------------
Solution I've implemented is adding another systemd unit that reads environment
from /proc/1/environ, filters some irrelevant vars such as HOME and PATH,
formats the data and writes the rest to /etc/environment. Then /etc/environment
is used as EnvironmentFile for systemd which then loads jenkins-jnlp-agent.
The current containers startup script gets (via CLI) and a list of agent
secrets.
I've created OVIRT-2364 to automatically register agents and generate the names.
> Set environment variable in jenkins user's env to inidicate it's a container
> ----------------------------------------------------------------------------
>
> Key: OVIRT-2359
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Daniel Belenky
> Assignee: infra
>
> We need to set a variable under the jenkins user that will indicate we're
> running inside a container.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
_______________________________________________
Infra mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/[email protected]/message/25YNRPJ57BZH4SJH3CNQ54QGY6OQYYHA/
