Jenkins CLI allows you to manage your Jenkins in an easy way. Jenkins 命令行客户端
MIT License
Bot releases are visible (Hide)
Thanks again to @LinuxSuRen! 🎉
Published by release-drafter[bot] over 1 year ago
Thanks again to @sikmir! 🎉
Published by release-drafter[bot] about 2 years ago
Thanks again to @LinuxSuRen! 🎉
Published by LinuxSuRen about 2 years ago
Thanks again to @LinuxSuRen, @dependabot, @dependabot[bot] and @jxr98! 🎉
Published by release-drafter[bot] about 3 years ago
Thanks again to @JohnNiang, @LinuxSuRen, @dependabot, @dependabot[bot], @fossabot, @jxr98, @wxharry, @yJunS and John Niang! 🎉
Published by release-drafter[bot] over 3 years ago
Published by release-drafter[bot] over 3 years ago
Published by release-drafter[bot] over 3 years ago
Published by release-drafter[bot] over 3 years ago
Published by release-drafter[bot] over 3 years ago
In some cases, we might need to add or remove parameters from Pipeline. It's terrible if you need to deal with too many Pipelines manually. You can add parameters via: jcli job param init-job --add '[{"name":"name","value":"my name","desc":"this is a name"}]'
Delete many job build history across different jobs is also very simple. See also: jcli job history init-job -d 1
Sometimes, it's very slow to download jenkins.war. From now, jcli can download it with multiple threads. For example:
# jcli center download -t 8
start to download with 8 threads, size: 67287051, unit: 8410881
Another big feature is that, jcli can start Jenkins in Docker with a single command:
jcli center start -m docker --image kubespheredev/ks-jenkins --version 2.249.1 --c-user root --port 9090 --setup-wizard=false
The star from GitHub is 234, star from Gitee is 251. The download is 11,168.
Published by release-drafter[bot] almost 4 years ago
This is a small release version. The main idea of this is to remove CASC from jcli core. You want to use it. Please see here.
Published by release-drafter[bot] almost 4 years ago
It's been a long time not to have a release of jcli. But it's totally worth to upgrade it. Let's see what you can get.
Normally, you need to set up the config file of jcli if this is the first time you install it. Generating the user token from Jenkins, then write it back to the config file is a pretty annoying process. But it's not necessary anymore. It can be automatically now. You just need to run the following command:
jcli center login
It will open the browser, and your config file will be ready once you login into Jenkins. But there's one limitation that does exist. Jenkins and your computer must be about to connect to each other. Besides, you need to install one more plugin.
The second feature is the Jenkins formula. Thanks @oleg-nenashev for taking the initiative to start Custom Jenkins WAR packager. We can generate a custom distribution of Jenkins. jcli support to export a formula from a Jenkins. Also, it can install all plugins that come from a Jenkins formula file. Check out these two commands below:
jcli plugin formula > formual.yaml # export into a YAML formula file
jcli plugin install --formula formual.yaml # install plugins from a formula file
The third feature is that we can run Jenkins as a docker container via jcli center start -m docker
.
What is next? I know a lot of newcomers to Jenkins feel terrible when they meet the plugins dependency issues. So please don't hesitate to file a pull request to close this issue if you're interested.
Do you want to upgrade? It's very simple: jcli version upgrade
.
Published by release-drafter[bot] over 4 years ago
For many uses who want to integrate Jenkins into their own platform, they might meet a problem. How can I get the build ID after I triggered a job?
In order to have a better understanding about it. I guess you need to know the mechanism of Jenkins schedule. If a job was triggered, Jenkins will create a task in the waiting queue, once there is a appropriate agent is ready for it, then Jenkins will schedule it to that agent.
In another word, it's a asynchronous process. So you cannot get the build id immediately, because it has not started.
There's my offer. Install plugin Pipeline restFul API v0.9 on your Jenkins, upgrade Jenkins CLI to v0.0.30. Then take the following command:
jcli job build job/devops/ -b --wait --columns Number --no-headers
The output is 36
.
Published by LinuxSuRen over 4 years ago
Published by LinuxSuRen over 4 years ago
Jenkins CLI now has plugin mechanism. The first plugin allow you share your configuration via git among your team members.
e2e tests could be a good practice to improve the quality of this project. In later, we will increase more test cases.
Published by LinuxSuRen over 4 years ago
Published by LinuxSuRen over 4 years ago
Published by LinuxSuRen over 4 years ago
Published by LinuxSuRen almost 5 years ago
Published by LinuxSuRen almost 5 years ago