## Where communities thrive

• Join over 1.5M+ people
• Join over 100K+ communities
• Free without limits
##### Activity
• Oct 02 2019 14:24
• May 10 2019 06:07
StefH commented #112
• May 07 2019 14:37
gep13 commented #112
• May 07 2019 14:13
StefH commented #112
• May 07 2019 14:06
henrikgjeriksson commented #112
• Nov 30 2018 09:25
StefH commented #117
• Nov 29 2018 10:54
StefH commented #117
• Nov 29 2018 10:29
david-bugeja commented #117
• Oct 27 2018 10:56
StefH commented #117
• Oct 26 2018 21:13
StefH commented #111
• Oct 26 2018 20:00
stunney commented #111
• Oct 26 2018 20:00
stunney commented #117
• Oct 08 2018 13:15
StefH commented #112
• Sep 22 2018 07:54
StefH opened #121
• Sep 22 2018 07:21
StefH commented #113
• Sep 22 2018 07:10
StefH closed #111
• Sep 22 2018 07:10
StefH commented #111
• Sep 22 2018 07:10
StefH closed #114
• Sep 22 2018 07:10
StefH commented #114
• Aug 29 2018 10:23
gep13 commented #117
Asbjørn Ulsberg
@asbjornu
I find that GRN generates very inaccurate release notes for https://github.com/getsentry/raven-csharp/
Some of the blame is probably on the project in which all development is not centered around pull requests, but weird things like version 1.4.6 not being included in the release notes and some issues and pull requests being tacked to the wrong version is unexpected behaviour, I’d say.
Asbjørn Ulsberg
@asbjornu
It also doesn’t seem to care whether issues are merged, fixed by other commits or simply closed (i.e. rejected).
Gary Ewan Park
@gep13
@asbjornu sorry, no, I am not sure off the top of my head, I would need to dig into it
@JakeGinnivan would be the person to answer that one
Asbjørn Ulsberg
@asbjornu
@JakeGinnivan Ideas? Cloning https://github.com/getsentry/raven-csharp/ and doing GitReleaseNotes.exe . /AllTags /OutputFile ReleaseNotes.md will reveal all the problems I’m seeing.
Jake Ginnivan
@JakeGinnivan
It is time based, so if the issues were not closed before the tag was created there will be issues
Asbjørn Ulsberg
@asbjornu
Hm ok
John Gietzen
@otac0n
Is there an easy way to exclude issues that were closed but not fixed? I have several issues that are being added to my release notes that I would rather not include.
I'm executing GitReleaseNotes . /O ReleaseNotes.cmd for https://github.com/otac0n/Pegasus
Based on the usage, I expect that these should be excluded already:
[/AllLabels|/AllL]                           Specifies that all labels should be included in the release notes, if not specified then only the defaults (bug, enhancement, feature) are included.
What am I missing?
Jake Ginnivan
@JakeGinnivan
lowercase o?
Jericho
@Jericho
My build script is throwing an error today when executed on AppVeyor. The problem seems to be caused by GitReleaseNotes. Here's the stack trace of the error:
Error:
Cake.Core.CakeException: GitReleaseNotes: Process returned an error (exit code -2).
at Cake.Core.Tooling.Tool1.ProcessExitCode(Int32 exitCode)
at Cake.Core.Tooling.Tool1.Run(TSettings settings, ProcessArgumentBuilder arguments, ProcessSettings processSettings, Action1 postAction)
at Cake.Common.Tools.GitReleaseNotes.GitReleaseNotesRunner.Run(FilePath outputFile, GitReleaseNotesSettings settings)
at Submission#0.<.ctor>b__37()
at Cake.Core.CakeEngine.RunTarget(ICakeContext context, IExecutionStrategy strategy, String target)
at Cake.Scripting.BuildScriptHost.RunTarget(String target)
at Submission#0..ctor(Session session, Object& submissionResult)
at Submission#0.<Factory>(Session session)
at Roslyn.Scripting.CommonScriptEngine.Execute[T](String code, String path, DiagnosticBag diagnostics, Session session, Boolean isInteractive)
at Roslyn.Scripting.Session.Execute(String code)
at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary2 arguments)
at Cake.Commands.BuildCommand.Execute(CakeOptions options)
at Cake.CakeApplication.Run(CakeOptions options)
at Cake.Program.Main()

