Hi Jesper, I have a similar case in one project. But we use the promote plugin.
We have different types of promotions, like promote to QA.
These promotions can happen automatically or manually.
Hope that helps
Bruno
--
Em seg, 3 de mar de 2014 12:17 BRT Jesper Eskilson escreveu:
>Hi,
>
>I have a particular use-case which I'm not sure how to approach. We have a
>production build environment which runs every night. I would like to be
>able to define certain actions (e.g. "release") on each build which the
>user should be able to execute (manually). Ideally, I'd like to have a
>"Release" button on the status page for each build, possibly with some
>additional configuration parameters for the external script.
>
>As I understand it there are at least three options available:
>
>1. Use the batch-task-plugin. The problem here is that the
>batch-task-plugin only seem to be able to execute the task on the project
>itself. There does not seem to be a way to specify which build to execute
>the task for.
>2. Extend the batch-task plugin.
>3. Write my own plugin.
>
>Any ideas about how I should proceed? Are there any other plugins which
>might already do this?
>
>
>--
>You received this message because you are subscribed to the Google Groups
>"Jenkins Developers" group.
>To unsubscribe from this group and stop receiving emails from it, send an
>email to jenkinsci-dev+unsubscr...@googlegroups.com.
>For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
