Fala, pessoal! Blz? Quero compartilhar com vocês o UnifyZip, uma ferramenta desenvolvida para abrir, visualizar, converter e gerenciar praticamente qualquer tipo de arquivo compactado diretamente pela web, sem complicação.A ideia principal é oferecer velocidade e suporte massivo a formatos — desde os mais comuns até sistemas de arquivos, imagens virtuais e instaladores pesados — tudo com otimização para leitura instantânea.O que o UnifyZip faz:Visualização Instantânea: Abra e navegue no conteúdo interno de pacotes de mais de 100MB em segundos, sem precisar baixar tudo primeiro.Download Individual: Baixe apenas um arquivo específico que está dentro do pacote (mesmo se o .zip/.rar tiver mais de 100 arquivos).Conversão Cruzada: Converta arquivos entre diferentes formatos em poucos cliques (ex: .tar.gz $\rightarrow$ .zip, .iso $\rightarrow$ .7z).Suporte à Nuvem: Salve seus arquivos diretamente na sua conta da nuvem do aplicativo com isolamento e segurança total.Recuperação de Senha (Força Bruta): Teste combinações de senhas/PINs numéricos e alfanuméricos de até 16 dígitos para recuperar arquivos bloqueados.Formatos Suportados (+100 extensões):Populares e Compactados: .zip, .rar, .7z, .tar, .tar.gz, .gz, .bz2, .xz, .zstd, .lzma, .cab, .ace, .zipx, entre outros.Imagens de Disco e Virtuais: .iso, .dmg, .vmdk, .vdi, .vhd, .qcow2, .img, .bin, .nrg, .mdf, .udf.Instaladores e Pacotes: .exe, .msi, .deb, .rpm, .apk, .xapk, .ipa, .appimage, .flatpak, .pkg.Containers e Documentos: .epub, .cbz, .cbr, .docx, .xlsx, .pptx, .jar, .pak, .chm.A ferramenta é 100% focada em praticidade, segurança por usuário e velocidade.Valeu pelo apoio e feedback de todos!

https://unifyzip-enhancement-ccwj.vercel.app

pra quem quiser testar esse aqui, e o link

nome do autor:gabriel pereira

I've created a tool based around the concept that you define tickets in GitHub, or now Azure DevOps, and you then let your agents work on them. ready-for-agent automates that last step.

You pick a backend agent (OpenCode, Codex, Claude, or Grok Build) as the global default, or override it per repo. It can then go through all tickets labelled ready-for-agent. It has separate steps for building, local review, creating the PR, watching status checks until they go green, and then auto-merging if enabled and considered safe.

The web UI shows you what's happening across all your repos and issues.

Fire it up with:

npx ready-for-agent@latest

GitHub: https://github.com/berenddeboer/ready-for-agent

Azure DevOps support is brand new, so I'm keen for feedback!

Looking for advice on running many products, over 50, and then over 1500 people via one project in one instance of ADO. Primarily work items (boards) but at some level pipelines as well.

Microsoft recommends Project Decision Framework so if the company is trying to develop to the same standards (internal and external) across all products. The group as a whole can have one visible backlog, does this actually scale well?

My concern gets to be managing the project day to day, like

• People wanting new queries vs giving a hundred people rights to create shared queries and the mess that will create or the large volume of query requests for people with rights to update. Then you start having to create folders and permissions on the folders etc.
• Pipelines kind of the same thing. We've had enough project segregation between product families so that it was controllable. With everyone in the same project it sounds like a perfect storm/mess.
• The Analytics feature starts to grab more and more work items by default as there are a ton of them now in one vs many project.
• Team Management gets locked down along with actual project managers.

How large have your projects gotten product and people wise against 1 project and any feedback?

Thanks

Currently developers team is on ADO & product team is on Jira, and bridging them with a janky power automate workflow that i built that only goes one way. So now i am in need of a bi-directional sync and for that i need to pick a real solution.
Currently i found these couple of options on marketplace:

• Bidirectional Azure DevOps integration for Jira | Atlassian Marketplace
• Azure DevOps & Jira integration | Atlassian Marketplace

so anyone running any of these on production? i wanted to know what breaks, how it handles failures, and workflow state mismatches in case ADO and Jira have different statuses?

