• Future post

    If I coded the GitHub Action correctly, this blog post should get published even though I’ve dated it 40 minutes in the future from when I committed it to the repository.

  • Errors from PowerShell 7 in Azure Pipelines

    I’m aiming to use PowerShell 7 as much as possible, including in Azure Pipelines tasks. I was getting a bit frustrated recently though where I had a task failing, but the log gave absolutely no clue as to why.

    eg.

    Starting: MyTask
    ==============================================================================
    Task         : PowerShell
    Description  : Run a PowerShell script on Linux, macOS, or Windows
    Version      : 2.165.0
    Author       : Microsoft Corporation
    Help         : https://docs.microsoft.com/azure/devops/pipelines/tasks/utility/powershell
    ==============================================================================
    Generating script.
    ========================== Starting Command Output ===========================
    "C:\Program Files\PowerShell\7\pwsh.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'D:\a\_temp\be69a030-2e55-4cb5-9f80-98968e90f3b2.ps1'"
    ##[error]PowerShell exited with code '1'.
    Finishing: MyTask
    

    What’s going on? Turns out it’s because PowerShell 7 now defaults to the ‘ConciseView’ for errors and so the error ends up being so concise it isn’t actually logged. I’m not the first to experience this. The fact that the concise output is not logged at all does look like a bug though.

    The solution

    Set $ErrorView to ‘NormalView’ as the first line of your script - then you’ll see useful error details that will help with diagnosing what the problem is.

    $ErrorView = 'NormalView'
    

    Hopefully in the future, they’ll fix the problem with no errors being logged, or enhance the pwsh task so you can set the errorview as a task property outside of the script.

    Update 15th May

    As Justin mentions in the comments, this problem has been fixed, so no need to prepend your scripts with $ErrorView = 'NormalView' now!

  • Upgrading WSL2 to Ubuntu 20.04 and running Jekyll

    Ubuntu LTS 20.04 just came out, and you can either install into WSL2 from the Windows Store, or if you already had Ubuntu for WSL then you can upgrade that in place using sudo do-release-upgrade -d.

    There’s a few confirmation prompts along the way. Eventually you’ll get to a point where it wants to reboot. The trouble is if you try sudo reboot it will complain that you’re not running systemd and give up.

    The solution is to jump back to Windows and run wsl --shutdown, then relaunch Ubuntu and it should be happy.

    Jekyll

    Having a freshly upgraded install of Ubuntu, I thought it was time I got a local copy of Jekyll so I could preview my blog posts.

    To ensure that I’m using the same Gems that GitHub Pages use, I updated my Gemfile to just reference the github-pages gem.

    source 'https://rubygems.org'
    
    gem 'github-pages'
    

    And then install Jekyll prerequisites:

    sudo apt-get install ruby-full -y
    sudo apt-get install build-essential dh-autoreconf -y
    sudo apt install zlibc -y
    sudo apt install libxml2-dev -y
    sudo apt install libxslt-dev -y
    

    Tell Ruby to install Gems locally (so we don’t need sudo)

    echo 'export GEM_HOME=~/.ruby/' >> ~/.bashrc
    echo 'export PATH="$PATH:~/.ruby/bin"' >> ~/.bashrc
    source ~/.bashrc
    
    gem update
    
    gem install pkg-config -v "~> 1.1"
    gem install nokogiri -- --use-system-libraries
    
    bundle install