[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Nicolas Forney commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Wayne Warren your workaround works only if you are always branching from master. In our team developers often branch from other developers branch or from a develop branch. And with Git there is no way to really know from which branch a branch as been created (they are only tags). I really wish Jenkins will be able to tell me which commit are affected on the first build. But apparently this issue has been open for years without any progress. Add Comment This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38) -- 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.182912.1497360024000.16779.1587680280447%40Atlassian.JIRA.
[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title Jesse Glick resolved as Duplicate Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: Jesse Glick Status: Open Resolved Resolution: Duplicate 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.182912.1497360024000.9518.1571316182303%40Atlassian.JIRA.
[JIRA] (JENKINS-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin updated JENKINS-44849 Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: benoit guerin Status: In Review Progress 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin stopped work on JENKINS-44849 Change By: benoit guerin Status: In Progress Open 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin updated JENKINS-44849 Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: benoit guerin Status: In Progress Review 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin assigned an issue to benoit guerin Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: benoit guerin Assignee: benoit guerin 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin assigned an issue to Unassigned Jenkins / JENKINS-44849 Changeset for first run of generated job is empty Change By: benoit guerin Assignee: benoit guerin 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin started work on JENKINS-44849 Change By: benoit guerin Status: Open In Progress 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-44849) Changeset for first run of generated job is empty
Title: Message Title Nathan Mische commented on JENKINS-44849 Re: Changeset for first run of generated job is empty I just ran into this today. Any update on this issue? 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-44849) Changeset for first run of generated job is empty
Title: Message Title benoit guerin commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Same on bitbucket-branch-source-plugin here : JENKINS-48687 It goes down to the git plugin itself, not computing the changelog for the first build of a new branch : JENKINS-14138 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-44849) Changeset for first run of generated job is empty
Title: Message Title Stepan Mazurov commented on JENKINS-44849 Re: Changeset for first run of generated job is empty Wayne Warren absolutely agreed - changeset is useless in any type of advanced use case. Thank you for the workaround! 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-44849) Changeset for first run of generated job is empty
Title: Message Title
Wayne Warren edited a comment on JENKINS-44849
Re: Changeset for first run of generated job is empty
This is a pretty serious problem that significantly impairs the functionality of the `changeset` directive in declarative pipeline. I would go as far as to say that the `changeset` directive is worthless because of its counter intuitive and inconsistent behavior. It's led myself and a teammate to make several meaningless changes to our `changeset` usages to see if that would make the job run the conditional stages; of course whenever we made such changes within a PR the next build would actually run so we mistakenly thought we had fixed something , even though in reality all we had done was satisfy the condition under which Jenkins would actually acknowledge that changes are present in the PR as described in this ticket . Since I absolutely know some other poor fool is going to encounter this problem, this is the workaround I've come up with:{code:java}+ _expression_ {+ sh(returnStatus: true, script: 'git diff origin/master --name-only | grep "^auth.*" > /dev/null') == 0+ }{code}
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-44849) Changeset for first run of generated job is empty
Title: Message Title
Wayne Warren commented on JENKINS-44849
Re: Changeset for first run of generated job is empty
This is a pretty serious problem that significantly impairs the functionality of the `changeset` directive in declarative pipeline. I would go as far as to say that the `changeset` directive is worthless because of its counter intuitive and inconsistent behavior. It's led myself and a teammate to make several meaningless changes to our `changeset` usages to see if that would make the job run the conditional stages; of course whenever we made such changes within a PR the next build would actually run so we mistakenly thought we had fixed something. Since I absolutely know some other poor fool is going to encounter this problem, this is the workaround I've come up with:
+ _expression_ {
+ sh(returnStatus: true, script: 'git diff origin/master --name-only | grep "^auth.*" > /dev/null') == 0
+ }
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.
