I know that once I install the Pipeline plugin (workflow-aggregator-plugin), this action becomes available. However there are about 30+ different plugins that get added with this action and for the life of me, I search all over github (even tried "Workspace" (or "Workspaces" for multibranch pipelines) because this is what I figured out would be returned from the action' getDisplayName() for that action in the side panel. So I have two questions:
what is the plugin and where is it implemented?
how could I have found this out without having to ask on stackoverflow?
Thanks a lot.
Related
We're using octo.exe to create releases. It starts suddenly giving error saying can't find project. I checked the api/projects and that's true, it is not in the returned json response. But when I look at the dashboard I can see the project. The only thing I did was cloning another project from this one earlier. The cloned project is working fine but not the original project.
It exists in dashboard (web gui) but not in api (hence octa.exe can't find project)
Looks like api is caching the projects. The new projects that I created via GUI not available in api.
Thanks,
I have had the same issue yesterday. It turns out to be something interesting. I believe that your project is still there properly set, but the total number of projects that you have become more than the listed ones in the API, and that's why the Octo.exe couldn't see it anymore.
I have explained here, how I managed to fix that issue quickly.
This is due to how pagination is implemented in Octopus (pretty poorly if you ask me). But you can override it. add this to the URL (at the end).
'?skip=0&take=2147483647'
alternatively, you can watch the json returned, if you find the links.Page.Next property you can use that link to get next page of the api response.
This is a continuation of a question I asked a few days ago regarding a designer connection for Domino OSGI dev and testing.
In eclipse, I do have the "debugging plug-in" installed (as mentioned by stwissel), and I am fairy certain that it is configured properly.
In a second attempt, I tried to export my plug-in in an update site.
1. import plug-in to feature
2. import feature to update site
3. build update site
I first tried to install using My Widgets in the notes sidebar. I did not get the thing to run with that so, then went into designer and installed it there directly, also nothing.
current stand
I built the update site and deployed using an nsf Update Site as a widget. I use this for openNTF Domino API, the ExtLibs -- it is comfortable and I like it.
I can verify that the feature is available in the application Management window of designer.
3 I expect to see those libraries in the xsp.properties page generation tab, but do not.
questions
1. Am I missing something?
2. Must I add some sort of class/code/flag in order to choose this library/plug-in in designer?
3. How can I best verify that the plug in and not just the feature is installed?
if your XspLibrary is not a 'global' one you probably won't see the activator run until the first nsf that uses it activates it.
seeing as you can't select it in an nsf this is probably why no nsf is ever activating it
can I ask have you correctly defined the library as an extension of com.ibm.commons.Extensions
as type
com.ibm.xsp.Library
if you don't define the extension you will not see it in the list of libraries.
also you must make sure you set the plugin settings to export the XspLibrary class (or package of the class) otherwise designer can't use the class
see this article on the domino designer wiki for an overview of necessary steps to correctly set up the XspLibrary plugin. the manifest.mf / plugin.xml settings are important.
another thing to double check, is to inspect the actual built plugin jar, using something like 7zip. you can open it up like a zip and have a look to make sure the .class files are actually included in the jar. if your build settings are incorrect it may not include them in the jar properly. also make sure the manifest.mf and plugin.xml are in there properly
EDIT from Greg
This should be the link for a non-mobile user
When you setup the debug plugin, it should create an entry in the workspace directory of the Notes client and Domino server (I think down in the RCP directory). This entry points back to the Eclipse workspace. So you don't need to deploy the plug-in. You also should see a warning when loading Notes ( with rparams -console) or Domino on the console about the debug.
Also what I found: auto deployment via Widget works when the update site sits on a server via http or nrpc. It doesn't when it is specified as file:/// so I run a Apache http on local (I need it for other stuff too, so no big deal for me).
I'll check the exact settings when I get back to my Dev workstation
You can identify if a plugin is installed via Help > About IBM Domino Designer, then clicking on the Plug-in Details button in the dialog.
Help > Support > View Log and View Trace should give more details. Trace is more detailed and allows you to write content, as we do for the OpenNTF Domino API. It may allow you to see how far through the code it's going.
That first message is in the XspLibrary class, in the constructor, just using a sysout
/**
* Constructor
*/
public XspLibrary() {
System.out.println("Loading org.openntf.domino.xsp library");
}
Hopefully that should help you see where it's failing.
Folks,
I've done a fair amount of research on this topic, and still haven't found any answers so far. I'm trying to achieve the same goals as demonstrated by #delaney05 in his post at Jenkins on OS X: xcodebuild gives Code Sign error but I seem to be having some problems that he didn't (or, at least that he didn't mention).
Specifically, I can get the developer profiles exported via XCode (using the standard GUI methods), but the security tool doesn't seem to allow me to import those via the CLI to the login.keychain for the Jenkins user. Of course, the Jenkins user is not a "real" user, and so you can't log in and do this using the GUI methods.
I tried posting an update to #edelaney05's article on this subject, but apparently the moderators want me to ask a separate question instead.
At this point, I'm seriously considering creating a real Jenkins user, then installing the app version of Jenkins as kindly provided by #sti a.k.a., Sami Tikka. At least this way I would be able to use all the Mac-standard GUI methods of exporting and importing developer profiles, .mobileprovision files, and other keys, certificates, etc.... Of course, doing that will make it more difficult to build out the cluster of Jenkins servers that we're going to need going forward, but I'm wondering if that really is the best solution right now.
Did I do anything stupid? Did I miss anything? Is there any additional documentation you'd like to see showing all the steps I've done through? Thanks!
BTW, I did try to post a version that fully referenced all the pages with proper links, but as a "new user" I apparently don't have a high enough reputation score to post a question with more than two links. ;-(
Suggest you try building your Xcode project via the command-line, and once this is working you can try setting the same environment in Jenkins.
Note that the user that Jenkins uses for running its commands is not related to the Jenkins-Login, but it is the OS-X user that had started the Jenkins application.
This user is probably 'daemon', which differs from the one you use for your regular work with Xcode.
(can confirm this by running "id" as the command in the Jenkins Job)
Good luck!
My team uses the Radiator View plugin for Jenkins for fast feedback on the build status of a few different projects. One thing we discussed that would be helpful is if the SVN revision number were included in this view. After only a quick Google search, I haven't found a clear answer on whether this plugin is configurable or not; does anyone know if there's a straightforward way to add this information?
I dont think there are customizable figures there but what you can do is, pull down the source and get the revsion numbers for all the failing builds, you will have to write the code yourself, but from what I can see there is no way of doing this with the configuration options.
What you might want to try if you just need to get that information is the recent changes on the build page of the recently broken build.
Goodluck.
Can I ask why it would be helpful to have the svn revision number on display? As far as I understand it, a build radiator is supposed to 'radiate' meaningful information into the room. The svn number is fairly meaningless unless you can look up the number in the repository, in which case you could have just looked up the revision number on Jenkins anyway.
I'm just guessing, and do correct me if I'm wrong, but I suspect that your real desire is to have some way of quickly working out who might be responsible for a failing build. If this is the case, then processing check-in comments and displaying pictures of the users involved is a far more effective way of getting developers to react to failing builds. I've experienced this first hand at my company.
With this in mind, I have developed a standalone build radiator webapp that talks to Jenkins over its REST API. CI-Eye is trivial to set up, and will probably give you better results in the workplace than the Radiator View plug-in. Give it a try, and let me know what you think -- I'm quite actively improving it, and welcome any feedback.
CI-Eye is free and open source -- see the CI-Eye wiki for more details.
There are no options displayed when I'm looking at a plugin with the plugin manager. Where there should be a menu for basic and advance options is just white space. How can I start trouble shooting this problem? Other installed extensions work fine and hours of searching about plugin options make me think this is a peculiar error. This is what my menu looks like http://i.stack.imgur.com/s2S4K.png
The plugin you are using is not written for Joomla 1.6, the XML manifest needs to be updated at the very least. The plugin itself may also need to be rewritten. I would start withe the XML file first, you can find details on the changes that need to be made here - http://www.theartofjoomla.com/home/9-developer/112-upgrading-a-plugin-to-joomla-16.html