Pulsant Cloud
We provide cloud capabilities to transform operations and drive your business forward
YOUR CLOUD, YOUR WAY
Find out more: https://www.pulsant.com/services/managed-cloud/
The latest News and Information on DevOps, CI/CD, Automation and related technologies.
We provide cloud capabilities to transform operations and drive your business forward
YOUR CLOUD, YOUR WAY
Find out more: https://www.pulsant.com/services/managed-cloud/
If you maintain a Ruby gem, you are definitely familiar with the recurring manual tasks surrounding the release of a new version. After doing this for a while, you inevitably start thinking that some of these steps could be automated. They can! With a few lines of code, you can bring the amazing world of continuous delivery to your project and increase the reliability of the whole process while freeing up some of your time. Double win!
Like many things in life, when you’re new to the cloud you don’t know what you don’t know. Given that migrating workloads to the public cloud is often a key component of a business transformation initiative, you want to avoid a long, expensive learning curve—especially since accelerating time-to-value is often a major impetus for the move.
In part 1 of our package repositories series, important terms like packages, metadata, dependencies, and upstreams were explained. In this part 2, we will take it further, diving into trends within the software landscape that have changed what developers and organizations want from a package repository. In recent years we’ve seen a push to use managed services in the cloud, automation, supply chain security.
Moving employees to Azure Virtual Desktop (AVD) or Windows 365 can have many advantages, including: But migrating to a virtual desktop environment also has its challenges. Perhaps the largest is ensuring that applications can be installed on the virtual desktop environment. And then, beyond installation, ensuring that each application performs at least as well as in the users’ former environment.
You groan. Perhaps not audibly, but your eyes widen and then slowly shut with dread. After a lucky streak of merging feature branches without incident, you finally hit a Git merge conflict. Unsure of where to start, you sheepishly bring up Slack and direct message a plea for help. Maybe this has been you, or maybe you’ve just seen it happen. Either way, it means spending time untangling the code by yourself, or with the sympathetic assistance of another.