What you are describing seems to be a configuration management issue instead of a build issue.
Answering the following questions should help in moving towards a solution: Does your process build a binary artifact and manage this artifact through a lifecycle or do you use the version control system to manage which code is in which state? How is the code and changes that comprise a task identified? What do you do if source code is impacted by multiple tasks some of which are not going to release? You should never view Jenkins as a solution to a problem but rather a way of automating a solution that can work without Jenkins. [image: --] Corneil du Plessis [image: https://]about.me/corneil <https://about.me/corneil?promo=email_sig> On 1 June 2015 at 09:18, Sunny Dyal <[email protected]> wrote: > I want to develop a plugin that will use a comma separated list of > tasks/issues as input (for instance TSK01, ISU02, TSK03 and many more) and > export only related files from svn/git and assemble them in one unit > war/jar/zip/xyz and deploy. > > @User Story > As a project manager I want to release only 10 items out of 15 so that I > can manage clients/delivery properly. > > @Why: > 1. Saving my neck for next release. I will deliver pending tasks in next > release. > 2. May be there are minor/major bugs that should not be delivered. > > @Description: > I have a list of 15 tasks that are being developed but I want to release > only few/selected of them. My project does't have enable/disable feature > functionlity. We always send source code along with build therefore I don't > want extra or non-planned task's code go out. Developer commit their code > on daily basis with <<TASK ID>> and <<DESCRIPTION>> and work on same branch > (all 15 tasks belongs to same branch). > > @Planned List of Tasks/Issues (For Build or Deliverable) > TSK01, ISU02, TSK03, TSK04, TSK12, TSK11, TSK07, TSK09, TSK05 and ISU05. > > @Jenkins: > Do we have any plugin that can fullfill my requirement? if yes please let > me know I will review else I am ready to develop a plugins. Paperwork has > been done. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-users/b02d258f-e4bc-406a-b577-110758617e1c%40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-users/b02d258f-e4bc-406a-b577-110758617e1c%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CACPng9bv4f0sQQFCqEsCcqmWF65MuH7xQdS%3D7kJ-pxf_Y9rOiQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
