I wanted to have a look at some GitHub Enterprise Server (GHES) upgrade scenarios so decided to create a quick GHES install on my local test Hyper-V instance. Due to me skimping on resources, and making a typo, creating this instance was much harder than it should have been. The first issue was I gave it a tiny data disk, this was down to me making a typo in my GB to Bytes conversion when specifying the size. Interestingly, the GHES setup does not initially complain but sits on the ‘reloading system services’ stage until it times out. If you check the /setup/config.log you see many Nomad related 500 errors. A reboot of the VM showed the real problem, the log then showed plenty of out-of-disk space messages. ...

I was recently trying to set up a copy of the Outlook desktop app with two outlook.com email accounts and hit a strange issue. I was able to add the first one without any problems, but when I tried to add the second one I got an error message asking for PIN, and most importantly on the same dialog showing the second outlook.com email address. This is confusing as I know of no way to set a PIN on an outlook.com account. ...

A recent addition to GitHub Actions is the ability to create a custom job summary. Using a simple echo command in a script you can write to the job summary steps: - name: Adding markdown run: echo '### Hello world! :rocket:' >> $GITHUB\_STEP\_SUMMARY Now, this got me thinking. I have a well-used custom release notes extension for Azure DevOps. It has a GitHub Action equivalent, but it does not seem to get as much usage. Would adding support for custom Job Summaries make it more useful? ...

GitHub’s Dependabot is a great tool to help keep your dependencies up to date, and most of the time the PR it generates just merges without a problem. However, sometimes there are issues with other related dependencies. This was the case with a recent PR to update jest-circus to 28.x. The PR failed with the error TypeError: Cannot read property ’enableGlobally’ of undefined at jestAdapter (node_modules/jest-circus/build/legacy-code-todo-rewrite/jestAdapter.js:39:25) at TestScheduler.scheduleTests (node_modules/@jest/core/build/TestScheduler.js:333:13) at runJest (node_modules/@jest/core/build/runJest.js:404:19) at _run10000 (node_modules/@jest/core/build/cli/index.js:320:7) at runCLI (node_modules/@jest/core/build/cli/index.js:173:3) ...

Did you miss the ‘Microsoft and GitHub DevOps Forum: DevSecOps’ event I presented at earlier in May? Well worry not, the on-demand stream is now available - here

I have blogged in the past ( here , here and here) about the complexities and possible areas of confusion with different types of Azure DevOps pipeline variables. Well here is another example of how to use variables and what can trip you up. The key in this example is the scope of a variable, whether it is available outside a job and the syntax to access it Variables local to the Job So, if you create your variable as shown below ...

As I have posted about previously, we create our Azure DevOps build agent images using the same Packer definitions as used by Microsoft. This time when I ran my Packer command to build an updated VHD I got the error Build ‘vhd’ errored after 135 milliseconds 708 microseconds: adal: Refresh request failed. Status Code = ‘401’. Response body: {“error”:“invalid_client”,“error_description”:“AADSTS7000222: The provided client secret keys for app ‘6425416f-aa94-4c20-8395-XXXXXXX’ are expired. Visit the Azure portal to create new keys for your app: https://aka.ms/NewClientSecret, or consider using certificate credentials for added security: https://aka.ms/certCreds.rnTrace ID: 65a200cf-8423-4d52-af07-67bf26225200rnCorrelation ID: 0f86de87-33fa-443b-8186-4de3894972e1rnTimestamp: 2022-05-03 08:36:50Z”,“error_codes”:[7000222],“timestamp”:“2022-05-03 08:36:50Z”,“trace_id”:“65a200cf-8423-4d52-af07-67bf26225200”,“correlation_id”:“0f86de87-33fa-443b-8186-4de3894972e1”,“error_uri”:“https://login.microsoftonline.com/error?code=7000222"} Endpoint https://login.microsoftonline.com/545a7a95-3c4d-4e88-9890-baa86d5fdacb/oauth2/token==> Builds finished but no artifacts were created. ...

I’m speaking at the resheduled Microsoft and GitHub DevOps Forum on the 4th of March. To Register: https://mktoevents.com/Microsoft+Event/333304/157-GQE-382?wt.mc_id=AID3045587_QSG_EML_586670

Issue I had an Azure DevOps YAML based pipeline that had been working but was now getting stuck with the message “Job is pending…” when trying to start a stage in which there is a deployment to an environment. Looking at the logs and Azure DevOps UI it was not obvious what the issue was. Solution Turns out it was due to environment checks and approvals. There was a branch policy on the environment. This was set to only allow use of Azure DevOps Templates on a given branch. The edit that had been done to the YAML meant it was trying to extend a template in a branch that was not in the approved list. ...

Update: This event has been rescheduled for the 4th May. The new registration link is here I’m speaking at the Microsoft and GitHub DevOps Forum on the 10th of March. To register - https://mktoevents.com/Microsoft+Event/325749/157-GQE-382