Promoted Builds Plugin

Plugin Information

Plugin ID promoted-builds
Latest Release 2.4-h-2
Latest Release Date Oct 7, 2013
Sources Github
Support Eclipse Hudson Forum
Issue Tracking Eclipse Bugzilla

This plugin allows you to distinguish good builds from bad builds by introducing the notion of 'promotion'. Put simply, a promoted build is a successful build that passed additional criteria (such as more comprehensive tests that are set up as downstream jobs.) The typical situation in which you use promotion is where you have multiple 'test' jobs hooked up as downstream jobs of a 'build' job. You'll then configure the build job so that the build gets promoted when all the test jobs passed successfully. This allows you to keep the build job run fast (so that developers get faster feedback when a build fails), and you can still distinguish builds that are good from builds that compiled but had runtime problems.

Another variation of this usage is to manually promote builds (based on instinct or something else that runs outside Hudson.) Promoted builds will get a star in the build history view, and it can be then picked up by other teams, deployed to the staging area, etc., as those builds have passed additional quality criteria. In more complicated scenarios, one can set up multiple levels of promotions. This fits nicely in an environment where there are multiple stages of testings (for example, QA testing, acceptance testing, staging, and production.)

Promotion Action

When a build is promoted, you can have Hudson perform some actions (such as running a shell script, triggering other jobs, etc. — or in Hudson lingo, you can run build steps.) This is useful for example to copy the promoted build to somewhere else, deploy it to your QA server. You can also define it as a separate job and then have the promotion action trigger that job.

Do not rely on files in the workspace
The promotion action uses the workspace of the job as the current directory (and as such the execution of the promotion action is mutually exclusive from any on-going builds of the job.) But by the time promotion runs, this workspace can contain files from builds that are totally unrelated from the build being promoted.

To access the artifacts, use the Copy Artifact Plugin and choose the permalink.

Usage

TODO: talk about a typical set up, the configuration, manual promotion, PROMOTED_URL.

Changelog