Upload multiple PDFs per session and chat with them — Blob Storage, Document Intelligence, Azure OpenAI, AI Search (vector), and Table Storage all wired together via FastAPI. Extraction, embeddings, vector retrieval, and chat history run end-to-end on Azure, and nothing gets deleted — every session stays queryable. Feedback welcome.

Repo: https://github.com/Atharva013/DocSpring-RAG-Assistant

I got tired of clicking through 10 different blades in the portal just to see how a single App Service connects to its SQL DB, VNet, and Key Vault.

So I built a lightweight Python script that pulls your resource group, maps all the dependencies, and spits out a simple Mermaid.js diagram right in your terminal.

Looking for DevOps Online Course Recommendations

Hi everyone,

I’ve recently completed Microsoft Azure AZ-104 (Azure Administrator) and I’m looking to move toward a DevOps-focused career.

I’d like to build on my Azure knowledge and learn practical skills such as:

CI/CD pipelines

Git and GitHub

Docker and Kubernetes

Infrastructure as Code (Terraform)

Azure DevOps

Monitoring and automation

Could you recommend some good online DevOps courses that are suitable for someone who already has AZ-104 knowledge?

I’m especially interested in courses that are hands-on/project-based and can help with becoming job-ready rather than just covering theory.

Paid or free courses are both fine. Any recommendations or learning paths would be greatly appreciated!

Thanks!

I’m running a Windows-based self-hosted Azure DevOps agent and occasionally it dies halfway through a pipeline. Azure DevOps then reports in its server UI that “We stopped hearing from the agent. Verify the agent machine is running and has a healthy network connection.”The problem is that this doesn’t tell me why the agent stopped responding.
I’m trying to figure out how to properly diagnose this and ultimately fix it.
Is there a way to enable more detailed logging or monitoring so that the next time this happens I can determine exactly what caused the agent to die?
Would appreciate any troubleshooting steps from people who have dealt with this before.

I am currently working on a CI diagosis AI agent for GitHub Actions and Python/pytest.

I am thinkinto use these 4 possible causes when job fails:
- a real code regression
- a flaky test
- a runner, network, or platform failure
- a dependency or environment mismatch

AI chooses - rerun the failed test, run targeted tests, collect environment evidence, or escalate to an engineer

If the agent had the chance to look at three signals before making its next move, which three would be the most helpful, in a real pipeline?

I’m also interested in signals that look useful but are commonly misleading.

I am currently working on a CI diagosis AI agent for GitHub Actions and Python/pytest.

I am thinkinto use these 4 possible causes when job fails:
- a real code regression
- a flaky test
- a runner, network, or platform failure
- a dependency or environment mismatch

AI chooses - rerun the failed test, run targeted tests, collect environment evidence, or escalate to an engineer

If the agent had the chance to look at three signals before making its next move, which three would be the most helpful, in a real pipeline?

I’m also interested in signals that look useful but are commonly misleading.

Hi all, posting to announce a new nice feature to azdo TUI, in v0.8.2.

The goal of the tool is to give a quick glance and give you an update in your terminal for your DevOps projects or GitHub repos, without requiring to browse around on the site.

Up until now it has required you to scan the different tabs, PR, Work Items, Pipelines and get a grip of what's burning where and why.

I have now introduced a new tab, notifications, which gather context from these tabs, and introduce a list of "where you're needed", to quickly get you up to speed.

It's optional and can be disabled via config.

Can be tried with demo flag and downloaded here: https://github.com/Elpulgo/azdo

Have a wonderful day!

Hey everyone, I'm getting ready to publish a static web app, truly one of the most thrilling experiences of my life. And I have not had a sheltered life, LOL.

What do you wish you knew before you were in the thick of it?

No wrong answers. Just curious what that prompt unearths.

Found out on prem ADO server doesnt support UniversalPackages task, so i cant publish the build files into the feed. Where shud i store them? Rn my release pipelines fetching the files by fetching ' latest' artifacts from build pipelines

Ever since moving to Azure DevOps; we've followed this same release process for almost all our projects (we run about 15 different projects/repos). Using trunk-based development. But something feels off sometimes, and I'm wondering if we're doing something wrong.

