config that isn't used
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
charm-k8s-jenkins-agent |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As of fc0869932f1bb06
the charm has a config.yaml with:
options:
image:
type: string
default: "jenkins-
description: "The docker image to install. Required. Defaults to jenkins-
tools:
type: string
default: git gcc make bzr
description: Tooling to deploy on jenkins agent node
labels:
type: string
description: Jenkins labels to associate with jenkins agent node
default: ""
jenkins_
type: string
default: ""
description: |
Configure the agent to use an explicit jenkins master instead of using
the jenkins-agent relation. This allows for the agent and master to
be deployed in different environments.
jenkins_
type: string
default: ""
description: |
Jenkins agent name that will be seen on the jenkins master.
Will default to the hostname of the container.
jenkins_
type: string
default: ""
description: "Jenkins API token used to join the master"
jenkins_user:
type: string
default: "admin"
description: "Jenkins user to download agent.jar from master"
However both tools and labels appear to be unused.
It is unclear whether these are carryover from a different charm, and should be pruned, or whether it is intended as desired future use.
Is jenkins_master_url still desirable now that Juju supports cross model relations?
Changed in charm-k8s-jenkins-agent: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
This has been addressed.