Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 03 18:48
  • Oct 12 2016 09:42
    ewilde unassigned #107
  • Oct 12 2016 09:42
    ewilde unassigned #107
  • Oct 12 2016 09:42
    ewilde assigned #107
  • Oct 12 2016 09:42
    ewilde assigned #107
  • Aug 08 2016 09:05
    ewilde opened #109
  • Aug 08 2016 09:05
    ewilde opened #108
  • Dec 18 2015 11:02
    ewilde opened #107
  • Dec 18 2015 11:02
    ewilde labeled #107
  • Jul 02 2015 14:25
    mrdavidlaing opened #106
  • Jun 29 2015 20:35
    Thieum starred ewilde/crane
  • Jun 29 2015 19:40

    ewilde on master

    ImprovedRelativeSolutionPathToB… Finally got copyright symbol updated test text to be correct and 151 more (compare)

  • Jun 29 2015 19:27

    ewilde on develop

    Increase wait time for service … (compare)

  • Jun 26 2015 19:14

    ewilde on develop

    fixing running scripts in direc… fixed paths with spaces (compare)

  • Jun 25 2015 21:25

    ewilde on ewilde-profile

    fixed paths with spaces (compare)

  • Jun 23 2015 20:52

    ewilde on ewilde-profile

    fixing running scripts in direc… (compare)

  • Mar 12 2015 20:55

    ewilde on feature-chocoapi-99

    updated build to use invoke-cho… (compare)

  • Mar 12 2015 20:33

    ewilde on feature-chocoapi-99

    first stab at choco pack implement test for choco pack '… (compare)

  • Mar 08 2015 17:47

    ewilde on develop

    coverity bug fixes Merge branch 'develop' of githu… (compare)

  • Mar 08 2015 17:46
    ewilde labeled #99
Edward Wilde
@ewilde
@kevholditch got burned earlier on with merging. When we re-cased those directories. Best to blow away local repositories, seems that the old lower case names can hang around. And bad things happen, that only get picked up on case sensitive OS. like the mono build.
good job we have that build or we would never have noticed. And would have had a very weird git repo
Kevin Holditch
@kevholditch
Ok good spot. I've think I've done that on all of my clones of the repo but will check again
Edward Wilde
@ewilde
hey just come across this project https://github.com/themotleyfool/Ciao/
Edward Wilde
@ewilde
found that profiler I was trying to track down the other day: https://clrprofiler.codeplex.com/
Edward Wilde
@ewilde
old school video showing how to use this profiler
Kevin Holditch
@kevholditch
Cool you finally found it amongst all of your saved links :)
Edward Wilde
@ewilde
yup the great link database in the sky
also known as google !
Edward Wilde
@ewilde
in your face garden path
finally got Klondike working under team city :palm_tree:
Kevin Holditch
@kevholditch
Awesome stuff mate
Edward Wilde
@ewilde
tx :) very happy chappy!
Edward Wilde
@ewilde
hey kev have you got a link to the mem profiler videos you were watching today?
Kevin Holditch
@kevholditch
Bit noddy but I found it helpful
Edward Wilde
@ewilde
great thanks
Kevin Holditch
@kevholditch
Can we get a license sorted for ants profiler tomorrow as we are going to need it
Edward Wilde
@ewilde
blob
nice no more waiting for manual approvals :+1:
@mrdavidlaing nuget support is in latest release
As you see from the integration test you need to invoke the 'NugetPublish' target and supply an api key as a required param
blob
David Laing
@mrdavidlaing
@ewilde - yay - thank you
David Laing
@mrdavidlaing
@ewilde - I’ve installed the latest crane:
PS C:\Windows\system32> choco install crane
Chocolatey (v0.9.8.31) is installing 'crane' and dependencies. By installing you accept the license for 'crane' and each
 dependency you are installing.
'crane 0.2.0.15' already installed.
If you want to reinstall the current version of an existing package, please use the -force command.

Finished installing 'crane' and dependencies - if errors not shown in console, none detected. Check log for errors if un
sure.

However, it seems to be missing the .nuspec template I can see at

https://github.com/ewilde/crane/tree/develop/src/Crane.Templates/source/VisualStudio/src/%25context.ProjectName%25

PS C:\Windows\system32> ls C:\ProgramData\chocolatey\lib\crane.0.2.0.15\tools\Templates\source\VisualStudio\src\%context
.ProjectName%


    Directory:
    C:\ProgramData\chocolatey\lib\crane.0.2.0.15\tools\Templates\source\VisualStudio\src\%context.ProjectName%


Mode                LastWriteTime     Length Name
----                -------------     ------ ----
d----        30/06/2015     11:51            Properties
-a---        30/06/2015     11:51       2406 %context.ProjectName%.csproj
-a---        30/06/2015     11:51        295 Calculator.cs
And when I crane init <Project> the resulting scaffolding doesn’t include a .nuspec file
David Laing
@mrdavidlaing
Looking at the file list at https://chocolatey.org/packages/crane it seems the .nuspec file hasn’t been published
Edward Wilde
@ewilde
not sure it's part of the package, it should just get created when you do a crane init
David Laing
@mrdavidlaing
@ewilde I manually created a nuspec, but it doesn't seem to be getting used when I run build.ps1
@ewilde Which part of the build scripts trigger the creation of the Nuget package? Or is that only when you actually try to publish the package?
Edward Wilde
@ewilde
yeah weird it should be build via crane init but it's not, ill have to check later and get back to you.
*built
David Laing
@mrdavidlaing
Thanks
David Laing
@mrdavidlaing

@ewilde After manually creating my .nuspec file, I discovered that you can trigger a Nuget publish using:

