March 2016 klimas7 (Boguslaw Klimas) he began to the care and maintenance of the plugin. In May 2014 ngiger (Niklaus Giger niklaus.giger) decided to maintain this plugin and bring in the various improvements made by others. This plugin was offered to the community by lukanus (Łukasz Miłkowski end of 2011. How to we test the configuration dialog? How do we test whether correct tags are listed when a user triggers a build? "Issue lukanus": lukanus#14Īllow translations by converting all html stuff to jellyĪdd explanation when configuring the sort modeīetter testing. Even though the GIT SCM module has the ability to provide "credentials" (SSH key) for the repository, the git-parameter plugin doesn't seem to use them.Will speed up listing tags and avoids cloning/fetching the content. TODOĪdd a new method listRemoteTags(URL) to git-client-plugin to use. If you want to add some changes for this plugin:Īdd the issue in jenkins JIRA to the component git-parameter-pluginĭescribe there why you need change the plugin. The Jenkins-CI of this plugin can be seen at Request Policy There you find an option to upload a plugin. Test your changes by going to your Jenkins-CI site and import the generated target/git-parameter.hpi by going to your base URL + jenkins/pluginManager/advanced. You may checkout/clone this project and build it by simply calling mvn clean install in the root of the checkout. Visit for "information about developing Jenkins-Plugins" This error occur when there are no ssh command on Jenkins master.This error occur when the repository is not exists or URL is wrong.This error occur when the repository is not configured or 'Use repository' option not match with any repository.We can see that there were other changes from the word function to export default, and that's been done throughout this commit on multiple files.If an error occurred while retrieving data, the default value is returned.Īdditional information is provided below, along with the cause of the error. We see that the message was to upgrade to ECMAScript 2015 modules. Now we have the full context behind this commit. Let's also use the patch option so that we see the diff. Now let's paste in the ID of the commit that we copied. For example, let's use the git log command to see more information about the rest of the changes in this commit. To get more context around this change, I like to copy the commit ID here, and then use other tools to find out more information. In this case, we know that the export default line change was made on July 2nd, and it was made by Trevor. For each line, we have the commit ID of when the line was last modified, as well as who last modified it, and when that change was made. In this case, for the geturlslug file, we have five lines in the file. When we run the git blame command, it shows us the details of how each line was last modified inside of the file that we passed in. What we can do is let's go back to our command line, and let's run the git blame command with the name of our file, which was geturlslug.js. We want to know why they added this export default. In our code editor, we're working on a file, and we'd like to know who last modified this line number one.
0 Comments
Leave a Reply. |