Command executed with exception: ocessSettings, Action1 postAction)
at Cake.Common.Tools.GitReleaseNotes.GitReleaseNotesRunner.Run(FilePath outputFile, GitReleaseNotesSettings settings)
at Submission#0.<.ctor>b__37()
at Cake.Core.CakeEngine.RunTarget(ICakeContext context, IExecutionStrategy strategy, String target)
at Cake.Scripting.BuildScriptHost.RunTarget(String target)
at Submission#0..ctor(Session session, Object& submissionResult)
at Submission#0.<Factory>(Session session)
at Roslyn.Scripting.CommonScriptEngine.Execute[T](String code, String path, DiagnosticBag diagnostics, Session session, Boolean isInteractive)
at Roslyn.Scripting.Session.Execute(String code)
at Cake.Core.Scripting.ScriptRunner.Run(IScriptHost host, FilePath scriptPath, IDictionary2 arguments)
at Cake.Commands.BuildCommand.Execute(CakeOptions options)
at Cake.CakeApplication.Run(CakeOptions options)
at Cake.Program.Main()
and here's my build script 'Release Notes' task:
Task("Create-Release-Notes")
.Does(() =>
{
GitReleaseNotes(outputDir + "releasenotes.md", new GitReleaseNotesSettings {
WorkingDirectory         = ".",
AllLabels                = true,
AllTags                  = true,
Verbose                  = true
});
});
The weird thing is that I get no such error when running the build script locally
I reported this problem in the CakeBuild chat rom and @gep13 suggested I should report it here
Any suggestion what I should look at to investigate the problem?
One more thing: here's the relevant log captured by AppVeyor:
========================================
Create-Release-Notes
========================================
Executing: "C:/projects/picton-d73oi/tools/GitReleaseNotes/tools/GitReleaseNotes.exe" "." /OutputFile "C:/projects/picton-d73oi/artifacts/releasenotes.md" /Verbose /AllTags /AllLabels
Cake.exe : An error occured when executing task 'Create-Release-Notes'.
At line:1 char:1
+ & "C:\projects\picton-d73oi\tools\Cake\Cake.exe" "build.cake" -target ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : NotSpecified: (An error occure...Release-Notes'.:String) [], RemoteException
+ FullyQualifiedErrorId : NativeCommandError
Gary Ewan Park
@gep13
@jakeginnivan could this be the same issue that we were seeing in the GitVersion build?
Jake Ginnivan
@JakeGinnivan
@gep13 maybe
The issue with GitVersion is running out of anon API calls
I remember having issues with the task, didn't have time to look into it
Jericho
@Jericho
Can GetReleaseNotes update the "ReleaseNotes" section of a nuspec file?
Gary Ewan Park
@gep13
@Jericho no, that is not really the intention of the GitReleaseNotes. It does one thing, i.e. generate release notes. What you do with those notes would be handled by something else, i.e. a larger build script
Jericho
@Jericho
@gep13 correct me if I'm wrong: what you're suggesting is that my 'larger' cake build script would invoke GRM (which would output the notes in a '.md' file), open this .md file and read the content, open the nuspec file and write the content at the desired location. Does that sound right?
Gary Ewan Park
@gep13
yes, that would pretty much sum it up, yes. One question though, you said GRM which suggests to be GitReleaseManager, but you are posting in the GitReleaseNotes Gitter Room. Those are two different tools :-D
Jericho
@Jericho
I meant GRN, sorry for the confusion
Gary Ewan Park
@gep13
no problem, just wanted to check :+1:
either way, the process is the same.
Jericho
@Jericho
I'm too lazy to type the whole name!
Gary Ewan Park
@gep13
assuming you are using NuGetPack, you could pass the generated release notes into the NuGetPackSettings class, and it would take care of it for you, so no need to open nuspec file
Jericho
@Jericho
that's an interesting suggestion. I am indeed using nugetpack so this sounds like a pretty good option
I whish I could invoke GRN like so: var notes = GitReleaseNotes(...), this would avoid writing to '.md'
Gary Ewan Park
@gep13
that is really down to the underlying tool. It itself doesn't do that, and the cake aliases tend to mimic what the tool does, so that there is no surprises
you could create a helper method to do it for you though
Matthias Koch
@matkoch
Anyone has an idea, why issues are duplicated across releases? #_5 and #_3 are not even in the commit range of 5.0.7:
5.0.7 (08 March 2017)
#7 - 7 +improvement +wontfix
#5 - 5 +feature
#4 - 4 +breaking-change
#3 - 3 +improvement
Commits: fe6ee03...523f413

5.0.5 (08 March 2017)
#5 - 5 +feature
#3 - 3 +improvement
Commits: ...
Matthias Koch
@matkoch
Always includes the issues from the last release. What's going on :/
Matthias Koch
@matkoch
Looks like the a tag for the release has to be there before running GRN.
That's quite surprising, because the name for the release (which should always be tagName, right?), is already passed.
Matthias Koch
@matkoch
Okay this gets too strange.. can please someone tell me in which order you: Tag, Create Release, Call GRN ?
Gary Ewan Park
@gep13
the best person to answer these questions would be @JakeGinnivan but I know he is really busy just now.
Jake Ginnivan
@JakeGinnivan
Pretty sure it just looks at the issues closed between the tags, it's been too long 😕 after next week I should have my free time back to get back into oss .
hichamkari
@hichamkari
Hi Guys, can someone help me with one issue
Where can I find the meanings of the exit codes related to GitReleaseNotes
?
I got Process returned an error (exit code -2)
hichamkari
@hichamkari
Hi,
I executed this command
.\tools\GitReleaseNotes\tools\GitReleaseNotes.exe . /AllTags /RepoToken "myRepoToken" /RepoUrl MyRepoUrl /RepoBranch master /Version 0.0.0-test /Verbose /OutputFile ReleaseNotes.md
But I don't see anything happening
Can someone look into it ?