jenkins-update-center-proxy
所属分类：构建工具
开发工具：JavaScript
文件大小：0KB
下载次数：0
上传日期：2023-06-16 19:14:57
上 传 者：
sh-1993
说明： Jenkins更新中心的镜像代理
(A Mirror Proxy for Jenkins update center)
文件列表:
Dockerfile (226, 2023-12-07)
LICENSE (1072, 2023-12-07)
index.js (415, 2023-12-07)
integration/ (0, 2023-12-07)
integration/Dockerfile (570, 2023-12-07)
integration/plugins.txt (30, 2023-12-07)
ip.js (461, 2023-12-07)
lib/ (0, 2023-12-07)
lib/config.js (2095, 2023-12-07)
lib/file.js (2411, 2023-12-07)
lib/json.js (1663, 2023-12-07)
lib/middlewares/ (0, 2023-12-07)
lib/middlewares/error.js (658, 2023-12-07)
lib/middlewares/health.js (150, 2023-12-07)
lib/middlewares/log.js (999, 2023-12-07)
lib/middlewares/proxy.js (409, 2023-12-07)
lib/proxy.js (1134, 2023-12-07)
package.json (426, 2023-12-07)
renovate.json (41, 2023-12-07)
test.sh (650, 2023-12-07)
test/ (0, 2023-12-07)
test/network.js (2390, 2023-12-07)
yarn.lock (70716, 2023-12-07)
# Jenkins Update Center Proxy
[](https://github.com/onigoetz/jenkins-update-center-proxy/releases)
[](https://hub.docker.com/r/onigoetz/jenkins-update-center-proxy)
A mirror for Jenkins Update Center.
Caches all `.hpi` files locally for faster download next time.
Very practical if you want to build your CI environment on your CI environment.
This is currently a very simple configuration that is supposed to work in environments where Jenkins doesn't have internet access.
## Usage
### Starting the Proxy
The easiest to get started is to use the [docker image](https://hub.docker.com/r/onigoetz/jenkins-update-center-proxy)
```bash
docker run --rm -it -p 3000:3000 \
-v "$PWD/cache:/cache" \
-e LOCAL_UPDATE_CENTER=http://192.168.1.10:3000 \
onigoetz/jenkins-update-center-proxy
```
Be extra careful, about setting `LOCAL_UPDATE_CENTER`, is this should be the public URL of where this Proxy will be exposed.
This is needed for redirects.
### Using the Proxy
In my case, I use it to build Jenkins Docker images with all plugins preinstalled, this is how it works :
```
# Define the update center
ENV JENKINS_UC="http://192.168.1.10:3000"
ENV JENKINS_UC_EXPERIMENTAL="http://192.168.1.10:3000/experimental"
ENV JENKINS_PLUGIN_INFO="http://192.168.1.10:3000/current/plugin-versions.json"
# Install plugins ( either with install-plugins.sh or jenkins-plugin-cli )
COPY plugins.txt /usr/share/jenkins/ref/plugins.txt
RUN /usr/local/bin/install-plugins.sh < /usr/share/jenkins/ref/plugins.txt
```
Notice that the URL is the same as the `LOCAL_UPDATE_CENTER` above.
## Options
| Variable | Default value | Description |
| ---------------------- | ----------------------------- | ------------------------------------------------------------------- |
| `LOCAL_UPDATE_CENTER` | `http://localhost:3000` | The URL to this update center, needed to rewrite redirects and URLs |
| `REMOTE_UPDATE_CENTER` | `https://updates.jenkins.io/` | The update center to take the files from |
| `CACHE_DIR` | `cache` | The cache dir, no need to change this within the Docker image |
| `PORT` | `3000` | The port to listen on |
| `HTTP_PROXY` | `null` | If you're in a corporate environment that needs a proxy |
| `GLOBAL_TIMEOUT` | `25000` | The timeout (in ms) for remote requests |
## Testing
Currently we only have one integration test that starts the application, installs a few Jenkins plugins and checks that they are correctly cached.
```bash
yarn install
yarn test
```
Some URLs to try :
```
GET /update-center.json?version=2.387.1
GET /dynamic-stable-2.387.1/update-center.json
GET /experimental/update-center.json
GET /current/plugin-versions.json
GET /download/plugins/ant/481.v7b_09e538fcca/ant.hpi
GET /download/plugins/antisamy-markup-formatter/159.v25b_c67cd35fb_/antisamy-markup-formatter.hpi
GET /download/plugins/structs/324.va_f5d6774f3a_d/structs.hpi
```
近期下载者：
相关文件：
收藏者：