#custom plugin

There is stateFileLabeler which you can use in ccnet.config to share same build label across multiple projects in CCNET like below-

"stateFileLabeller"> Project Name to pull Build Label From

But, build label will remain same, which is disadvantage,if you need incremental build label across multiple projects. You can create your own custom plugin for CCNET to do that. I have implemented like below- 1) Create C# Class Library Project and name it as sharedLabeller. Put below code in .cs file using System; using System.Collections.Generic; using System.Linq; using System.Text; using ThoughtWorks.CruiseControl.Core; using ThoughtWorks.CruiseControl.Remote; using System.IO; using Exortech.NetReflector; namespace ThoughtWorks.CruiseControl.Core.labeller {     // this is the labeller name that will be used in  ccnet.config     [ReflectorType("sharedLabeller")]     public class SharedLabeller : ILabeller     {         [ReflectorProperty("syncronisationFilePath", Required = true)]         public string SyncronisationFilePath { get; set; }         #region ILabeller Members         public string Generate(IIntegrationResult previousResult)         {             if (ShouldIncrementLabel(previousResult))                 return IncrementLabel();             if (previousResult.Status == IntegrationStatus.Unknown)                 return "0";             return previousResult.Label;         }         public void Run(IIntegrationResult result)         {             result.Label = Generate(result);         }         #endregion         private string IncrementLabel()         {             if (!File.Exists(SyncronisationFilePath))                 return "0";             using (FileStream fileStream = File.Open(SyncronisationFilePath,                  FileMode.OpenOrCreate,                  FileAccess.ReadWrite,                  FileShare.None))             {                 // read last build number from file                 var bytes = new byte[fileStream.Length];                 fileStream.Read(bytes, 0, bytes.Length);                 string rawBuildNumber = Encoding.ASCII.GetString(bytes);                 // parse last build number                 int previousBuildNumber = int.Parse(rawBuildNumber);                 int newBuildNumber = previousBuildNumber + 1;                 // increment build number and write back to file                 bytes = Encoding.ASCII.GetBytes(newBuildNumber.ToString());                 fileStream.Seek(0, SeekOrigin.Begin);                 fileStream.Write(bytes, 0, bytes.Length);                 return newBuildNumber.ToString();             }         }  private static bool ShouldIncrementLabel(IIntegrationResult previousResult)  {      return (previousResult.Status == IntegrationStatus.Success || previousResult.Status == IntegrationStatus.Unknown);  }     } }

2) Change properties of the project to output dll and name it like- ccnet.sharedLabeller.plugin 

3) Build solution and copy in \server folder

4) Edit ccnet.config and ccnet.exe.config for Plugin location value and give path to the folder where you placed Plugin.

5) Create some file like buildnumber.txt in \server folder and edit ccnet.config for your project where to want to share your label incrementally-

        E:\Program Files\CruiseControl.NET\server\buildnumber.txt

    Whenever build is triggered, it will increment label in buildnumber.txt and use in the project where it is being called.

During the development of CityZen, I wanted to take a small break and work on a smaller plugin to provide a new feature. After a little over a day’s work, I’m proud to announce our newest custom plugin.

It’s called TopicOfTheDay, and works like you’d expect. Every day when the server starts up, the plugin pulls a random topic from the config. Then when players log in, it shows them the topic after a short delay.

These topics are short discussion questions to help break the ice and get people chatting. We will be adding lots of them in the coming days, so make sure to take advantage of this plugin to get to know your fellow players (this is a community server, after all).

Add Capability of Custom Plugin to a Role

To add new Capability of a custom made plugin in WordPress to a specific Role.

function add_theme_caps() { // gets the author role $role = get_role('editor'); // This only works, because it accesses the class instance. // would allow the author to edit others' posts for current theme only // just mention your plugin filename like I have edit_events.php as my plugin $role->add_cap('edit_events');…

A few months back when we migrated one of our apps from Grails 1.3.7 to 2.1.1 we lost the ability to dive into the code of our custom plugins while debugging. All we saw was the compiled code, with the ability to attach source but not really knowing where to attach it from because eclipse wouldn't accept the code in the workspace. Since we were strapped for time back then we didn't get a chance to figure out how to debug the code inside the plugins so we made do with lots of debug logging.

Today when I ran into the same issue while working on a new plugin, I didn't have the patience to write all the debug statements. I googled and found nothing! The stackoverflew but nothing came out of it, too. So I went back to the trial and error method and found the solution to that particular pain. Here's a step-by-step guide for anyone who wants to step-in to their custom plugin code:

If you have any reference to the plugin in the main app's BuildConfig, comment it out. (I am talking about any config that looks like grails.plugin.location.myplugin = "../myplugin"

Next, package your plugin.

Install it on your main project the old school way, using the install-plugin command pointing to the zip file created by the package plugin in step 2. You should now have a new entry in your application.properties file.

Run your app and confirm that all's wired up. The debugging still won't work.

Stop the server and uncomment the configuration in BuildConfig or add that config (refer to bullet 1).

And that should do the trick. Did it for me.

When you're done building the plugin you can uninstall the plugin and just leave the config in the BuildConfig file.