Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Nov 26 11:21

    matkoch on 6.0.0

    Update NuGet token (compare)

  • Nov 26 11:16

    matkoch on 6.0.0

    (compare)

  • Nov 26 11:15

    matkoch on develop

    Fix placement of JsonPropertyAt… Move specification files Fix MinVerSettings.Verbosity fo… and 27 more (compare)

  • Nov 26 10:00
    matkoch milestoned #792
  • Nov 26 10:00
    matkoch milestoned #809
  • Nov 26 10:00
    matkoch milestoned #815
  • Nov 26 09:59
    matkoch milestoned #813
  • Nov 26 09:59
    matkoch milestoned #814
  • Nov 26 09:59
    matkoch commented #814
  • Nov 26 09:59
    matkoch commented #813
  • Nov 26 09:59
    matkoch commented #814
  • Nov 26 09:58

    matkoch on develop

    Add MSBuildVersion.VS2022 and u… Update AzurePipelines, GitHubAc… Update AppVeyor to Visual Studi… and 2 more (compare)

  • Nov 26 09:57
    matkoch commented #814
  • Nov 26 09:55

    matkoch on develop

    Fix ConfigurationGenerationTest… (compare)

  • Nov 26 09:33

    matkoch on move

    project/solution model wip (compare)

  • Nov 26 09:32
    mvestergaard commented #814
  • Nov 26 09:32
    matkoch closed #764
  • Nov 26 09:30
    matkoch commented #815
  • Nov 26 09:30

    matkoch on develop

    Add Boots (#815) (compare)

  • Nov 26 09:30
    matkoch closed #815
Benjamin Höglinger
@nefarius
I just created a fresh project with latest nuke and the template has some inconsistency errors:
Maybe that's already known?
Matthias Koch
@matkoch
i guess you need to update your global tool
Benjamin Höglinger
@nefarius
Ah bloody hell, good point
Benjamin Höglinger
@nefarius
Jupp, that worked, thanks! :thumbsup:
Matthias Koch
@matkoch
:)
It’s quite hard to make a good compromise
the templates are contained in the global tool, which allows offline usage
however, this implies that outdated global tools might be not working with new versions of nuke.common
Benjamin Höglinger
@nefarius
No worries, once you know it
Matthias Koch
@matkoch
@/all :mega::shipit: NUKE 0.12.2 IS OUT!!!
  • Fixed globbing related issues
  • Fixed shell-completion to not split common names
  • Fixed bootstrapping scripts to guard extraction of SDK version
  • Fixed help text to be printed before value injection
Matthias Koch
@matkoch
@/all :mega::shipit: NUKE 0.12.3 IS OUT!!!
  • Fixed EnvironmentInfo.Variables not to be cached
  • Fixed Glob package reference in legacy template
  • Fixed error message for unresolvable root directory
  • Fixed global tool setup to hide choice of bootstrapping by default
  • Fixed NuGetPackageResolver assertion for dependency resolution
Wiesław Šoltés
@wieslawsoltes
Is it possible to disable path warning :
2018-12-02T10:34:57.7524304Z ##[warning]Path environment variable contains invalid or inaccessible path '"/usr/local/sbin'.
2018-12-02T10:34:57.7534493Z ##[warning]Path environment variable contains invalid or inaccessible path '/usr/local/games"'.
Matthias Koch
@matkoch
@wieslawsoltes currently not, but there will be a switch for that... you can create an issue if you like
Wiesław Šoltés
@wieslawsoltes
@matkoch Added issue nuke-build/nuke#189
Matthias Koch
@matkoch
Thanks!
Simonas G
@SlowLogicBoy
PANICK! All the icons ran away from Api Reference and I now need to read TOC to find what I'm looking for :laughing:
Matthias Koch
@matkoch
:)
Matthias Koch
@matkoch
@/all :mega::shipit: NUKE 0.13.0 IS OUT!!!
  • Change verification of PATH environment variable to be executed only with Trace log level
  • Added ToolSettings.When for conditional fluent modifications
  • Added .editorconfig file in setup to avoid formatting issues
  • Added DotMemoryUnitTasks
  • Added missing properties in DotNetCleanSettings, DotNetRestoreSettings and MSBuildSettings.Restore
Wiesław Šoltés
@wieslawsoltes
:+1:
Benjamin Höglinger
@nefarius

When running powershell .\build.ps1 locally - which defaults to Debug configuration - I can't build because it complains about locked file:

