Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "fuck artifactory"
-
Internal mail form CIO's office:
"Thank you for being part of the internal trial for NPMe, we have decided to remove this tool in favour of Artifactory because of its support for multiple platforms and tools. We are sorry for the inconvenience, here is a link to migration scripts ..."
Migration "script" readme, please clone this repo, create file A, and B, and install these 2 dependencies.
Dependency 1:
- "install via homebrew ..."
- .... homebrew needs to update, checking for updates
- 10 mins later = Update failed, please upgrade to Ruby version 2.3
- Installs ruby version manager
- GPG signature verification failed
- Install GPG v2 + accept keys
- Install ruby version manager
- "please execute this command before running rvm"
- execute command
- "rvm install ruby-2.3"
- Install failed, please see log file
- Opens log file
- "Xcode on its own is not sufficient, please install xcode cli tools"
- Install xcode tools
- 5 minutes later -> "rvm install ruby-2.3"
- 10 minutes later "brew install jq"
Ok back to read me, "login to Artifactory, go here and copy paste XXX."
- Login to Artifactory
- Eventually find repo
- Login again to actually see credentials for some reason
- Screen doesn't match instructions in readme
- Click around
- Back to readme
- Back to artifactory
- Login again
- Execute command auth / setup command
- Copy contents to npmrc file .... now all my scoped packages are going to point to 1 specific repo
Fuck the migration, Fuck these shitty instructions, i'll set them all up again manually. See tags below for further opinions on this matter.undefined fuck ruby fuck homebrew fuck this fuck shitty cli fuck artifactory fuck cli fuck jq fuck rvm2 -
WHY THE FUCK ARE WE ONLY KEEPING THE LAST 10 BUILD ARTIFACTS IN ARTIFACTORY?!
THAT IS LITERALLY THE OPPOSITE OF HOW YOU'RE SUPPOSED TO USE IT
NOW I CAN'T ROLL BACK PROD CHANGES TO A WORKING VERSION BECAUSE IT LITERALLY DOESN'T EXIST ANYMORE
FUCK YOU, IT'S YOUR FIRE NOW9 -
My favourite dev tool? I would't be able to do my work without any tool, which's in the list. I love IntelliJ IDEA & Webstorm, Java, JavaFX, Maven, Git & Gitlab, TeamCity, Upsource, YouTrack, Artifactory, wtf that list's kinda the complete tech stack. But I completly hate AWT & Swing (AWT fucks up on my Linux install, such a frame creates in about 10-20 seconds, if you test the app locally, you loose approximately 15 seconds per minute, and Swing uses AWT internally too), I hate Gradle (screw Google for standardizing it), and so on. Wow that's like my complete tech stack, what the fuck happend? The question was one tool, help me.1
-
One of the truth no one wants to say because what can not be can not be.... but...
Maven is fuck... bullshit... failure by design.
For each project I need an own settings.xml. Always something not working. The same artifactory password 10 times there. Null pointer exceptions all over the place. Basics like versioning not really solved.
In all my years with Ant I never had so much problems than with Maven.
This settings.xml is really a design failure. Crap.1