For multi-branch pipeline, deleting branch from github project will not result in deleting of same branch project from jenkins.

1 797 vues
Accéder directement au premier message non lu

Vijay Surwase

non lue,
20 déc. 2016, 00:04:0420/12/2016
à Jenkins Users
Whenever i create new branch in github project, new project named with same branch gets created in multi-branch pipeline project in jenkins.
But vise versa is not possible.
please let me know the reason or is there any way to do this ?

Trever

non lue,
20 déc. 2016, 12:47:2120/12/2016
à Jenkins Users
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.

Vijay Surwase

non lue,
28 déc. 2016, 04:37:4028/12/2016
à jenkins...@googlegroups.com
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b8925449-a555-4ccd-b9eb-26debc967dde%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Stephen Connolly

non lue,
28 déc. 2016, 05:24:1028/12/2016
à jenkins...@googlegroups.com
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
--


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 jenkinsci-use...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAAjva%2BzKEbYbyamE27Ky7y_UkfSzzQis706mQwvcfYuh_SGPAw%40mail.gmail.com.



For more options, visit https://groups.google.com/d/optout.


--
Sent from my phone

Vijay Surwase

non lue,
31 déc. 2016, 12:06:4931/12/2016
à jenkins...@googlegroups.com
Thank you for you response. I am using 2.19 version. After branch deletion it will wait for few days to remove that branch job from multi-branch pipeline. It basically depends on build history retention policy as mentioned in above mail trail.

On Wed, Dec 28, 2016 at 3:53 PM, Stephen Connolly <stephen.al...@gmail.com> wrote:
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.
--
Sent from my phone

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwjkebnVM1O9pCvQKBw3km27Zb1VW5c8n3qx2a%2Bj7SxiA%40mail.gmail.com.

Stephen Connolly

non lue,
31 déc. 2016, 16:21:2031/12/2016
à jenkins...@googlegroups.com
SCM API 2.0.1+ and Branch API 2.0.0+ and friends... not Jenkins version

On Sat 31 Dec 2016 at 17:06, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you for you response. I am using 2.19 version. After branch deletion it will wait for few days to remove that branch job from multi-branch pipeline. It basically depends on build history retention policy as mentioned in above mail trail.

On Wed, Dec 28, 2016 at 3:53 PM, Stephen Connolly <stephen.al...@gmail.com> wrote:
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
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 jenkinsci-use...@googlegroups.com.
--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
--


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 jenkinsci-use...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAAjva%2BwuOxCNOOErH7wKCxK6W-GxFvmnMRDaDKq_6DGFwF42ug%40mail.gmail.com.



For more options, visit https://groups.google.com/d/optout.


Vijay Surwase

non lue,
1 janv. 2017, 00:21:1601/01/2017
à jenkins...@googlegroups.com
SCM API 1.3 and Branch API 1.11.1.

On Sun, Jan 1, 2017 at 2:51 AM, Stephen Connolly <stephen.al...@gmail.com> wrote:
SCM API 2.0.1+ and Branch API 2.0.0+ and friends... not Jenkins version
On Sat 31 Dec 2016 at 17:06, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you for you response. I am using 2.19 version. After branch deletion it will wait for few days to remove that branch job from multi-branch pipeline. It basically depends on build history retention policy as mentioned in above mail trail.

On Wed, Dec 28, 2016 at 3:53 PM, Stephen Connolly <stephen.alan.connolly@gmail.com> wrote:
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.
--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwjkebnVM1O9pCvQKBw3km27Zb1VW5c8n3qx2a%2Bj7SxiA%40mail.gmail.com.



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 jenkinsci-users+unsubscribe@googlegroups.com.


--
Sent from my phone

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwqbYyaQTfiGYq2uonYUrqgh61SJJnfMx3Q82WZAdxGSQ%40mail.gmail.com.

Stephen Connolly

non lue,
1 janv. 2017, 09:06:5101/01/2017
à jenkins...@googlegroups.com
Exactly. You should find improvements once I cut the non-beta releases in the coming week

