Due to some maintenance issues, this service has been switched in read-only mode, you can find more information about the why

and how to migrate your plugin documentation in this blogpost

Skip to end of metadata
Go to start of metadata

Plugin Information

View Persistent Parameter on the plugin site for more information.

String, text, boolean and choice parameters with default values taken from the previous build (if any).

Version History

1.1 (Feb 20, 2015)
  • Support for non-interactive (periodic, SCM poll etc) builds
1.0 (Oct 24, 2014)
  • Initial release

15 Comments

  1. Unknown User (brantone)

    Curious what problem this is trying to solve?

    Does it remove the need to pass parameters to downstream jobs??

  2. Unknown User (greg2001)

    You can specify job parameters at the first run and parameter values you entered will be automatically available for succeeding runs.

  3. Unknown User (catonyx)

    I like this plug-in so far but it quickly revealed a downside compared to standard parameters. If I configure a job with default values, say the version for the next build, then the persistent value is used once it is established. So, I am wondering if there could be a flag or something to similar the "Successful only" where if selected in the configure screens, it would set the value to the default when saved. I would like to be able to "Seed with Default" without actually running the job. Hopefully, that is clear. Not sure if there is a formal way to request enhancements.

    1. Unknown User (greg2001)

      I think I know what you mean: you want to have a flag in the configuration forcing the plugin to take the default value, the flag shall be reseted after the build, right?

      Let me check if that's possible; I'll let you know.

      1. Unknown User (catonyx)

        I think that would give me the right effect. Essentially, it would not use the persistent value for the "next build" but use the default instead. It is kind of like saying I want to start over start with a new (default) persistent value.

  4. Unknown User (shokkas)

    I really like the abilities this plugin enables.

    Using this plugin I can allow developers to run a build and set the next build version (if needed) which is great.

    However, the last saved value of the persistent parameter is used when the build is triggered manually or on scheduling.

    If the job is triggered through SCM polling, the default value is used.

    Can this be fixed or a workaround provided?

    Thanks

    1. Unknown User (greg2001)

      I suppose, you're using the latest version of the plugin. What SCM do you have?

      I tested the plugin with ClearCase we're using in our company and it worked just fine; haven't tested it with others (git etc) though...

      Please describe me your configuration so that I could make a similar setup and try to reproduce the problem.

      1. Unknown User (shokkas)

        I do have the latest version of the plugin.
        The SCM we use is Git and have the Git plugin in use (configured to use a repository master branch).

        The Poll SCM trigger is enabled. When the time comes the Git plugin will check the remote Git repo for changes and if such are found will start a run of the job, in which time the persistent parameter roles back to default.

        Thanks! 

        1. Unknown User (greg2001)

          Thanks for the info - I'll try to reproduce and fix that.

          It could take a while: I'm on vacation for the next 3 weeks, so just hold on...

          1. Unknown User (shokkas)

            Enjoy your vacation.

            Meanwhile, workaround I'm using is:
            Some build changed from SCM poll schedule to regular schedule.
            Other builds, I've set the default value of the parameter to the last one entered by dev team.

            Not ideal but will hold the fort.

            Cheers

          2. Unknown User (shokkas)

            Enjoy your vacation.

            Meanwhile, workaround I'm using is:
            Some build changed from SCM poll schedule to regular schedule.
            Other builds, I've set the default value of the parameter to the last one entered by dev team.

            Not ideal but will hold the fort.

            Cheers

          3. Unknown User (shokkas)

            Multiple comments by mistake.

            How do I delete?

  5. Unknown User (srikanthreddykv)

    Hi,

    Is that possible to pass arguments by overriding before build starts, I mean dynamically while building jobs...? Thanks in advance.

  6. Unknown User (avreimale)

    How can one reference the last value for a given parameter to be used with the Run Condition plugin ?

  7. Unknown User (avreimale)

    How can one reference the last value for a given parameter to be used with the Run Condition plugin ?