Updating a table in confluence wiki using Jenkins plugin - jenkins

I would like to use Jenkins to update specific cells in a table created in Wiki.
I see that i can use the "publish to confluence" plugin, but i am not sure how i can mark the place that i want to update. The plugin help is talking about token - what are those tokens?

In the plugin, "tokens" are wiki text. They can be hidden Confluence Macros or even visible text. The macros work best because they are hidden from the normal reader. I use raw text matches on our Confluence because our permissions don't allow those macros. Either one works.
I should not that my experiences are with Confluence 3.x. Confluence 4.x apparently changes a number of things that have an impact on how this plugin works.
The plugin's page has a comprehensive list with examples and differences between 3.x and 4.x:
Confluence Publisher Plugin

Related

My own html report in build summary

Previously, I used testlink. This plugin generated a nice table with the test results in the build summary view.
Now, I don't use testlink anymore, so this plugin cannot be used. But instead, I want to feed a html report (which I take care of generating) to the build summary view.
I tried HTML Publisher Plugin, but it makes a link instead of displaying in the build summary view.
Is there such a plugin that allows me to specify that a certain .html file from the workspace will be included?
Bonus question: or even a plugin that allows a .html fragment to avoid the use of i-frames?
Try using the Summary Display Plugin. It work pretty good.
The configuration is a bit tricky so I'm adding an example screenshot of my configuration.

Custom Jenkins Plugin - how can I override values loaded from older versions of the plugin?

I'm develping custom Jenkins plugin.
As part of the development I had to make some changes to the classes and fields of my custom build step.
As a result, each client that updates the plugin has to re-enter the configuration of some of the fields.
I wonder if there is a way to load the old values and map them to the new fields?
Any help will be appreciated.
Cheers,
Nadv
See Hint on retaining backward compatibility in the Jenkins wiki. It covers all relevant cases, e.g. adding/removing/renaming fields.

use Confluence-publisher-plugin in Jenkins to send build information to Wiki

I know there are some questions regarding this, but didn't get the right answer yet.
I am trying to use Confluence publisher plugin in Jenkins to send build information (Logs, artifacts...) to wikiD page. I can attach artifacts and write plain text to the wiki page. But I'm trying to update/append/prepend wiki page table with build info. I think I might be able to achieve this by using macros but not sure how to use that for data in tables??
does anyone here know how to achieve that?
Sure. I can mention how i did it. There might be different way others will do the same thing.
So, in Confluence, either create a Blank macros as mentioned on Confluence-publisher-plugin wiki and in Jenkins, use "Wiki Markup Replacements" options in plugin configuration to direct your Contents.
OR other option is what i did on mine, was to create table in the wiki and use Cell header ( |cell1||cell2|... ) as Marker Token. then select plain text option, where you enter all the contents that you want to be published in your Wiki.

How to version control the JIRA changes?

I asked the following two questions in JIRA Answers, but got no reply so far:
Question 1
Question 2
Basically my question is what's the best way to make changes in a JIRA production environment.
This will be rather general answer, but this is how I do it:
I avoid modifying JIRA production files. When I need it (e.g. mail templates), I keep them under source control along with plugin in 'deploy' directory which mimics JIRA directory structure so it is possible to grap it and deploy it with copy&paste
I frequently use javascript to decorate screens with custom behavior
Schema changes, custom fields and other meta data are all created in code
Keep everything in plugin and leverage plugin versioning system. Plugin should be able to check whether there is everything it needs and when not it should be able to upgrade incrementally.
For JIRA configuration - this is the same, plugin should check whether it has everything it needs, but you can also keep configuration changes in some excel file and have it under source control
My aproach is to have everything possible in source control and modify production files only when absolutely necessary. Do as much in code as possible.

How to enable the RTF editor in Jira

I'm new to Jira and have big problem with creating tables inside my testing plan. Using pipes, double pipes, etc. to build the table markup is really time consuming.
So, I saw here, that actually there's a RTF editor with visual table building in Confluence (which should be used in JIRA right? ) : http://confluence.atlassian.com/display/DOC/Working+with+Tables+in+the+Rich+Text+Editor
However the textareas in my Jira installation are just plain text fields and can't figure out how to turn them into the the nice RTF areas shown in the URL above...
You have to go to Admin, Field Configurations and tell JIRA to use the Wiki Renderer for fields such as Description and Environment.

Resources