"D:\Development\...\build\_build.csproj" (Rebuild target) (3) ->
       (CopyFilesToOutputDirectory target) ->
         C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\amd64\Microsoft.Common.CurrentVersion.targets(4194,5): warning MSB3026: Could not copy "obj\Debug\_build.dll" to "bin\Debug\_build.dll". Beginning retry 1 in 1000ms. The process cannot access the file 'bin\Debug\_build.dll' because it is being used by another process. The file is locked by: ".NET Core Host (19464)" [D:\Development\GitHub\ViGEmClient\build\_build.csproj]
         C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\amd64\Microsoft.Common.CurrentVersion.targets(4194,5): warning MSB3026: Could not copy "obj\Debug\_build.dll" to "bin\Debug\_build.dll". Beginning retry 2 in 1000ms. The process cannot access the file 'bin\Debug\_build.dll' because it is being used by another process. The file is locked by: ".NET Core Host (19464)" [D:\Development\GitHub\ViGEmClient\build\_build.csproj]
         C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\amd64\Microsoft.Common.CurrentVersion.targets(4194,5): warning MSB3026: Could not copy "obj\Debug\_build.dll" to "bin\Debug\_build.dll". Beginning retry 3 in 1000ms. The process cannot access the file 'bin\Debug\_build.dll' because it is being used by another process. The file is locked by: ".NET Core Host (19464)" [D:\Development\GitHub\ViGEmClient\build\_build.csproj]

PEBKAC? Known issue? This went under the radar for long because I literally only build Release all the time :sweat_smile:

nuke 0.13.0, netstandard2.0
Matthias Koch
@matkoch
debug for _build.csproj?
Benjamin Höglinger
@nefarius
Debug for entire solution
Matthias Koch
@matkoch
if your build project is build when building the solution, you have a misconfigured solution
*being built
Matthias Koch
@matkoch
Benjamin Höglinger
@nefarius
Ok @matkoch I swear to god I was cleaning the solution file before I posted here, you're some sort of dark wizard, ofc. it works now :sweat_smile: thanks!
Matthias Koch
@matkoch
some things are very easy to discover :) There is an open PR for issuing a warning (https://github.com/nuke-build/nuke/pull/203)
Vlad Khapin
@Liminiens
Oh, you stumbled on the same problem
Benjamin Höglinger
@nefarius
I was already deselecting it from build but VS put it back, the bastard! I saw it in Git diff :angry:
Matthias Koch
@matkoch
(rider) :)
Matthias Koch
@matkoch
@/all :mega::shipit: NUKE 0.14.0 IS OUT!!!
  • Removed named target dependencies
  • Removed choice of target framework in setup
  • Changed setup to write solution file reference to configuration file again
  • Added extended solution parsing with integration for Microsoft.Build
  • Added Configuration type
  • Added continue parameter
  • Added checking for active build project configurations in solution files
  • Added highlighting for default target in HTML graph
  • Added SonarScannerTasks
  • Added EnvironmentInfo.SwitchWorkingDirectory
  • Added SymbolPackageFormat property for DotNetTasks, MSBuildTasks, and NuGetTasks
  • Fixed bootstrapping scripts not to leave DotNet processes behind
  • Fixed bootstrapping scripts to correctly quote arguments
  • Fixed overload of tool path for .NET Core executables
  • Fixed default value not to be hidden by cursor
  • Fixed ToolSettingsExtensions.When to have generic constraint on ToolSettings
  • Fixed InspectCodeTasks to use deterministic hashing
  • Fixed ChangelogTasks to correctly parse empty sections at end of file
  • Fixed InjectionAttributeBase to express implicit assignment only
  • Fixed ExternalFilesTask to be executed before Restore target
Vlad Khapin
@Liminiens
@matkoch happy holidays:)
Matthias Koch
@matkoch
thanks, you and everyone else too :)
Matthias Koch
@matkoch
@/all :mega::shipit: NUKE 0.14.1 IS OUT!!!
  • Fixed package reference versions
  • Fixed SolutionSerializer to handle empty lines
Simonas G
@SlowLogicBoy
Nuke no longer runs async tasks ? or awaits them?
Matthias Koch
@matkoch
Which version?
Simonas G
@SlowLogicBoy
because after updating to 0.14.1 tasks that are async produce no output and not being ran :?
upgraded from 0.10.1
Matthias Koch
@matkoch
Well, of course not intentionally
Could you check if the correct Executes method gets called? Just use goto declaration
Simonas G
@SlowLogicBoy
well first I'll try to debug then :)
Matthias Koch
@matkoch
thx, if it persists, please create an issue in nuke-build/nuke with a small repro
Simonas G
@SlowLogicBoy
ok I think this is my problem :)
Matthias Koch
@matkoch
not perfect, but better :D
Simonas G
@SlowLogicBoy
GlobFiles pattern matching changed probably?
Because that one doesn't want to work
Matthias Koch
@matkoch
might be, we changed to another version