toxicbakery

4 ms·

1.
by toxicbakery 8y ago
That sounds like a great improvement to the process!
2.
by toxicbakery 8y ago
I'm not sure what you mean by this but a few other people have asked me about the described screen size problem so I decided to add some clarification. https://toxicbakery.github.io/vsts-devops/dimensions/
3.
by toxicbakery 8y ago
It is likely that this is a variant of the issue with secure files. Secure files require a song and dance around changing the default branch or committing directly to a default branch to trigger a build after setup of the secure file. Comin
4.
by toxicbakery 8y ago
In the opening paragraphs I stated it was my hope that this gives me a gateway to communicate with someone that isn't support and isn't the void that is their robot response issue tracker. That said, they generously reached out to
5.
by toxicbakery 8y ago
I initially thought the same thing but I'm less convinced of that after trying an aws based build agent. I think the agents themselves may have a bug that combined with our pipeline needs, triggers some perfect storm issue. At the same
6.
by toxicbakery 8y ago
Funny enough I had not had the time to write about this yet. This resolves one of the other issues on my list. Thank you.
7.
by toxicbakery 8y ago
The majority of the product indeed does work pretty well. We make heavy use of their Boards and Test Plan features and outside of specific but minor UI/UX complaints, it is a competent tool.
8.
by toxicbakery 8y ago
You are correct, I'm just an Android dev but the company I work for is a long time user of Microsoft products like Visual Studio and obviously Windows. Over time, if anything, we have become more invested in their products and I don&#x
9.
by toxicbakery 8y ago
You got me, I use Linux :)
10.
by toxicbakery 8y ago
I'm interested to hear you have not had the same CI issues I have. One theory I have with no substantiating evidence is that Linux agents are least commonly used. The Linux agents on hosted builds run in a hypervisor but I've seem
11.
by toxicbakery 8y ago
Horrifically broken was an exaggeration, you are correct. Much of this was written after a stressful day compounded by dealing with our CI failing to do the thing it is supposed to do. I also agree with you that Microsoft has been making gr