Epic
Goals:
- Decide what is the target Docker base image going forward (e.g AdoptOpenJDK)
- Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow
- Agent Docker packaging supports multi-platform configuration. See https://github.com/jenkinsci/remoting/pull/292
- Agent Docker packaging produces multi-architecture Docker images
- The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management
- The release is automatically triggered for updates in parent images
- slave=>agent renaming
- relates to
-
JENKINS-51986 Java 11: Create Debian Docker images jenkins/slave and jenkins/jnlp-slave
-
- Resolved
-
[JENKINS-54460] Revamp of the Jenkins Agent packaging in Docker
| Link |
New:
This issue relates to |
| Description |
Original:
Goals: * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management |
New:
Goals: * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images |
| Description |
Original:
Goals: * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images |
New:
Goals: * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images * slave=>agent renaming |
| Description |
Original:
Goals: * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images * slave=>agent renaming |
New:
Goals: * Decide what is the target Docker base image going forward (e.g AdaptOpenJDK) * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images * slave=>agent renaming |
| Epic Child | New: INFRA-1857 [ 195395 ] |
| Description |
Original:
Goals: * Decide what is the target Docker base image going forward (e.g AdaptOpenJDK) * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images * slave=>agent renaming |
New:
Goals: * Decide what is the target Docker base image going forward (e.g AdoptOpenJDK) * Agent Docker packaging and release is done on trusted CI so that we can integrate it into the automated release flow * Agent Docker packaging supports multi-platform configuration. See [https://github.com/jenkinsci/remoting/pull/292] * Agent Docker packaging produces multi-architecture Docker images * The flow is unified for jenkins/slave and jenkins/jnlp-slave so that we have only one build flow instead of manual dependency management * The release is automatically triggered for updates in parent images * slave=>agent renaming |
| Labels | Original: agents java11 | New: agents java11 triaged |
| Assignee | Original: Oleg Nenashev [ oleg_nenashev ] |
Basil Crow
made changes -
| Labels | Original: agents java11 triaged | New: agents triaged |