[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title manuel boillod commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly the are usecases where building all the tags in a random order (build storm) is not a problem. Indeed, if the pipeline build an artefact which is published in an artefact repository like nexus, there are no problem (except may be the extra workload for jenkins). If the tags is already built (already present in the artefact repository), the pipeline will fail as expected, and if the tag has never been built, the pipeline will succeed as expected. So adding this behaviour in the multibranch pipeline makes sense for me (with any warnings you want about the potential risks) Best regards, Manuel Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.2863.1575894300509%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Mark Waite closed an issue as Not A Defect Jenkins / JENKINS-47496 No automatic builds for tags Change By: Mark Waite Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.14838.1571794282128%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Liam Newman commented on JENKINS-47496 Re: No automatic builds for tags Marat Radchenko Please use the Basic Branch Build Strategies plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.5816.1567520520658%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Marat Radchenko commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly R. Tyler Croy This article clearly states that if we add "Discover tags" to multibranch pipeline, Jenkins will trigger builds when tags are pushed into repo. But this bug ( JENKINS-47496 ) says that tags are not supposed to trigger a build automatically. Could you please decide somehow which one of you is right? As a Jenkins user, I +1 for tag triggering. We want to use this to build/publish releases whenever Git tag is created. This is the way all other major CI systems work: Travis CI, CircleCI, AppVeyour. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.5627.1567516740485%40Atlassian.JIRA.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title
Will Curry updated an issue
Jenkins / JENKINS-47496
No automatic builds for tags
Change By:
Will Curry
After upgrading to the Git Plugin 3.6.0 I activated the "Discover Tags" option in a Multibranch Pipeline Job. The tag is also discovered as expected, but no build is triggered. {code:java}Checking tags... Checking tag PNR-12345 ‘Jenkinsfile’ found Met criteria Changes detected: PNR-12345 (null → d56c6578f5f04403f4bd64bf2647f3dd0f36e826) No automatic builds for PNR-12345 Processed 1 tags{code}I expected that a new build is triggered, when a new tag is found. How to achieve this?
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.8852.1561497660399%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title vinoth SS commented on JENKINS-47496 Re: No automatic builds for tags Sure, thanks i have opened up the ticket : https://issues.jenkins-ci.org/browse/JENKINS-57772 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.17091.1559261700428%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Liam Newman commented on JENKINS-47496 Re: No automatic builds for tags vinoth SS Please open a new JIRA for that. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.16708.1559229540392%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title vinoth SS commented on JENKINS-47496 Re: No automatic builds for tags I found some issue on Build strategy plugin for tags, if i specify Ignore tags newer than to 1 days, no automated builds are triggering, if i specify only 7 days builds are triggering, can we have that restriction to 1 day as well. so that automated builds will trigger only for tags which created less than 1 day. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.16455.1559191680599%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Jay Ache edited a comment on JENKINS-47496 Re: No automatic builds for tags I found that adding a Basic Branch Build Strategy to automatically build tags interfered with the rest of the multibranch pipeline builds automatically triggered by GitHub. They were working fine, then I added a Basic Branch Build Strategy to automatically build a tag, added a new tag, the new tag was automatically discovered and it attempted to build it (but failed with a NullPtrException; I had to manually schedule the tag build again before it successfully built, but that's an unrelated issue , probably because of this: https://issues.jenkins-ci.org/browse/JENKINS-50715 ). However, subsequent pushes to branches didn't re-trigger builds as expected. Simply removing the Basic Branch Build Strategy fixed it, and builds/pull-requests were again automatically built whenever pushes happened. I'll try Mark F's JobDSL workaround next. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.1917.1557794400289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Jay Ache commented on JENKINS-47496 Re: No automatic builds for tags I found that adding a Basic Branch Build Strategy to automatically build tags interfered with the rest of the multibranch pipeline builds automatically triggered by GitHub. They were working fine, then I added a Basic Branch Build Strategy to automatically build a tag, added a new tag, the new tag was automatically discovered and it attempted to build it (but failed with a NullPtrException; I had to manually schedule the tag build again before it successfully built, but that's an unrelated issue). However, subsequent pushes to branches didn't re-trigger builds as expected. Simply removing the Basic Branch Build Strategy fixed it, and builds/pull-requests were again automatically built whenever pushes happened. I'll try Mark F's JobDSL workaround next. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.849.1557739680362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title
Mark F commented on JENKINS-47496
Re: No automatic builds for tags
Here is the workaround to add tag discovery for multibranch pipelines in JobDSL:
multibranchPipelineJob('my_repo') {
branchSources { branchSource { source { git {
remote(git_url)
credentialsId('my_credential_id')
traits {
gitBranchDiscovery()
gitTagDiscovery() // be careful you don't create a build storm!
headWildcardFilter {
includes('my_branch1 my_branches* my_tags* )
excludes('')
}
}
} } } }
...
}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-47496) No automatic builds for tags
Title: Message Title
Raphael Reitzig edited a comment on JENKINS-47496
Re: No automatic builds for tags
[~stephenconnolly], this (non-)behaviour is quite confusing and I find your chain of reasoning unconvincing.{quote}You could have a build storm if you have 200 tags, they all get discovered and queued for building...{quote}So? The same happens with branches _by default_. I have to cancel all builds on old branches manually. Not even the build strategies plugin allows me to suppress builds on stale branches.(Maybe it's bad style to have lots of stale branches, but whether they are around in any given project is for none of us to decide.)Anyway, this only happens _once_ (after creating the project). The age restriction implemented in the build strategies plugin effectively prevents a "build storm"; why not integrate that functionality into the core?{quote}and your tags are set up to deploy to production because they are tags...{quote}That's quite the assumption. The pipeline may do nothing of the kind.{quote}and jenkins does not guarantee the order in which the tags will be discovered or actually executed... {quote}If the order matters, the pipeline author needs to take care of undesired effects, anyway.{ code quote } you have to explicitly configure it{ code quote }Without the build strategies plugin, how do you even do so?You seem to have a certain set of use cases in mind, which kind of contradicts how Jenkins (as a whole) is advertised as a general-purpose tool. While that's certainly your prerogative as an open-source maintainer (?), but you should maybe consider whether your perspective covers as many of your users as you'd like.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-47496) No automatic builds for tags
Title: Message Title
Raphael Reitzig edited a comment on JENKINS-47496
Re: No automatic builds for tags
[~stephenconnolly], this (non-)behaviour is quite confusing and I find your chain of reasoning unconvincing.{quote}You could have a build storm if you have 200 tags, they all get discovered and queued for building...{quote}So? The same happens with branches _by default_. I have to cancel all builds on old branches manually. Not even the build strategies plugin allows me to suppress builds on stale branches.(Maybe it's bad style to have lots of stale branches, but whether they are around in any given project is for none of us to decide.)Anyway, this only happens _once_ (after creating the project). The age restriction implemented in the build strategies plugin effectively prevents a "build storm"; why not integrate that functionality into the core?{quote}and your tags are set up to deploy to production because they are tags...{quote}That's quite the assumption. The pipeline may do nothing of the kind.{quote}and jenkins does not guarantee the order in which the tags will be discovered or actually executed... {quote}If the order matters, the pipeline author needs to take care of undesired effects, anyway. {code} you have to explicitly configure it{code}Without the build strategies plugin, how do you even do so? You seem to have a certain set of use cases in mind, which kind of contradicts how Jenkins (as a whole) is advertised as a general-purpose tool. While that's certainly your prerogative as an open-source maintainer (?), but you should maybe consider whether your perspective covers as many of your users as you'd like.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-47496) No automatic builds for tags
Title: Message Title
Raphael Reitzig edited a comment on JENKINS-47496
Re: No automatic builds for tags
[~stephenconnolly], this (non-)behaviour is quite confusing and I find your chain of reasoning unconvincing.{quote}You could have a build storm if you have 200 tags, they all get discovered and queued for building...{quote}So? The same happens with branches _by default_. I have to cancel all builds on old branches manually. Not even the build strategies plugin allows me to suppress builds on stale branches.(Maybe it's bad style to have lots of stale branches, but whether they are around in any given project is for none of us to decide.)Anyway, this only happens _once_ (after creating the project). The age restriction implemented in the build strategies plugin effectively prevents a "build storm"; why not integrate that functionality into the core?{quote}and your tags are set up to deploy to production because they are tags...{quote}That's quite the assumption. The pipeline may do nothing of the kind.{quote}and jenkins does not guarantee the order in which the tags will be discovered or actually executed... {quote}If the order matters, the pipeline author needs to take care of undesired effects, anyway.You seem to have a certain set of use cases in mind, which kind of contradicts how Jenkins (as a whole) is advertised as a general-purpose tool.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
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-47496) No automatic builds for tags
Title: Message Title Raphael Reitzig commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly, this (non-)behaviour is quite confusing and I find your chain of reasoning unconvincing. You could have a build storm if you have 200 tags, they all get discovered and queued for building... So? The same happens with branches by default. I have to cancel all builds on old branches manually. Not even the build strategies plugin allows me to suppress builds on stale branches. (Maybe it's bad style to have lots of stale branches, but whether they are around in any given project is for none of us to decide.) Anyway, this only happens once (after creating the project). The age restriction implemented in the build strategies plugin effectively prevents a "build storm"; why not integrate that functionality into the core? and your tags are set up to deploy to production because they are tags... That's quite the assumption. The pipeline may do nothing of the kind. and jenkins does not guarantee the order in which the tags will be discovered or actually executed... If the order matters, the pipeline author needs to take care of undesired effects, anyway. You seem to have a certain set of use cases in mind, which kind of contradicts how Jenkins (as a whole) is advertised as a general-purpose tool. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Aaron Marasco commented on JENKINS-47496 Re: No automatic builds for tags Stephen Connolly thanks for that plug-in; it's exactly what I needed. No more needing checkboxes in my job asking "Do you really mean it?" Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-47496) No automatic builds for tags
Title: Message Title Stephen Connolly commented on JENKINS-47496 Re: No automatic builds for tags Piotr Sobieszczański I recommend that you create a plugin with the variation of https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/src/main/java/jenkins/branch/buildstrategies/basic/TagBuildStrategyImpl.java that you need (if the implementation that is already available does not do what you actually need). Seriously, how hard is it to install the Basic Branch Build Strategies plugin and then do? If you need something for building tags that is different from the one in Basic Branch Build Strategies then it is trivial to create your own. But it looks to me like you were not even reading my comments...Because I said over a month ago how to build tags automatically... just that it will not exactly meet everyone's requirements because there are cases where building tags could result in build storms and this is why you have to explicitly configure it and decide what risk of build storms you are willing to take Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-47496) No automatic builds for tags
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-47496 No automatic builds for tags Change By: Stephen Connolly Attachment: Screen Shot 2018-08-14 at 00.41.53.png Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-47496) No automatic builds for tags
Title: Message Title Stephen Connolly updated an issue Jenkins / JENKINS-47496 No automatic builds for tags Change By: Stephen Connolly Attachment: build-tags.gif Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-47496) No automatic builds for tags
Title: Message Title Piotr Sobieszczański commented on JENKINS-47496 Re: No automatic builds for tags Hi Stephen, I understand that tags are not built in order. That obvious. Because I don't care about tags in my project up to now (= until I implement my repository with Jenkins), they can build in whatever order they want (Ideal situation would be if I could mark checkbox with label saying "Do not run old tags, only new one". And yes I understand you can have thousands of tags already, but in real life, you set up repo and then you set up the project with your CI/CD, so you don't have at all, or maybe after some time with maximum several dozens). I just want to build new tags and as you know you don't create several tags per minute. Normally there is one, two maybe three tags per day and that's all. In this situation, you are totally fine with an automatic build. So for instance, you creating a new tag, pushing it to a repo, then Jenkins is detecting it (and this is the only new tag comparing to his repo), and finally triggering it. That's the whole idea. Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-47496) No automatic builds for tags
Title: Message Title Stephen Connolly commented on JENKINS-47496 Re: No automatic builds for tags You could have a build storm if you have 200 tags, they all get discovered and queued for building... and your tags are set up to deploy to production because they are tags... and jenkins does not guarantee the order in which the tags will be discovered or actually executed... so production is constantly cycling different versions. In any case, if you want to build tags just install the Basic Branch Build Strategies plugin and configure it: https://github.com/jenkinsci/basic-branch-build-strategies-plugin/blob/master/docs/user.adoc#tags Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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-47496) No automatic builds for tags
Title: Message Title Leandro Lucarella commented on JENKINS-47496 Re: No automatic builds for tags you could have a build storm when checking out a repository I don't get this. What do you mean? I'm quite surprised by this design decision, other CI system build tags automatically and I never had any problems with it. Checking out the repository where could have a build storm? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- 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.
