I am extremely busy right now. So, I cannot build plugins at this moment.
How can I put in a request for a Jenkins plugin to be created? I want a Jasmine plugin for Jenkins created.
I do not see the answer at the Jenkins Plugin page.
Again, I wish I had time to create one. However, I barely have time to write this question! :)
Thank you!
I would try posting on the jenkins mailing list. There also is a list with plugin ideas somewhere in the Jenkins Wiki, however, it is outdated, and hard to find, so I would not bother much with it. Best option should be the mailing list, lots of plugin developers roam around there.
Related
I would like to integrate my sonarqube instance with a confluence space, so all my team could have access to the project metrics. Does anyone know any plugin that does this or how to do it without a plugin? Thanks
You're looking for badges, which allow you to embed a little image in a page with a metric name and current metric value. This is a native feature on SonarCloud.io, and coming soon for SonarQube. In the meantime, there's a community plugin you can use.
We experienced the same need and a colleague recommended me to give this a try:
https://marketplace.atlassian.com/plugins/es.excentia.confluence.plugins.confluence-sonarqube-connector/server/overview
We are currently in the evaluation stage, and quite happy with its use and functionality.
I have a plugin's resource codes and I want to edit. Because I want to change plugin's prefix but it isn't possible unless edit plugin. I tried edit with Eclipse but I had a lot of errors.
If you have source codes of some plugins, there meight be a problem, that they are using some api for example WorldEdit api, but you don't have it added in your project. You have to look into code and find out what they use. Then download the api and add it in Build Path - Right Click the project->Build bath->add external Jars. I hope this will help.
You may be getting errors from imports, API's, etc.
The best way to change this is to contact the developer of the plugin, who has the project themselves. It's not a good idea to change code unless you have full permission; but I will still tell you some possible ways to fix it.
Your imports may be faulty, check those.
Actually REVIEW the code yourself– Don't mess around with things you don't know what they do.
CHANGE YOUR PACKAGE NAMES (This got me before, simple mistake)
If there are comments in the code, use those to your advantage
Google your errors.
If you are new to Java, don't skip to changing code already. TRUST ME. Learn all you can before skipping to other "higher level" developer styles.
Like I said, these are vague and simple ways to fix it; the best way to have your feature implemented is to contact the developer.
*I understand that this thread is old; I'm just saying this because there are currently no answers that describe this for other Google travelers of the internet.
Where can I find a developer guide to kibana, that explain me how the system work and all the things i need to know for developing kibana plugin?
Or if someone could publish snippets of sample plugin.
I've started cloning statusPage plugin, but I don't want to do revers engineering to understand the platform.
On the website, the is no type of developer manual.
Thank you
You can refer to the following links to learn How to develop Kibana Plugins:-
http://logz.io/blog/kibana-visualizations/
https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/
The official answer from 6+ months ago seems to be "don't":
We're working to develop an external API but would caution you away
from making custom changes as things still move pretty fast and
internal APIs are likely to change even in patch versions.
Also, "there are no public plugin APIs right now" (8/2015)
Hard to find any information to date. I recommend you to look at the plugin generator released some days ago:
Generator Kibana Plugin Structure
There are two plugins I found where you can have a look at the code to understand the structure. The first is the Sense plugin, the second Timelion. Timelion matches more to the structure of the generator.
Sense Github
Timelion GitHub
I suggest understanding plugin structure and code for traffic plugin (https://github.com/sbeyn/kibana-plugin-traffic-sg) which would be one of the simplest plugins to understand and you could directly add it to your installed plugin folder in kibana and see it working.
Other than that I would also suggest you do read timroes blogs (https://www.timroes.de/2015/12/02/writing-kibana-4-plugins-basics/) for developing kibana plugins
and last I would also suggest using elasticsearch discussion forum for kibana related issues as well for quicker responses:
https://discuss.elastic.co
In some cases I need to mark (several) lines of code in Eclipse. For example when reviewing, or when testing. Is there a feature or plug-in in Eclipse which can help me to that?
For now I'm just putting #REVIEWED or #TOBEREVIEWED on lines or around blocks. But that is a lot of work.
Any ideas?
EDIT: I'm aware of the Bookmark feature, but that seems to cover only 1 line.
EDIT2: I'm also aware of Task tags like TODO and FIXME, thanks E-Riz
You can use custom task tags in comments (the default is //TODO), which are automatically added to the Markers or Problems views in Eclipse. for example, you could create a custom task tag like //TO-REVIEW.
It's not exactly marking blocks of code, since it's essentially a marker for one line, but it is a convenient way to track and locate them. See the Eclipse Help page for more details.
Why not use some code review features of external server like GitHub?
I mean it could be nice to comment and discuss code blocks just within Eclipse,
but it is much overhead to develop and maintain comparing to web-based solution (that would be universal).
Then possibly such server has similar feature support as Eclipse plugin.
For example
if you use git, you can check GitHub and Eclipse EGit and Eclipse Mylyn tasks.
For perforce there is job concept (similar to issues).
So it leads to understanding that what you actually need is issue-tracker integrated into Eclipse that can conveniently point to code blocks. Again depends on your SCM.
You can us Eclipse plugin like Jupiter for code review. It will help to identify issues (if any) in code blocks with review comments without touching actual code.
The code review comments get stored in jupiter files in your respective project.
Developer can see those issues, fix and comment on them.
I was asked to create a simple JIRA plugin that combines Workflow + Custom Fields + Conditional Steps
I just started installing JIRA and finally managed to create a run a simple Hello World Plugin.
I am already confused with how huge this interface is, and cannot seem to be able to grasp the big picture
Could any of you send me to the right direction? An idea on what could include all these?
It might be a good idea to start with the scriptrunner plugin. This enables you to write custom groovy scripts for workflow conditions, validators, post-functions, listeners and many more.
The advantage is that the learning curve for simple groovy scripts is not as steep as for "real" plugins. That way you can accomodate with the jira api and then when you hit the point where you can't help yourself with groovy anymore switch over to normal plugin mechanics.
The Introduction to the Atlassian Plugin SDK is actually quite good.
The get your head around try to focus on the type(s) of plugin you want to have:
customfield - calculated or not?
workflow plugins - validators, conditions
Within each plugin, find out what information you need and then see where from the API you can get that information.
Script Runner is easier to learn and it does exactly what you are asking for. A SR script can become also a JIRA plugin if you want to install it in other instances (SR plugin must be available).
Learning Script Runner helps you to understand better how to develop JIRA plugins, in any case it's not time wasting because you can easily switch between native JIRA plugins and SR (SR uses JIRA components so the main logic is still the same, it just hides most of the annoying and repetitive stuff).
You can start with this template:
https://bitbucket.org/jamieechlin/sr-scripts-plugin/overview