Hi,
I'm looking how possible it would be to allow the customization of a new
Jenkins worker based on the definition of a node within a Jenkinsfile file.
Considering a node provisioner which is able to create new nodes from
Docker images for example, I would like to be able to do something similar
to this:
node("my-node-provisioner", docker_image="internal/jenkins-worker:v12",
memory_limit="4GB") {
// my steps here
}
That would allow the developers to customize the context in which their job
is running in, within the available node provisioner possibilities, while
keeping all the versioning on how the job needs to be executed within the
Jenkinsfile of the project.
Some more context about what I'd like to do: I'm using the Nomad plugin to
schedule our Jenkins jobs in the pool of machines we are managing via the
Nomad scheduler. Nodes ("slave templates" in the Nomad plugin terminology)
can be configured from Jenkins main configuration screen, but it's not that
convenient. See my RFC here for even more details:
https://github.com/jenkinsci/nomad-plugin/issues/20
It's my first time digging inside Jenkins extensions and I don't really
know where I should start to look for. Any pointers would be appreciated!
I'm especially interested to know if it's something which has been done
before, and if it's desirable or not.
Thanks!
Jonathan
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" 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/jenkinsci-dev/3bfab27d-79ab-427b-b67b-ad69a6830001%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
