Details
-
Improvement
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
-
Platform: All, OS: All
Description
This is a "would be nice to have" request, so please file it accordingly! :o)
When a developer destroys a sub-branch of the one Hudson is monitoring, a build is triggered, even
though no modification to the watched branch occurred.
For instance, let's say my project is watching "feature_1.23" and the following change is found:
"20080326.110739" "esmalling" "destroy sub-branch "esmalling_branch" of branch"
"vobs/gtx2/core/src/foo/bar/MyFile.java" "/main/feature_1.23"
Destroyed branch "/main/feature_1.23/esmalling_branch".
That's not something we want to have built.
But if the feature_1.23 branch itself was destroyed, then we DO want a build.
Attachments
Activity
In the attached "Picture 2.png" there is a piece of a view tree, assume that the "roadmap_dev5" branch is
right off of the "main" (trunk) branch. As you can see, each of our developers has a sub-branch off of the
"roadmap_dev5" one. Also assume that Hudson is watching "roadmap_dev5" for changes to trigger builds.
Now, let's say that the "ecosta_frivaiii_roadmap_dev5_20070719" sub-branch is destroyed. Today, that
triggers a build of the "roadmap_dev5" branch and what I'm wanting is for it not to.
If, however, for some reason, someone destroys the "roadmap_dev5" branch itself (not likely to happen,
but it could), that SHOULD trigger a build since the contents of the file will now be back to what's on
"main".
Code changed in hudson
User: : redsolo
Path:
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/AbstractClearCaseScm.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearCaseSCM.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearCaseUcmSCM.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/action/DefaultPollAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/action/PollAction.java
trunk/hudson/plugins/clearcase/src/main/resources/hudson/plugins/clearcase/ClearCaseSCM/config.jelly
trunk/hudson/plugins/clearcase/src/main/resources/hudson/plugins/clearcase/ClearCaseUcmSCM/config.jelly
trunk/hudson/plugins/clearcase/src/main/webapp/filteroutdestroysubbranchevent.html
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/AbstractClearCaseScmTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/ClearCaseSCMTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/ClearCaseUcmSCMTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/action/DefaultPollActionTest.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=10367
Log:
JENKINS-1470 Option to not trigger build on downstream branch destroys
Code changed in hudson
User: : redsolo
Path:
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/AbstractClearCaseScm.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ClearToolHistoryParser.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/action/ChangeLogAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/action/DefaultPollAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/action/PollAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/base/BaseChangeLogAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/ucm/UcmChangeLogAction.java
trunk/hudson/plugins/clearcase/src/main/java/hudson/plugins/clearcase/util/EventRecordFilter.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/AbstractClearCaseScmTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/action/DefaultPollActionTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/base/BaseChangeLogActionTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/ucm/UcmChangeLogActionTest.java
trunk/hudson/plugins/clearcase/src/test/java/hudson/plugins/clearcase/util/EventRecordFilterTest.java
http://fisheye4.cenqua.com/changelog/hudson/?cs=10370
Log:
[FIXED JENKINS-1470] Added option to not trigger build on downstream branch destroys
Code changed in hudson
User: : redsolo
Path:
trunk/hudson/plugins/clearcase/src/main/resources/hudson/plugins/clearcase/ClearCaseSCM/config.jelly
trunk/hudson/plugins/clearcase/src/main/resources/hudson/plugins/clearcase/ClearCaseUcmSCM/config.jelly
trunk/hudson/plugins/clearcase/src/main/webapp/filteroutdestroysubbranchevent.html
trunk/hudson/plugins/clearcase/src/test/resources/hudson/plugins/clearcase/ct-lshistory-1.log
http://fisheye4.cenqua.com/changelog/hudson/?cs=10374
Log:
JENKINS-1470 Some text changes
Bulk-updating all bugs fixed through 0.8.1 to VERIFIED. Part of cleanup for
0.8.2 release.
What is the difference between a branch and a sub branch? Why would you like a build if
the branch was destroyed, I mean unless all files were removed then nothing really happened?
I have another user request that it should ignore the "destroyed branch" actions, so I
dont know what to do.
Do you know of any place where I can find all types of actions that can show up in the
history? To be able to ignore change log actions I must know the exact action phrase ("create
branch", etc.)