On Sun 1 Jan 2017 at 05:21, Vijay Surwase <surwa...@gmail.com> wrote:
SCM API 1.3 and Branch API 1.11.1.

On Sun, Jan 1, 2017 at 2:51 AM, Stephen Connolly <stephen.al...@gmail.com> wrote:
SCM API 2.0.1+ and Branch API 2.0.0+ and friends... not Jenkins version
On Sat 31 Dec 2016 at 17:06, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you for you response. I am using 2.19 version. After branch deletion it will wait for few days to remove that branch job from multi-branch pipeline. It basically depends on build history retention policy as mentioned in above mail trail.

On Wed, Dec 28, 2016 at 3:53 PM, Stephen Connolly <stephen.al...@gmail.com> wrote:
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
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 jenkinsci-use...@googlegroups.com.
--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwjkebnVM1O9pCvQKBw3km27Zb1VW5c8n3qx2a%2Bj7SxiA%40mail.gmail.com.



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 jenkinsci-use...@googlegroups.com.


--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-use...@googlegroups.com.
--


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 jenkinsci-use...@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAAjva%2BwkRJ85OisUG%3DtD5sdvXPgksJSe59Uw%3Dp%2ByPu3_gMBOeA%40mail.gmail.com.



For more options, visit https://groups.google.com/d/optout.


Vijay Surwase

non lue,
1 janv. 2017, 09:13:4401/01/2017
à jenkins...@googlegroups.com
Thank you so much

On Sun, Jan 1, 2017 at 7:36 PM, Stephen Connolly <stephen.al...@gmail.com> wrote:
Exactly. You should find improvements once I cut the non-beta releases in the coming week
On Sun 1 Jan 2017 at 05:21, Vijay Surwase <surwa...@gmail.com> wrote:
SCM API 1.3 and Branch API 1.11.1.

On Sun, Jan 1, 2017 at 2:51 AM, Stephen Connolly <stephen.alan.connolly@gmail.com> wrote:
SCM API 2.0.1+ and Branch API 2.0.0+ and friends... not Jenkins version
On Sat 31 Dec 2016 at 17:06, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you for you response. I am using 2.19 version. After branch deletion it will wait for few days to remove that branch job from multi-branch pipeline. It basically depends on build history retention policy as mentioned in above mail trail.

On Wed, Dec 28, 2016 at 3:53 PM, Stephen Connolly <stephen.alan.connolly@gmail.com> wrote:
If using the 2.0.0+ versions (currently only in the experimental update centre) the events will mark the branch as a dead branch within 5s of the branch being deleted.

The branch will not actually be deleted until the branch indexing has run and only if the Orphaned Item strategy marks the branch for deletion.

Once a branch is a dead branch, however, you can manually delete it sooner (assuming you have delete permissions)

(This behaviour is necessary to eg allow close PR & reopen PR to trigger a rebuild while retaining history)

HTH

On Wed 28 Dec 2016 at 09:37, Vijay Surwase <surwa...@gmail.com> wrote:
Thank you.

On Tue, Dec 20, 2016 at 11:17 PM, Trever <trever...@gmail.com> wrote:
I believe it may depend on your build history retention policy. If your policy is to keep builds for 10 days, the build will remain for 10 days. I've found that changing the retention policy will allow it to be removed sooner.





--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
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 jenkinsci-users+unsubscribe@googlegroups.com.
--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwjkebnVM1O9pCvQKBw3km27Zb1VW5c8n3qx2a%2Bj7SxiA%40mail.gmail.com.



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 jenkinsci-users+unsubscribe@googlegroups.com.


--
Sent from my phone








--


You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.


To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.


To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.


To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMwqbYyaQTfiGYq2uonYUrqgh61SJJnfMx3Q82WZAdxGSQ%40mail.gmail.com.



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 jenkinsci-users+unsubscribe@googlegroups.com.


--
Sent from my phone

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/YXcQDmnE128/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscribe@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzCH%2B0z5nG_yhs9WMUpdvfz7mxQVty06rrkXq8Bti_VEQ%40mail.gmail.com.
Répondre à tous
Répondre à l'auteur
Transférer
0 nouveau message