Version 1.11 (Jan 31 2011)
  • Promote a build even if downstream build is unstable. (issue #8626)
  • Promote Builds Plugin can use custom workspace. (issue #8547)
  • Invalid characters in Promotion name causes error. (issue #7972)
  • Fix promotion permlinks. (issue #8367)
  • Allow promotion actions to be reordered. (issue #8548)
Version 1.10 (Sep 28 2010)
  • Promotion processes are now recognized as permalinks.
Version 1.9 (Jun 9 2010)
  • If fingerprints are not available, use the upstream/downstream triggering information to determine the relationship as a fallback.
Version 1.8 (Jun 5 2010)
  • Add the possibility to choose a different color for the star icon, to be able to differenciate the various promotion processes
Version 1.7 (Mar 29 2010)
  • Use JDK configured for project when running promotions (issue #3526)
  • Select node for running promotions from label configured for project (issue #4089) (does not yet run on exact node where promoted build ran, unless project is tied to a single node)
  • Show most-recent first in promotion history tables (issue #6073)
Version 1.6 (Dec 30 2009)
Version 1.5 (Aug 17 2009)
  • Updated to work with Hudson 1.320
Version 1.4 (May 21 2009)
  • Re-doing a release as 1.3 had never shown up in the update center.
Version 1.3 (May 11 2009)
  • Expose environment variable 'PROMOTED_URL' that points to the URL of the build that's being promoted (report)
  • Internal modernization.
Version 1.2 (Mar 25 2009)
  • Updated to work with the current Hudson
Version 1.1 (Feb 20 2009)
  • Fixed a problem where Hudson may issue the same warning multiple times for the same configuration problem (report)
  • SVN Tagging is now a permitted promotion step
  • Promotion now fails if any actions are not performed (issue #2597)
  • Improved logging of promotion build process so users can see what succeeded and what failed
  • Promotion action to build another project no longer does nothing (issue #1765)
  • Added "Promotion History" pane to the PromotedBuildAction page (issue #2794)
  • Fixed 404 for last failed link while promotion build occuring (issue #2578)

Labels:

plugin-misc plugin-misc Delete
plugin-ui plugin-ui Delete
tier2-plugin tier2-plugin Delete
plugin-builder plugin-builder Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.
  1. May 19, 2008

    InstallGal says:

    I am using promotion to promote a compilation project and build an installer pro...

    I am using promotion to promote a compilation project and build an installer project once the compilation project is promoted (UTC promotion criteria).  Is there a way to sync the upstream (compilation) project build number with the action project build number?  The have to be the same b/c some of the c++ header files and property files contain build number info.

    Thanks. 

    1. Apr 15, 2010

      Iftach Bar says:

      I don't know if it's still relevant, but I needed to use build number and the jo...

      I don't know if it's still relevant, but I needed to use build number and the job name of the original job that I'm promoting.

      I created a small shell script that extracts it from a weird place in hudson home directory.

      JOB_NAME=`echo $JOB_NAME | sed s/promotion/promotions/`
      OUTPUT=`grep Promoting "$HUDSON_HOME/jobs/$JOB_NAME/builds/$BUILD_NUMBER/log"`
      # The output will be something like: Promoting myJob #456
      ORIG_JOB_NAME=`echo $OUTPUT | awk '{print $2}'`
      BUILD_NUMBER=`echo $OUTPUT | awk '{print $3}' | cut -b 2-`
      

      This will probably won't work if on slaves and will have to change somehow, but it works really great for me when I only have one master box.

      It will probably be a good idea just to give some access to a variables like $ORIG_JOB_NAME and $ORIG_BUILD_NUMBER from the plug-in code.

  2. Jun 19, 2008

    Stephen Finley says:

    Is there a way to set who has the right to promote a build? I am using it with t...

    Is there a way to set who has the right to promote a build? I am using it with the only when manually approved option. I am also using hudson matrix based security. It looks like the only way someone can promote is if they have administer privileges.

    Thanks

  3. Feb 10, 2009

    Alex Carr says:

    I am attempting to configure a Hudson Job to use the Build Promotion Plugin. I w...

    I am attempting to configure a Hudson Job to use the Build Promotion Plugin. I want to manually promote a build.  The onscreen help indicates that selecting the criteria "Only when manually approved" provides a push button method to manually promote the build. I have been unable to find the button or link called "force promotion" once I have enable this criteria.

     Can anyone tell me if this feature is implemented and if so where do I find the "force promotion" button.
     Thank you

    1. Apr 22, 2009

      Peter Centgraf says:

      To find the button: 1. Go to a project that has a promotion process defined. 2...

      To find the button:

      1. Go to a project that has a promotion process defined.

      2. Make sure that a build has occurred after the promotion process was defined.  (If not, trigger a build now.)

      3. Go to the page for a specific build (one that happened after the promotion process was defined).

      4. Click on the "Promotion Status" link in the menu on the left.

      5. Under the section for the specific promotion process, there will be a button on the far right.

  4. Feb 11, 2009

    Steve Leach says:

    It would be great if the promotion actions included the ability to run a target ...

    It would be great if the promotion actions included the ability to run a target from the project's ant script.  This would let me have a "build" target and a "promote" target, for example, with the build target running automatically whenever there is a code change, and the "promote" target run manually.

  5. Feb 20, 2009

    Shibu Gope says:

    This plugin fails for me with Hudson 1.284 when trying to configure a promotion....

    This plugin fails for me with Hudson 1.284 when trying to configure a promotion.  Below is the stack trace snippet:

    Failed to parse form data. Please report this probelm as a bug JSON=
    {"..."}
    net.sf.json.JSONException: null object at net.sf.json.JSONObject.verifyIsNull(JSONObject.java:2498) at net.sf.json.JSONObject.getString(JSONObject.java:1842) at hudson.plugins.promoted_builds.JobPropertyImpl.(JobPropertyImpl.java:67) at hudson.plugins.promoted_builds.JobPropertyImpl.(JobPropertyImpl.java:37) at

     

  6. Feb 20, 2009

    Shibu Gope says:

    Problem still exist with 1.285

    Problem still exist with 1.285

  7. Feb 21, 2009

    Shibu Gope says:

    Testing

    Testing

  8. Apr 30, 2009

    James Bengeyfield says:

    Great plugin but have found a couple of issues - lt will not allow me to add m...

    Great plugin but have found a couple of issues -

    1. lt will not allow me to add more than one promotion process at a time, I get the following error - Failed to parse form data. Please report this probelm as a bug followed by a a JSON string
    2. When adding a new promotion process, the newly added process will not allow me to add any actions until the configuration has been saved and reloaded.
    3. When copying an existing build configuration, the promotion section is not copied.

    Any assistance would be gratefully received.

    1. Jul 24, 2009

      Peter Centgraf says:

      I second the request to copy existing promotions when copying a job.  This ...

      I second the request to copy existing promotions when copying a job.  This would be handy when we move from trunk to a branch during the endgame of a release.

  9. May 14, 2009

    Mahesh Narayanan says:

    Where can I find Version 1.3? I see the changelog, but I can't find it on the do...

    Where can I find Version 1.3? I see the changelog, but I can't find it on the downloads page.

  10. Jun 02, 2009

    Ryan Ramage says:

    I am trying to get a build promoted using this tool. One question I have is arou...

    I am trying to get a build promoted using this tool. One question I have is around the fingerprints of the artifacts. Does the set of artifacts have to be equivalent on both projects (the upstream and downstream)? Or can it be an intersection of the two sets of artifacts?

  11. Jul 15, 2009

    Greg says:

    There is a problem with this plugin when trying to promote a build with the "Inv...

    There is a problem with this plugin when trying to promote a build with the "Invoke top-level Maven targets" action on a build that is tied to a specific node.  The promotion process is not obeying the fact that the project build was tied to a specific node, so when it tries to invoke the maven target, it does so on a different node.  This node obviously does not have the project directory checked out there, so it fails with a "no such file or directory" error.

  12. Aug 18, 2009

    Daniel Lindner says:

    Right now, the new version 1.5 isn't available via hudson's plugin manager or th...

    Right now, the new version 1.5 isn't available via hudson's plugin manager or the download area of the hudson site. If you try to run hudson 1.320 with the promoted-builds plugin, you get HTTP 500 errors because of some tags using old bindings. I guess the publishing process didn't suceed for the new version?

  13. Sep 30, 2009

    cava says:

    I have a problem, because all the parameters I set for the job are null when I p...

    I have a problem, because all the parameters I set for the job are null when I promote a build with a promotion that re-use these paremters.

  14. Dec 14, 2009

    Raffi says:

    I would love to have the promoted builds available with a permanent URL just lik...

    I would love to have the promoted builds available with a permanent URL just like the permalinks for the latest successful, latest stable build a.s.o. 

    e.g. myjob/qaBuild, myjob/qaApproved ...

    Maybe I just didn't find it in the documentation or is it not yet implemented?

  15. Jan 12, 2010

    Nicholas Hahn says:

    Great plugin - my department has been using with this Hudson for almost a year n...

    Great plugin - my department has been using with this Hudson for almost a year now.  Anyways, with my department growing it now makes sense for us to use the mutli-configuration job.  Is there any chance support for the job can be added?

  16. Jan 13, 2010

    Haggai Philip Zagury says:

    A great feature would be to prompt the user for a pre-defined password (which wi...

    A great feature would be to prompt the user for a pre-defined password (which will be configurable in the promotion build step) in order to release a version.

  17. Jan 18, 2010

    Gilles QUERRET says:

    Version 1.6 changelog says that there's a fix for running on slave node. However...

    Version 1.6 changelog says that there's a fix for running on slave node. However I'm still having a problem when manually triggering a promotion. This project is bound to a specific node, but the Ant task executed by the promotion is always executed on the master node (and failing because it doesn't find the workspace). Is this the standard behavior, or is there still a bug ?

    1. Jan 29, 2010

      Gilles QUERRET says:

      In fact, I just had to recreate the job to make it work.

      In fact, I just had to recreate the job to make it work.

  18. Feb 09, 2010

    Jim Hendricks says:

    This is a great addon. I am now using it and so far it has caught on well with m...

    This is a great addon. I am now using it and so far it has caught on well with my users to the point I now have a new requirement. I need to publish the promoted build artifact to the scp server. I tried a few tests and it moves just the artifacts in the current build even though the user promotes a build 2 or 3 generations earlier.

    How do I set it up to pull the correct build generation?

    Thanks

    1. Feb 15, 2010

      Adam Burnett says:

      I second this request. It would be extremely helpful to be able to deploy an arc...

      I second this request. It would be extremely helpful to be able to deploy an archived artifact.

    2. Mar 02, 2010

      J. Longman says:

      I was looking at a hack to do this: execute a shell: rm -fr hudson-promotion ...

      I was looking at a hack to do this:

      • execute a shell:
        rm -fr hudson-promotion
        mkdir -p hudson-promotion
        cd hudson-promotion
        wget --accept tgz,pkg --no-directories --restrict-file-names=windows --recursive --level 1 -erobots=off --relative ${PROMOTED_URL}artifact/
        
        • our targets end in tgz or pkg
        • --restrict-file-names and --no-directories were trying to combat wget barfing on *view* and *zip*. --no-directories may be enough.
      • run the scp plugin to copy from the current (random) slaves workspace to the official repository
      • delete the hudson-promotion directory when done promotion

      Unfortunately --relative should work but doesn't and IIRC it also grabs the next and previous builds.

      This plugin also doesn't work for matrix jobs as near as I can tell.

      1. Nov 11, 2010

        Patrick Renaud says:

        I have exactly the same need. Have you managed to get the above working?

        I have exactly the same need. Have you managed to get the above working?

  19. Mar 23, 2010

    Nelms says:

    Our company is currently testing Hudson for our SW Development and Iam currently...

    Our company is currently testing Hudson for our SW Development and Iam currently testing this feature for our needs. One thing i can suggest for the improvement of this feature is that when doing a manual promotion, it would be great if the one who perform the promotion is required to put a note or something wherein he/she can justify why this particular build pass this level of promotion. A text area will do(to put test result or assessment coverage ).

  20. Apr 28, 2010

    mmorizot says:

    Hi, I am currenlty implementing a promotion status using this plugin, allong wi...

    Hi,

    I am currenlty implementing a promotion status using this plugin, allong with artifactory 2.2.1 (excellent tool BTW) + power pack and the hudson artifactory plugin .

    Here after is a shell script that allows me to assign a promotion value (aka  a property value for artifactory).

    It uses Iftach Bar's script exerp, a few messages above.

     JOB_NAME=`echo $JOB_NAME | sed s/promotion/promotions/`
    OUTPUT=`grep Promoting  "$HUDSON_HOME/jobs/$JOB_NAME/builds/$BUILD_NUMBER/log"`
    # The output will be something like: Promoting myJob #456
    ORIG_JOB_NAME=`echo $OUTPUT | awk '{print $2}'`
    BUILD_NUMBER=`echo $OUTPUT \| awk '{print $3}' \| cut \-b 2-`
    echo $BUILD_NUMBER
    rm -f myfile
    
    # retrieve list of all deployed artifacts that are  part of the build (could use the JSON interface yet, but need to master  it first)
    grep -a "Deploying artifact:"  "$HUDSON_HOME/jobs/$ORIG_JOB_NAME/builds/$BUILD_NUMBER/log" | cut -d:  -f3 > myfile
    while read f
    do
     rm -f properties
    #  retrieve all properties from the artifact
     curl -X GET -u  toto:toto42 "http:${f}:properties" >>properties
    
    #delete  closing </properties>
     sed -i '/<\/properties>/d'  ./properties
    
    # delete previous promotion status if already exist
      sed -i '/InternalReleasePromotion.CTA/d' ./properties
    
    
    #  insert my promotion status
    
    
     echo  "<InternalReleasePromotion.CTA>OK</InternalReleasePromotion.CTA>"  >> properties
    
    #add the closing properties
     echo  "</properties>" >> properties
    
    #upload back to  artifactory
     curl -X PUT -u toto:toto42 --data-binary @properties  "http:${f}:properties"
    done < myfile
    echo  "***********LIST**************"
    
  21. May 14, 2010

    Andrew Stevens says:

    I have two projects setup: trunk and test. Trunk, upon a successful build, kicks...

    I have two projects setup: trunk and test. Trunk, upon a successful build, kicks off test. Trunk has test as its automatic build promotion criteria ( "When the following downstream projects build successfully" --> test ).

    But my trunk project never gets promoted. The kickoff works fine and both projects build successfuly, so I am not sure what is wrong.

    Thanks

  22. May 25, 2010

    Peter Kahn says:

    What do you think of this approach? is this replicating something that's alread...

    What do you think of this approach? is this replicating something that's already done?

    I'm planning to add some complex promotion tasks and I was thinking having a gradle promotion helper that would allow my hudson builds to be standardized and allow for customization of promotion to be stored in source control.

    Each project would have a promotion control file which would store the following:

    • types of promotion (local, dev, qa, prod)
    • actions associated (update properties files in the artifact package, deploy artifact, start integration test jobs, update confluence pages)

    Each time I built one included artifact would be a promotion-status file that could contain

    • current promotion level
    • history of promotion changes (date/time and user – if I can figure that out)
    • source location (repos-path and revision)

    When hudson promotion was enacted the script would locate the artifact (the war file), the promotion-status file, and the promotion-control file and would handle the necessary operations.

    The promotion system would be versioned and stored in source control. The promotion tasks would be centralized in a releng-repository so I'd have centralized control with simple hudson builds but still allow customization per build.

  23. Jun 30, 2010

    Nicholas Kulikov says:

    Is there a way to remove promotion mark from build?

    Is there a way to remove promotion mark from build?

  24. Jul 01, 2010

    Adam Myatt says:

    I much prefer this Promoted Build plugin to the "Promoted Builds Simple" plugin....

    I much prefer this Promoted Build plugin to the "Promoted Builds Simple" plugin. However, the "Promoted Builds Simple" plugin uses a BuildSelector in its PromotedBuildsSimplePlugin class that does this:

    @Extension public static Descriptor initBuildSelector() {
    // Add BuildSelector extension if Copy Artifact plugin is present
    try { 
        Class.forName("hudson.plugins.copyartifact.BuildSelector");
        return PromotedBuildSelector.DESCRIPTOR;
    }

    catch (ClassNotFoundException ignore) {
    return null;
    }
    }

     and defines PromotedBuildSelector which uses an action. Based on my limited knowledge this seems to make the builds promoted by the "Promoted Builds Simple" plugin available to the "Copy Artifact" plugin. Can a simple extension point be added to this Promoted Builds plugin to enable the builds promoted by it to be available to the "Copy Artifact" plugin. This would be a very valuable feature to this plugin, much like it is to the "Promoted Builds Simple" plugin. 

  25. Jul 18, 2010

    Haggai Philip Zagury says:

    Having a serious set-back in this plug-in we have added an automatic promotion t...

    Having a serious set-back in this plug-in we have added an automatic promotion to deploy artifacts upon a manual promotion of a a successful build - we get(see below)

    1. this used to work (like a charm I may add)
    2. If I use the built in "redploy artifacts buttom" and re run the promotion it works !!

    Any ideas?

    Return code is: 401
    	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:94)
    	at hudson.maven.reporters.MavenArtifactRecord.deploy(MavenArtifactRecord.java:119)
    	at hudson.maven.reporters.MavenAggregatedArtifactRecord.deploy(MavenAggregatedArtifactRecord.java:79)
    	at hudson.maven.RedeployPublisher.perform(RedeployPublisher.java:109)
    	at hudson.plugins.promoted_builds.Promotion$RunnerImpl.build(Promotion.java:124)
    	at hudson.plugins.promoted_builds.Promotion$RunnerImpl.doRun(Promotion.java:103)
    	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
    	at hudson.model.Run.run(Run.java:1257)
    	at hudson.plugins.promoted_builds.Promotion.run(Promotion.java:75)
    	at hudson.model.ResourceController.execute(ResourceController.java:88)
    	at hudson.model.Executor.run(Executor.java:127)
    Caused by: org.apache.maven.wagon.TransferFailedException: Failed to transfer file: http://nexus-host.com/content/repositories/my-releases/com/myproj/adapters/adapters-asdasd/1.1_b80126/adapters-netscaler-1.1_b80126.pom. Return code is: 401
    	at org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:172)
    	at org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:244)
    	at org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:160)
    	at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
    	... 10 more
    build hudson.plugins.promoted_builds.tasks.RedeployBatchTaskPublisher@e0898e FAILURE
    
  26. Sep 23, 2010

    Ross L. Owen says:

    I am wanting to modify the promoted-builds plugin to incorporate security by eac...

    I am wanting to modify the promoted-builds plugin to incorporate security by each individual promotion item.

    I am new to plug-in development, and jelly. I can sort of follow along with it, but am hoping someone on here can provide some guidance or documentation to look at.

    in the jelly code (resources/hudson.plugins.promoted_builds/JobPrompertyImpl/config.jelly) I was wanting to add this as a tag, but not sure if I'm even going in the right direction:

    <f:entry title="Security">
        <f:descriptorList targetType="${descriptor.securityUserType}" descriptors="${descriptor.getApplicableUsers(it)}" />
    </f:entry>
    

    I'm hoping to pull the users from the project security where the users selected under Run | Update will display in the individual promotion item to be selected as users approved to manually execute the promotion.

    Any help would be greatly appreciated.

  27. Oct 15, 2010

    Graeme English says:

    I have a job which kicks off two downstream jobs. I'm using this plugin to promo...

    I have a job which kicks off two downstream jobs. I'm using this plugin to promote the build once the downstream jobs complete and copy the resulting artifacts. I then have another promotion step which archives those artifacts however I can seem to reach those archived artifacts through the web ui (other than going to the downstream projects themselves). I can see the achived artifacts on the filesystem however.

    Is there any way to get at these through the website?

  28. Oct 26, 2010

    Tamer Awad says:

    I wanna use this plugin but i couldn't get some data from it. I can not get pro...

    I wanna use this plugin but i couldn't get some data from it.

    I can not get project svn url.

  29. Dec 01, 2010

    Ignacio Alles says:

    I've made a patch from v1.10 to include two environment variables from the versi...

    I've made a patch from v1.10 to include two environment variables from the version you are promoting. The variables are ORIG_BUILD_NUMBER (such as 33) and ORIG_BUILD_ID (such as 2010-12-01_13-08-45).

    With these numbers you can access the artifact from an old revision or the archive build directory (for instance: $WORKSPACE/../$ORIG_BUILD_ID, or something like that).

    I hope I help someone.

    Files:
    hudson_promote_build-orig.patch
    promoted-builds.hpi

    1. Dec 01, 2010

      Iftach Bar says:

      Wow, that's really cool. thanks!

      Wow, that's really cool.

      thanks!

    2. Dec 06, 2010

      Aurélien Pelletier says:

      It does! Just what I needed. I thought BUILD_NUMBER and BUILD_ID environment v...

      It does!

      Just what I needed.

      I thought BUILD_NUMBER and BUILD_ID environment variables were supposed to give the same information as your ORIG_ variable, but they don't.

      Should be included in the official plugin.

      1. Dec 06, 2010

        Ignacio Alles says:

        I'm glad it helped. As the promotion process is in fact a new build, the enviro...

        I'm glad it helped.

        As the promotion process is in fact a new build, the environment variables BUILD_NUMBER and BUILD_ID correspond to this new build instead of the build that you are promoting.

  30. Dec 20, 2010

    Indra Gunawan says:

    Can I promote a build using remote API? We have a sanity test outside Hudson th...

    Can I promote a build using remote API? We have a sanity test outside Hudson that can execute remote API to promote the Hudson build which passes the test.

    Thank you.
    -Indra

  31. Mar 04, 2011

    baztheman says:

    Hi, I am using hudson server version 1.352, version 1.396 and promotion plugin ...

    Hi,

    I am using hudson server version 1.352, version 1.396 and promotion plugin version 1.10. My questions and issues are:

    1. I added actions into the promotion process but they do not work. Why? For example, I have a simple promotion process, I check or not check the "Only when manually approved", added description setter or email as actions. When I manually promoted the build, I did not see any changes to the description of the build nor receiving any email. Can someone help?

    2. How can i change the icons used in the promotion plugin. For example, can i add and change icons from stars to other picture or icons? How?

    Thank you.

    1. May 25, 2011

      Rohit Gupta says:

      Hi bazthman, Did you get the response back to your query. I am facing similar i...

      Hi bazthman,

      Did you get the response back to your query. I am facing similar issues.

      Thanks,
      Rohit

  32. Jul 11, 2011

    Saad says:

    Are promoted builds exempt from getting discarded if I set the Discard Old Build...

    Are promoted builds exempt from getting discarded if I set the Discard Old Builds options?

  33. Oct 11, 2012

    Ken Neth says:

    Are you still supporting this plug-in on Hudson? It appears that this has been a...

    Are you still supporting this plug-in on Hudson? It appears that this has been abandoned and moved to Jenkins.

    I tried the Jenkins plugin 2.7, and it does not work with Hudson.

    I am trying to get parameterized builds to work with promotions and found that there was a bug fix in the Jenkins version of the plugin that is not in the Hudson 2.4 version of the plugin.

    Can you either update this one or put a note above stating that you no longer support Hudson? Would save others some time and headache.

    Thanks

    1. Oct 11, 2012

      Winston Prakash says:

      Hi Ken, We are in the process of verifying all the plugins including this one fo...

      Hi Ken, We are in the process of verifying all the plugins including this one for Hudson 3.0.0. You can read about it here http://wiki.hudson-ci.org/display/HUDSON/Plugin+Verification.

      If you need this plugin to work for Hudson 2.x, let us know, we will make it available