Travis CI Github pages frustration pissed off fucking piece of shit fuck everyone



  • I've been trying to learn Angular for a while now and wanted to push an angular application to github pages. I wanted to do this so I could make my Portfolio page with all the bells and whistles and host it on github pages instead of somewhere else.

    These are the steps I followed

    1. Create an Angular App

    2. Push it to Github

    3. Google how to push angular apps to Github pages

    4. Proceed to click the first link in the results, follow the instructions for the command prompt to spit out "oh yeah this command does not work anymore"

    5. paste error message above and google, land on a page that says oh yeah that command does not work anymore so do this instead.

    6. Follow instructions from step 5 everything seems like it is working but the web page looks empty. Developer tools shows a flood of 404 error messages

    7. Go back to google again, try another link except it uses Travis CI to build and deploy the app to Github pages. I don't need the added complexity of fucking Travis now but fine fuck it I wanna push this on to Github pages.

    8. Follow all the instructions from step 7. Integrate Travis CI with Github and try to build the project and I get an error message that is informative on a whole new fucking level.

    0_1508863007206_GithubPagesFuckup.png

    Are you fucking kidding me? How the fuck am I supposed to fix this? Where do I even start?

    What bothers me is I have been at this whole thing for close to three hours now trying literally everything I could find on the interwebs and not a single fucking thing works. Top it with an error message that was written by someone who couldnt give a single fuck . Who does this who the fuck does this why is this happening.

    I don't think the problem is with me not being able to follow instructions because a couple of months back on a sunday I wanted to find out what was the deal with Azure. I went on to the docs and followed the steps and within a couple of hours had an ASP.NET MVC application talking to a Azure SQL Database just with the fucking docs. I have learnt Angular purely via the documentation and it has been smooth AF.

    1.Am i too Dumb to do open sourcey deployment and stuff and what not ?
    2.Am I supposed to really get something out of that error Message?
    3.Am I TRWTF?

    This is so fucked up Holy shit.

    I'm sorry about the typos and the grammatical errors but I am fucking frustrated and boiling with rage why the fuck is this so complicated motherfuck



  • No idea why the formatting is fucked up



  • @stillwater Welcome to JavaScript, where nothing really works and you're :doing_it_wrong: no matter what you're actually doing.

    At a glance, seems that the actual error message might be hiding in the collapsed lines 1484 through 1499. Alternatively, "couldn't push" may mean a problem with your permissions or networking. Just a guess.



  • @stillwater said in Travis CI Github pages frustration pissed off fucking piece of shit fuck everyone:

    No idea why the formatting is fucked up

    You need spaces after the periods after the list numbers.


    As for the GitHub issue, I know very little JavaScript.
    From what little I do know about it, could there be a version dependency that lost support with a newer version?
    Are there finicky (folder) naming requirements for the GH Pages support?



  • GitHub Pages is just static files in a branch named gh-pages, or somewhere else if you change the configuration. There's no "backend" for it.



  • @ben_lubar Does that mean the project should be built locally and the output be uploaded to GHP?



  • @djls45 yes



  • @dcoder

    Haha that is what you would think. The collapsed lines might have a clue hidden inside about why this is failing. Well,

    0_1508902393175_GithubPagesFuckup2.png

    Not a fucking clue. Not one.

    The Build process seems to run okay. No errors there. It says expiremental support for Github Pages which is something I'm worried about now.



  • @djls45 There is absolutely no folder requirements. you can set GHPages to point to any folder that you want. I have never had a problem pushing plain HTML/CSS/JS pages to GHPages before. Angular needs compilation, minification, uglification and whatever the fuck not without which there will be 180+ MB of data that might need to be downloaded(according to the docs) and hence it needs to be built before deployment. Who fucked up this thing so much??? Why is deploying something as simple as a Hello World App so fucking complicated ?



  • @stillwater Yeah, the problem is in the deployment step, not build. Like Ben said, deployment to GH Pages is "push this stuff to my GH repository", so the failure suggests the Deployment Bot failed to push it - maybe you didn't set up some permissions for that bot to have write access to your repository? What instructions did you follow to set this up?



  • @dcoder

    I have given Travis write access to the entire repo and any branches it needs to create and or modify. God knows what the fuck happens behind the scenes. Also it needs a Github token to be included in the travis.yml file when travis builds it. Set it up too. I followed the instructions to the dot.



  • Although I really like how angular works, If this is the sort of shit I have to go through for deployment every time I'd rather stick with a stable ecosystem instead of being all over the interwebs trying to fix something that should not even be a problem in the first place.



  • @stillwater said in Travis CI Github pages frustration pissed off fucking piece of shit fuck everyone:

    Angular needs compilation, minification, uglification and whatever the fuck not without which there will be 180+ MB of data that might need to be downloaded(according to the docs) and hence it needs to be built before deployment. Who fucked up this thing so much??? Why is deploying something as simple as a Hello World App so fucking complicated ?

    The modern web has way more moving parts and dependencies than the old web, that is entirely correct.
    However, your workflow failed in the "push this to GitHub" stage, not the "build this" stage. Therefore the complexity of the build process is not to blame in this case.

    These extra build steps — transpilation, concatenation, minification/uglification, tree-shaking, etc. — are involved in all modern JavaScript frameworks to some degree, not just Angular. Some of that also applies to modern CSS. And that should be expected - look at native apps, where release builds involve more steps than debug builds.

    There should be solutions to this pipeline that just work, but thanks to all the busywork, mental masturbation, and not-invented-here'ism in the JS ecosystem (and its impotent standard library necessitating shit like left-pad), we instead have an endless stream of "best practices" that contradict yesterday's best practices. The modern web frontend stack is now a black box - developers take a foundation and start tacking on functionality without fully understanding how it works and what steps are involved. Lucky few have enough knowledge to make sense of it to some extent, and others are just hoping nothing will break down.

    Oh, and – the good old days weren't. The shit we had to write back then is just as bad as the hoops we have to jump through now to get things to work, the complexity just moved around. As soon as we get better frameworks, we start building more complex apps and the overall complexity of the systems never decreases.

    Edit: now that I read it again, this reads like I'm doing a "well, actually" against your rant. I'm not doing that, I deal with and rant about the crap this ecosystem has all too often myself, I just wanted to keep your troubleshooting work in the right area, away from the properly functioning build process.



  • @dcoder

    I completely agree with you. I just wanted to vent off my frustrations cos I thought this was a safe place is all. :(


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.