I would like to add extra columns to the build history sidebar that can be modified by user (comments,etc..).
Has anyone did something similar? or any suggestions how can it done easily?
You cannot add columns to the build history without digging deeper into the Jenkins-internal layout engine.
The simplest solution to achieve what you want is to use the "Edit Build Information" menu item for a build. Users can add information there, and it's also possible to add HTML code with tables etc there, which can then look nicely in the build history.
It's not as interactive as what you're looking for, though, and it requires some discipline from your users to avoid that they destroy the build history format completely.
If you only need comments for failed builds, then the Claim plugin is a nice solution.
Related
Is there a way to shorten the text which is shown on the Maven plugin documentation Page under the point Usage?
I wrote a long Mojo-description and i do not wan't to show it all on the first usage page.
So is there a way to add something like a "Read more" link or simple shorten the displayed text ?
Update:
I added a table to the class-description and I do not want to show this table on the Usage-Page.
I would like to ask the community if there is any way to create a GUI menu where the options will populate itself based on number of files that are saved in a folder directory. The user will then have two options whereby he can choose to generate a status or a dashboard option. After he chooses the report that he wish to generate, another menu will appear to ask him which document he want to select. This is where the menu would check the folder and generate the options based on number of files in the folder. For example, there could be doc1 and doc2 in the folder. Then the menu will generate 2 options. 1. Select doc1. 2. Select doc2. Then after the user inserted another doc3 into the folder. The menu will add another 3. Select doc3 without having the user to change the code. Is there a way to do this? Thanks.
This makes no sense. A .bat file is by definition something that does not have a GUI.
Also you really have provided the vaguest information for something seemingly large, and there appears to be no reason why you've also tagged this as excel and exe.
Since your .bat file could launch a particular Excel file, you could go that way, putting all the dashboard info in the spreadsheet. Would require some VBA code to make it as interactive as it sounds like you want, but that's entirely possible.
I'm not aware of any way that a .bat file can create a GUI on its own, although I may be missing something. Since the .bat file can run almost anything, it can be a starting point, but the heavy lifting would be done in something else.
Another approach would be to look at AutoHotkey, which can give you a GUI and a fair bit of processing power & interactivity all within the one script. The URL is http://www.autohotkey.com/ and that site has a tremendous amount of examples and help available. Also some AHK questions here on Stack Overflow from time to time.
Either way you go, it's a fairly large project. Good luck!
Is there any way to make force global save actions for a project?
My team uses a specified formatter and a save actions. Formatting all code is easy to be done, but later on when someone does edit in some file, VCS diff goes mad - save actions come into play and changing 1 line results in many lines edited.
"Format edited lines instead of Format all lines." is a know workaround, but I'd rather not use it.
My team uses a formatter and save actions too. I couldn't find a way to force global save actions in a whole project and VCS diff really gets everyone mad after some change because of the format change...
What we did was ask everyone to commit their changes to svn and use the formatter an save actions. Then, I changed the format of all files in the project and comitted it. Everyone downloaded again the project, with format changes already done, and continued working without madness :)
You want to format your whole source code at once right? Then right-click your project and select Source -> Format.
To run the save actions you have to select your packages right-click and select Source -> Clean Up...
#user714965 Using Clean Up as save actions seemed the best, till I found this this plugin that does exactly what I want - applies save actions.
http://marketplace.eclipse.org/sites/default/files/styles/ds_solution_screenshot/public/Screen%20Shot%202011-10-10%20at%2011.25.52%20PM.png
http://marketplace.eclipse.org/content/save-actions-extensions#.U-ynLfl_tCZ
I have a RCP app which I want to "brand", i.e. create a proper text for the about box with build id. Simple stuff. Unfortunately this wasn't as easy as I had hoped, and now I am stuck.
My RCP project is launched from a project configuration and is not deployed as plugins through features.
I have tried entering stuff directly in the product configuration -> branding tab, but when I do, the input isn't formatted, meaning I have no newlines and no possibility to externalize strings like I want to. I have also tried creating about.ini, about.properties and about.mappings in an attempt to use the %< property >, but still no luck. The about box is a standard org.eclipse.ui.help.aboutAction.
Every tutorial on the net says different things, so now I feel pretty confused. I have also tried to replicate what is done with branding in the Eclipse repos, without any luck.
Does anyone know what I'm doing wrong?
What is needed is this line in the MANIFEST.MF file:
Bundle-Localization: plugin
guido's comment on my question sheds some light on what the different files are for as well.
I have a Java project in a SVN repository, with a bunch of .java files, each of those files has a licence agreement flower box at the top of the file (I have customers which have licenced the source as well as running the product).
Is there a good way to be able to modify / maintain the licence text in one place rather than having to update all the source files manually if it changes?
Looking at some similar (but not identical) questions it seems like SVN does not have this functionality out of the box - what other approaches would be most suitable?
Edit: Ideally the solution would act like the SVN keywords (Id, Author etc.) rather than being a build-time solution. The customer has access to the SVN repository too, so it would be ideal if the licence text was present in the SVN version of the file. I know SVN has commit triggers - what's a simple way to implement that?
Edit 2: Looking at the SVN hooks it doesn't look like what I'd like to do is possible. I guess build process that can be run when the text changes is ok - since it won't change too often.
Modify the source files that need to contain the text of the license to contain some token instead, and then move the license text to a single file that's kept in subversion. Finally, as part of your build process, add a step that substitutes the text of the license for the token. At my job, I do something along these lines using a combination of sed and make. You could then execute this single step before distributing the source to your customers.
ANT can do the substitution easily. Look into the <copy> target.