This repository was archived by the owner on Mar 8, 2022. It is now read-only.
jcli 0.0.31 #1081
Merged
jcli 0.0.31 #1081
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updating package jcli to release v0.0.31.
Release info
What’s Changed
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 loginIt 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:
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.🚀 Features
📝 Documentation updates
👻 Maintenance