Viewing profile — toxicbakery
toxicbakery
HN member- Joined
- Thu, Jan 24, 2019, 2:05 AM UTC
- HN karma
- 16
- Public activity
- 11 items
- HN profile
- View on Hacker News ↗
About toxicbakery
No profile information was provided.
Recent public activity
-
comment
Comment #19005030
That sounds like a great improvement to the process!
-
comment
Comment #18988608
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.i…
-
comment
Comment #18988233
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 bra…
-
comment
Comment #18987882
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 …
-
comment
Comment #18987839
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 pipelin…
-
comment
Comment #18987824
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.
-
comment
Comment #18985423
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 compe…
-
comment
Comment #18985406
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 h…
-
comment
Comment #18985399
You got me, I use Linux :)
-
comment
Comment #18985398
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 …
-
comment
Comment #18985381
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…