Weird bug in Calculate Changelog behavior

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Weird bug in Calculate Changelog behavior

jbrooks
Hi all-

I'm using the "Calculate Changelog Against a Specific Branch" additional behavior, and I've used the GIT_PREVIOUS_SUCCESSFUL_COMMIT env variable. However, I'm getting this error in my build:

Using 'Changelog to branch' strategy.
fatal: bad revision '^origin/$GIT_PREVIOUS_SUCCESSFUL_COMMIT'
ERROR: Unable to retrieve changeset

I've attached a screenshot of the config. It's straightforward: use the origin repo, and use a variable. Why isn't this field interpolating the variable? (I've tried other variables- it just doesn't seem to respect variables at all, regardless of whether I have braces around them or not.)

Cheers,
Jack

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Screen Shot 2017-12-21 at 18.21.29.png (60K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Weird bug in Calculate Changelog behavior

Mark Waite-2
I suspect it is not interpreting that variable because variable expansion is not implemented for that field.  I suspect the original author did not consider variable expansion in handling that field.

I think that is a novel use of the field, asking it to compute changes since the last successful build.  I'm more accustomed to that field being used to define a common branch against which diffs are performed.

Mark Waite

On Thu, Dec 21, 2017 at 4:23 PM <[hidden email]> wrote:
Hi all-

I'm using the "Calculate Changelog Against a Specific Branch" additional behavior, and I've used the GIT_PREVIOUS_SUCCESSFUL_COMMIT env variable. However, I'm getting this error in my build:

Using 'Changelog to branch' strategy.
fatal: bad revision '^origin/$GIT_PREVIOUS_SUCCESSFUL_COMMIT'
ERROR: Unable to retrieve changeset

I've attached a screenshot of the config. It's straightforward: use the origin repo, and use a variable. Why isn't this field interpolating the variable? (I've tried other variables- it just doesn't seem to respect variables at all, regardless of whether I have braces around them or not.)

Cheers,
Jack

--
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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtG8ixqct2Y%3DhBUc3JLNK-vn_rw5hhPxCj9G3mVTGtqJPQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: Weird bug in Calculate Changelog behavior

jbrooks
Hmm, that's what I was afraid of! Darn my novel approaches! *shakes fist*

Yeah, I'm looking for a way to make sure that, for manual builds, I can still generate changelogs for branches. It's possible there's a more idiomatic way to do this and I'm just not aware of it.

Thanks!
Jack

On Thursday, December 21, 2017 at 6:59:57 PM UTC-5, Mark Waite wrote:
I suspect it is not interpreting that variable because variable expansion is not implemented for that field.  I suspect the original author did not consider variable expansion in handling that field.

I think that is a novel use of the field, asking it to compute changes since the last successful build.  I'm more accustomed to that field being used to define a common branch against which diffs are performed.

Mark Waite

On Thu, Dec 21, 2017 at 4:23 PM <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="HmAjB4UeAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jbr...@...> wrote:
Hi all-

I'm using the "Calculate Changelog Against a Specific Branch" additional behavior, and I've used the GIT_PREVIOUS_SUCCESSFUL_COMMIT env variable. However, I'm getting this error in my build:

Using 'Changelog to branch' strategy.
fatal: bad revision '^origin/$GIT_PREVIOUS_SUCCESSFUL_COMMIT'
ERROR: Unable to retrieve changeset

I've attached a screenshot of the config. It's straightforward: use the origin repo, and use a variable. Why isn't this field interpolating the variable? (I've tried other variables- it just doesn't seem to respect variables at all, regardless of whether I have braces around them or not.)

Cheers,
Jack

--
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 <a href="javascript:" target="_blank" gdf-obfuscated-mailto="HmAjB4UeAwAJ" rel="nofollow" onmousedown="this.href=&#39;javascript:&#39;;return true;" onclick="this.href=&#39;javascript:&#39;;return true;">jenkinsci-use...@googlegroups.com.
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.com?utm_medium=email&amp;utm_source=footer" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.com?utm_medium\x3demail\x26utm_source\x3dfooter&#39;;return true;">https://groups.google.com/d/msgid/jenkinsci-users/80a97199-bece-45e6-afec-9ae3062d7aeb%40googlegroups.com.
For more options, visit <a href="https://groups.google.com/d/optout" target="_blank" rel="nofollow" onmousedown="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;" onclick="this.href=&#39;https://groups.google.com/d/optout&#39;;return true;">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 [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9aabdb3f-33b1-4c26-9308-59ab316c03b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.