build.ps1
build.ps1 -nuget_api_key 76b0XXXXX NugetPublish

However, it seems that it is using the incorrect -Source setting, failing with

psake version 4.4.0
Copyright (c) 2010-2014 James Kovacs & Contributors

-------------------------[SetupContext]-------------------------


sln_file_info       : C:\dev\log4net.Appenders.Contrib\src\log4net.Appenders.Contrib.sln
solution_context    : Crane.Core.Api.SolutionContext
chocolatey_api_key  :
configuration       : Debug
nuget_api_url       : https://www.nuget.org/api/v2/
nuget_api_key       : 76b040c7XXXX
nuget_file          :
build_version       : 2.0.0.0
build_dir           : C:\dev\log4net.Appenders.Contrib\build
verbose             :
packages_folder     : C:\dev\log4net.Appenders.Contrib\src\packages
nuget_artifacts_dir : C:\dev\log4net.Appenders.Contrib\build-output\nuget
root_dir            : C:\dev\log4net.Appenders.Contrib
teamcity_build      : False
build_artifacts_dir : C:\dev\log4net.Appenders.Contrib\build-output
is_git_repo         : True
chocolatey_api_url  :

-------------------------[NugetExists]-------------------------
-------------------------[NugetPack]-------------------------
Attempting to build package from 'log4net.Appenders.Contrib.nuspec'.
Successfully created package 'C:\dev\log4net.Appenders.Contrib\build-output\nuget\log4net.Appenders.Contrib.2.0.0.0.nup
kg'.


-------------------------[NugetPublish]-------------------------
Error: 02/07/2015 15:06:12:
At C:\dev\log4net.Appenders.Contrib\build\modules\nugettasks.psm1:21 char:5 +     Invoke-CraneNugetPublishAllProjects $
global:context.solution_context -NugetO ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~~~~~ [<<==>>] Exception: Error executing nuget push for project log4net.Appenders.Contrib.Command: C:\dev\log4net.Ap
penders.Contrib\build\NuGet.exe push "C:\dev\log4net.Appenders.Contrib\build-output\nuget\log4net.Appenders.Contrib.2.0
.0.0.nupkg" -Source https://www.nuget.org/api/v2/ -ApiKey 76b040c7XXX, StandardOutput: Pushing
 log4net.Appenders.Contrib 2.0.0.0 to 'https://www.nuget.org/api/v2/'..., ErrorOutput: Failed to process request. 'Meth
od Not Allowed'. The remote server returned an error: (405) Method Not Allowed.., ExitCode: 1

I think that the correct NuGet -Source is:

https://www.nuget.org/api/v2/package

Is this a bug, or a problem with the way I’m invoking the NugetPublish target?

Edward Wilde
@ewilde
can you try changing the source to https://www.nuget.org
or passing in source as https://www.nuget.org
David Laing
@mrdavidlaing
This seems to work
PS C:\dev\log4net.Appenders.Contrib> .\build.ps1 -nuget_api_key 76b040c7XXX -nuget_api_url http
s://www.nuget.org/api/v2/package NugetPublish

psake version 4.4.0
Copyright (c) 2010-2014 James Kovacs & Contributors

-------------------------[SetupContext]-------------------------


sln_file_info       : C:\dev\log4net.Appenders.Contrib\src\log4net.Appenders.Contrib.sln
solution_context    : Crane.Core.Api.SolutionContext
chocolatey_api_key  :
configuration       : Debug
nuget_api_url       : https://www.nuget.org/api/v2/package
nuget_api_key       : 76b040c7XXXXX
nuget_file          :
build_version       : 2.0.1.0
build_dir           : C:\dev\log4net.Appenders.Contrib\build
verbose             :
packages_folder     : C:\dev\log4net.Appenders.Contrib\src\packages
nuget_artifacts_dir : C:\dev\log4net.Appenders.Contrib\build-output\nuget
root_dir            : C:\dev\log4net.Appenders.Contrib
teamcity_build      : False
build_artifacts_dir : C:\dev\log4net.Appenders.Contrib\build-output
is_git_repo         : True
chocolatey_api_url  :

-------------------------[NugetExists]-------------------------
-------------------------[NugetPack]-------------------------
Attempting to build package from 'log4net.Appenders.Contrib.nuspec'.
Successfully created package 'C:\dev\log4net.Appenders.Contrib\build-output\nuget\log4net.Appenders.Contrib.2.0.1.0.nup
kg'.


-------------------------[NugetPublish]-------------------------
Pushing log4net.Appenders.Contrib 2.0.1.0 to 'https://www.nuget.org/api/v2/package'...
Your package was pushed.



Build Succeeded!

----------------------------------------------------------------------
Build Time Report
----------------------------------------------------------------------
Name         Duration
----         --------
SetupContext 00:00:00.0196846
NugetExists  00:00:00.0020109
NugetPack    00:00:00.3147637
NugetPublish 00:01:06.3255324
Total:       00:01:06.6869157
Edward Wilde
@ewilde
did it work with the source just as https://www.nuget.org ?
David Laing
@mrdavidlaing
PS C:\dev\log4net.Appenders.Contrib> .\build.ps1 -nuget_api_key 76b040c7-XXX -nuget_api_url http
s://www.nuget.org NugetPublish
Appears to work too
Edward Wilde
@ewilde
looks like a bug with the default in crane
yeah that should be the correct way to do it
nuget is wierd sometime you have to pass /api/v2 in the source other times it doesn't want it!!!!
David Laing
@mrdavidlaing
Yeah!
Should I raise a bug against crane?
Edward Wilde
@ewilde
yes please :)
David Laing
@mrdavidlaing
@ewilde Here you go: #106