[JIRA] (JENKINS-41092) Build Triggers > Build periodically is not preset for child project by multi-branch-project-plugin
Title: Message Title Yuriy Zaplavnov created an issue Jenkins / JENKINS-41092 Build Triggers > Build periodically is not preset for child project by multi-branch-project-plugin Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2017/Jan/15 11:34 PM Environment: Jenkins: 2.40 Multi-Branch Project Plugin: 0.5.1 Priority: Major Reporter: Yuriy Zaplavnov Hello, I'm not sure if this is the issue of the plugin, however it seems so. Any condition specified at Build Triggers > Build periodically for parent is not updated or saved in any child project created by multi-branch-project-plugin. In child project the checkbox is turned off and the field for configuration (textbox) is empty. Can you please check and help to resolve this? Thank you, Add Comment
[JIRA] (JENKINS-39926) No Gitlab configuration in Build Triggers
Title: Message Title Yuriy Zaplavnov edited a comment on JENKINS-39926 Re: No Gitlab configuration in Build Triggers Thanks for the assistance. Could you please tell a few words to understand this properly. Would it require to extend branch-api-plugin or make other modifications in gitlab plugin to make it working? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title Yuriy Zaplavnov edited a comment on JENKINS-40529 Re: Prune tags on fetch Yes, the options such as to prune the branches or to fetch the specific refspec are available and they are the part of the advanced options, however they are unfortunately not relevant to the case I'm looking for. Let's imagine there is a job which is configured to clone repository and pull the changes for the specific branch. Additionally to the changes, all the tags associated with commits within that branch are also retrieved from central repository. For example: Step 1: there is a branch 'test-branch' which is supposed to be retrieved and pulled for the changes. The 'test-branch' contains the commits with associated tags: 'test-tag1', 'test-tag2'. Step 2: Run job, and all those tags will be fetched from origin. Step 3: Someone updates origin by removing tag 'test-tag2' and associating a new tag 'test-tag3' with a commit within our sample branch 'test-branch'. Step 4: Run job, and our workspace would contain new tag 'test-tag3', and old one 'test-tag2' which was removed in origin (but still exists in checked workspace). The goal is to do not have 'test-tag2' in checked workspace, because it doesn't exist already in origin. As far as I see there is no way at the moment how it could be achieved by using the git-plugin, therefore I wondered to prune tags. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title
Yuriy Zaplavnov updated an issue
Jenkins / JENKINS-40529
Prune tags on fetch
Change By:
Yuriy Zaplavnov
The git-plugin doesn't prune tags on fetch and it comes to the situation when there are a lot of unused tags already fetched and stored locally in .git even though that tags in central repository were already removed.In cases when the build process is based on tags, old tags could play a role and break the custom build logic.To avoid this, there is an option to delete a workspace entirely before build, however it doesn't look like a right and nice solution to clone everything again.It would help a lot if there will be an option implemented to prune tags on fetch such as{code: shell none }# git fetch --prune origin +refs/tags/*:refs/tags/*{code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title
Yuriy Zaplavnov updated an issue
Jenkins / JENKINS-40529
Prune tags on fetch
Change By:
Yuriy Zaplavnov
The git-plugin doesn't prune tags on fetch and it comes to the situation when there are a lot of unused tags already fetched and stored locally in .git even though that tags in central repository were already removed.In cases when the build process is based on tags, old tags could play a role and break the custom build logic.To avoid this, there is an option to delete a workspace entirely before build, however it doesn't look like a right and nice solution to clone everything again.It would help a lot if there will be an option implemented to prune tags on fetch such as $ {code:shell}# git fetch --prune origin +refs/tags/*:refs/tags/* {code}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it,
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title Yuriy Zaplavnov updated an issue Jenkins / JENKINS-40529 Prune tags on fetch Change By: Yuriy Zaplavnov The git-plugin doesn't prune tags on fetch and it comes to the situation when there are a lot of unused tags already fetched and stored locally in .git even though that tags in central repository were already removed.In cases when the build process is based on tags, old tags could play a role and break the custom build logic.To avoid this, there is an option to delete a workspace entirely before build, however it doesn't look like a right and nice solution to clone everything again.It would help a lot if there will be an option implemented to prune tags on fetch such as # $ git fetch --prune origin +refs/tags/*:refs/tags/* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title Yuriy Zaplavnov updated an issue Jenkins / JENKINS-40529 Prune tags on fetch Change By: Yuriy Zaplavnov The git-plugin doesn't prune tags on fetch and it comes to the situation when there are a lot of unused tags already fetched and stored locally in .git even though that tags in central repository were already removed.In cases when the build process is based on tags, old tags could play a role and break the custom build logic.To avoid this, there is an option to delete a workspace entirely before build, however it doesn't look like a right and nice solution to clone everything again.It would help a lot if there will be an option implemented to prune tags on fetch such as# git fetch --prune origin +refs/tags/*:refs/tags/* Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to
[JIRA] (JENKINS-40529) Prune tags on fetch
Title: Message Title Y Z created an issue Jenkins / JENKINS-40529 Prune tags on fetch Issue Type: New Feature Assignee: Mark Waite Components: git-plugin Created: 2016/Dec/18 4:07 PM Priority: Major Reporter: Y Z The git-plugin doesn't prune tags on fetch and it comes to the situation when there are a lot of unused tags already fetched and stored locally in .git even though that tags in central repository were already removed. In cases when the build process is based on tags, old tags could play a role and break the custom build logic. To avoid this, there is an option to delete a workspace entirely before build, however it doesn't look like a right and nice solution to clone everything again. It would help a lot if there will be an option implemented to prune tags on fetch such as git fetch --prune origin +refs/tags/:refs/tags/ Add Comment
[JIRA] (JENKINS-39926) No Gitlab configuration in Build Triggers
Title: Message Title Y Z created an issue Jenkins / JENKINS-39926 No Gitlab configuration in Build Triggers Issue Type: Bug Assignee: Matthew DeTullio Components: multi-branch-project-plugin Created: 2016/Nov/21 11:36 PM Priority: Major Reporter: Y Z 1. The plugin https://wiki.jenkins-ci.org/display/JENKINS/GitLab+Plugin is installed, but invisible or not available to be configured at "Build Triggers" when the multi-branch job is configured. If we go to the created job for a particular branch the option is available and could be configured. 2. On each reindexing on multi-branch job, the previously configured Gitlab settings for the branch jobs are reset and Gitlab build trigger is disabled. Add Comment
[JIRA] (JENKINS-30058) Support Maven Core Extensions
Title: Message Title Y Z commented on JENKINS-30058 Re: Support Maven Core Extensions +1 Any ETA when this feature is going to be delivered? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