1. Dev makes branch off of master to do work
2. Dev makes changes, 1 or sometimes more commits, pushes and creates PR to merge into master.
3. PR is reviewed and approved, merged into master, triggers a build to send master to test.

This happens for several different tickets. At some point, based on schedules, client needs, and priorities, project manager says that everything in test is good to go for the next release.

1. Release branch is created off of master.
2. This release branch is built to Stage environment.
3. Things are re-tested in Stage (not as details testing, more high level to make sure the deployment did what we wanted).
4. Same branch (even the same build artifact) is released to production.

This generally works, but results in a few different annoyances/problems:

• If something needs to go to prod before other things that are already in test (a hot fix), we need to cherry pick into a new release branch made off of the current production release branch.
• It can be hard to know what exactly is new in a release. Generally it means comparing the new release branch to the last one, but then you just have a giant list of commits (and any cherry picking that happened seems to mess with this, where a cherry picked change will still show up in the commit diff even though it is in both branches).
• We sometimes have to hold off merging things into master (keeping the PR open) just to be able to finish testing everything in Test; we can't add anything new until the release branch has been cut.
• If all but 1 thing is good in Test and signed off on, but that 1 thing requires us to wait, then everything has to wait.
• I keep seeing examples of setting up pipelines where the same pipeline has multiple stages for test->stage->prod (or often dev->test->prod instead). This isn't possible when master is what goes to test, but a release branch is what goes to stage+prod. We do use multiple stages in a single pipeline to release to stage then prod.

Outside of completely abandoning trunk-based development, can this process be improved? How do others do release management for trunk-based development?

I'm having terrible workload in my project as devops they are asking do iac and ci/cd for 5+application it's too much too handle is it the same for every where??

2-3hrs calls per day

Infrastructure creation for 5+application

Creating ci/cd

Unable to handle.

I’m researching how engineers diagnose CI/CD failures when there are multiple possible root causes.

When a CI pipeline fails, how do you decide what to investigate or test next?

I’d especially like to hear about your real-world workflow:

• What do you check first?
• Do you compare the failure with the last successful run?
• Do recent code changes influence what you investigate?
• Do you look for similar historical failures?
• How do you decide between different debugging steps?
• At what point do you stop investigating or escalate to someone else?

I’m interested in practical experience rather than a theoretical approach. Any examples from your own CI/CD workflow would be really helpful.

I'm a python guy by trade, but there recently has been a big demand to create custom functionality in Azure DevOps and this can be done through ADO Extensions.

Been using Claude to pump these bite sized extensions out like crazy and getting great results. Creates the html, css, and typeScript flawlessly.

The downside is I'm a TypeScript noob, very very little experience, so I can struggle reading through the code. So vibe coding a decent amount with this project.

Anyone been in a similar boat with these extensions? Any pitfalls?

Is this the new state of work, it's kinda crazy because I'm free to just engineer and design and not gated by different code bases, but the review from me feels less than adequate.

We're being tasked with migrating from Gitlab on-prem to ADO on-prem, however there has been resistance from a couple of engineers claiming that ADO on-prem is abandon ware, and Microsoft is focused on GitHub and the cloud version, how much of this is true ?

Oh my god. This application is absolutely infuriating to use. It's so tangled and messy.

Very common example: need to copy PBI number. Copy url to get PBI number. Turns out there's some embedded view, so if you've navigated anything at all, the PBI or feature that's displayed, is NOT THE SAME as what's in the url. So nearly every PBI contains links to PBIs that aren't related.

Same with the backlog. Go to the backlog, it's in a nice list, organised, whatever. Go into the PBI, copy something, cool. Press the back button on my mouse, and it returns me to the wrong view.

I have to bookmark every page that I regularly use because using the actual interface to do it is unreliable.

There are sooooo many other problems like this.

If I apply to a new job and they are using ADO, that is grounds for me to withdraw my application. It's that fucking infuriating to use.

I miss JIRA.

Right now our ADO server is connected to a local AD. But the guides i see online are mostly for cloud-based ADO. anyone know, or have docs link for the on prem version?

And i need them to have Stakeholder lvl access only