Thanks for the reply and consideration. I would say it is kind of
interceptor that will intercept source update step/process during build.
@Answers:
1. Yes it build war file and We use svn as a source version control.
2. We have task repository that is configured in developer's IDE. On commit
we get following information automatically from task repository:
@Pattern:
${task.key}: ${task.description}
Task-Url: ${task.url}
@Values
TSK01: Add a new client - Sprint1
Task-Url: http://xxxx:8080/browse/TSK01
3. Good question. We will fetch only task related changes in source code.
That can be managed by SVN revision number if I am not wrong. Here is one
scenario:
File A.java is used in TSK01 and TSK03. TSK01 is going to release.
Developers will commit for TSK01 and TSK03 individually and that will
create a revision number. We will fetch only TSK01's revision changes for
A.java.
I have not viewed jenkins as solution. I just want to tweak jenkins
automation process with a plugin that will perform some pre-build and
post-build actions. it is a automation.
Kind Regards
Sunny Dyal
On Monday, 1 June 2015 13:06:44 UTC+5:30, Corneil du Plessis wrote:
>
> 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] <javascript:>>
> 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] <javascript:>.
>> 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/9cef766f-8dc4-49fb-9ea8-3beb6be94d7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
