This is their container builder project re-branded.
Pretty nice product, but missing some LAUGHABLE features.
Specifically:
- Ability to start builds based on github pull requests
- Ability to send messages to slack on successful / failed builds
- Ability to update github PRs with build status
- Conditional build steps AT ALL
- Ability to start parameterized builds from GUI ( What if I want to deploy to a specific environment? )
- Any outside integrations AT. ALL.
- No story on how to store secrets
I've been running this product for about a year. I have a Jenkins job that detects github PRs, and then launches these builds. I would LOVE to delete that Jenkins VM, but for some reason a lot of basic functionality has been ignored.
edit:
People have informed me that Github PR building is in alpha! PRAISED BE THE GOOGLE!
Hi, member of the Google Cloud Build team here. Appreciate all the feedback on the launch! Yes it's both a rebrand as well as an update.
When we first launched Container Builder a year ago we always had a plan to support more CI use cases. With the launch today we've added a few new features such as:
- Built-in support for pushing non-container artifacts to Google Cloud Storage
- Filepath triggers for invoking builds only on changes to certain subdirectories or files
- Updates to the Cloud Console UI and of the Cloud SDK (from `gcloud container builds...` to `gcloud builds...`)
We have more updates in alpha now including built-in support for GitHub pull requests, status/Checks API support, and programmatic triggers, which we agree is one of the biggest missing pieces for many people. That GitHub app is the first step with more granular control over PR triggers coming soon.
We try not to comment on roadmap items but looking ahead a little, this rebrand is also an indication of the product's focus on broader CI/CD use cases, which many of our users are already using Cloud Build for, and an evolution towards bringing DevOps and Continuous Integration best practices to Google Cloud users. Feature requests like built-in conditional steps and notifications are on our radar and we always appreciate hearing from users what they'd like to see us prioritize.
We appreciate all the positive feedback on the thread as well. We're excited about what's ahead for Cloud Build and that it's helping people be more productive!
Awesome to see this product getting more love! I'm looking forward to the Github status updates.
A few suggestions from my experience using the product for the last few months:
- Setting the machine type on a per-step basis instead of for the entire job. For example, I'd like to use a large box to compile my scala, but can use a smaller one to test each package.
- Showing the status of each step before everything ends.
- Showing the elapsed time for a job on the page for the job in addition to the start time.
- Failing a single step without stopping the build (for example, a single project in a ci build fails.)
- Speeding up the web view (it's very frustratingly laggy when you have a significant logs in your build.)
- Using the dataflow visualization for cloud builder.
Do you even support trivial features like sending an email if a build fails? Please don't answer write your own pubsub component. If you don't have that, you shouldn't have bothered rereleasing this.
"Set up triggers to automatically build, test, or deploy source code when you push changes to GitHub, Cloud Source Repositories, or a Bitbucket repository."
Container Builder has been able to trigger based on changes to GitHub repos for a while (tags and merges to branches). What it (and the new branding) can't do, and what the parent comment is referring to, is trigger builds when PRs are opened, and update the PR with the build status.
"Observe that the Google Cloud Build app builds your code on creating a pull request."
"Go to the Checks tab.
You'll see that Cloud Build has built your changes and you should see that your build has succeded. You'll also see other build details such as the time it took to build your code, the build ID, etc."
> Ability to send messages to slack on successful / failed builds
That should be easy enough, request a new cloud builder Slack. Currently this is possible though using the curl cloud builder and constructing a custom curl request to the Slack API.
> No story on how to store secrets
Agree, need a way to mark variables as sensitive/secure. Don't show them in the build history in plain text and make the input field of password type. Encrypt somehow when stored as well.
The demo I just saw certainly seemed to have all of those things (except possibly PR status updates and outside integrations). I don't think it's a rebranding but an update.
We've been using https://drone.io/ for some time, which is very, very similar, but if we weren't I'd give it some serious consideration.
As a student who SUFFERED through K-12, was an awful C-D student, I agree 100% with this overall idea.
I went from a D high school to a straight A student in college. I found the freedom to choose to study what I am interested in ( Computer Science ) extremely liberating. I found the respect shown by the faculty to the students refreshing compared to my high-school. I found that being able to leave, take a nap, and then come back for my next class much more tolerable. I found that not being locked in a building for 9 hours a day freed up time to actually study and get your homework done.
Basically, I discovered what everyone else already knew: Current schooling is intended to keep kids in child-jail while their parents are working. Most schools do not have the resources to cater to bored gifted students, so we are cast aside with the understanding that "we'll be fine" while sitting through remedial classes where we have to read out loud because some of the students in the classroom are illiterate.
People claim college is a waste of time? HA. HIGH SCHOOL is four years of my life WASTED that I will never get back.
Let students set their own pace for education. Have them take responsibility for their own lives and future at a younger age. Let the children out of child jail.
I don't really miss their hardware, Sega shot themselves in the foot by releasing too much cash-grab junk over the 90's instead of focusing on their core products.
But the games they made still create this painful nostalgic twinge in my heart. Just HEARING the Dreamcast sound chip affects me.
Agreed on the nostaliga, but what cash grabs? The 32x and Mega CD might have been failures, but they were pretty innovative I think. The Dreamcast was also the 90s :)
Fair enough. The products could, and probably had, been made in good faith. But, I think the constant barrage of new products from Sega, along with the complicated hierarchy of how the products interacted with each other, burned people out.
I've lived in the Midwest my entire life, from a tiny town of 2,000 people to Chicago Illinois. I'm moving out to Portland in less than a month.
I REALLY dislike the Midwest due to it's lack of natural beauty, epidemic of poor civil engineering and city design, and hostile climate.
> If you're looking to move to the Bay area, you should also look at moving to the like Lincoln, NE or Omaha, NE or Kansas City. A lot more so if you have a family. I know that sounds strange, but....
Comparing the job market of Lincoln, Omaha, or KC to the Bay Area is very flawed. The tech-hubs are a real thing, and there are advantages to working in an office that make remote work undesirable. ( More likely to be promoted, having a social life, etc. )
Even in cities like Portland, you look around at the jobs being offered and see MOSTLY lame fintech and insurance company jobs. Additionally, you are away from the critical mass of highly educated and motivated developers. Even here in Chicago, you meet a LOT of the b-team.
> The Midwest is cheap. Albeit harder than the past, it is still possible and common in the Midwest to live a middle-class-ish lifestyle on a single income. A two bedroom apartment can be less than $500 a month.
While it's true that you can get a large house for cheaper, what are you going to do while you are in these cities? They, full stop, lack the cultural and natural vibrancy of the Bay Area. Extremely homogeneous, poorly designed cities full of insurance salesmen and hicks.
Brutal cold winters and sweltering, buggy summers. Not that you would want to go outside anyway, since most of these Midwestern cities have declined to invest in walkable infrastructure and instead more resemble disconnected buildings joined by huge highways. You will drive everywhere and none of it will be interesting or beautiful. ( To be fair, I hear Columbus has some nice infrastructure )
Not that you would have anywhere to drive to. The nature sucks. You can drive out of town and see some beautiful... corn fields. And flat land. Filled with bugs. Nobody has bothered to forge hiking trails because there's nothing to see.
> I have friends with $830/month mortgage payments on their house.
The most expensive house is the one you can't sell. And housing is not an automatically good investment like many people believe.
I know from experience, a lot of my friends who bought cheap houses regret it now that they are interested in selling and NOBODY'S BUYING.
> The Internet is solid in the Midwest too...
True. You can do the job. If you don't mind working remote / find a good job in the Midwest, it is 100% viable to live there.
> Lastly, (this is a hot topic issue so I am reluctant to put it in, but it is something that comes up from my friends on the west coast) the states are red states, but the cities are blue.
Yes. This means every time you decide you want to get away from the city, you are greeted by a bunch of Trump-supporting, confederate flag waving yokels who cut the sleeves off of their shirts. Also this means that when those people want to get away from the country, guess where they go? Your city, where you have to interact with them.
I have to say I loved growing up in midwestern nature. It's not a touristy sight-seeing nature like we have in the SFBA but there is just so much of it and you are surrounded by it and it's yours to play with. So.. as you said, it depends on what you want.
I have a System76 Galago Pro with 32 gigs of ram and an i7 processor.
Works GREAT, fan of the keyboard and everything.
The case is kinda shit, but it doesn't really bother me that much. I'm not obsessed with having a designer laptop that looks beautiful, just something to slam around and run programs on. Additionally, having a ton of ports to plug things into has been very welcome after migrating off of the touchpad macbook pros.
Linux desktop is nice because of the great docker support, and honestly it tends to work quite well for pretty much everything I throw at it. Multi-monitor support is great, it works fine with my 4k monitor. I was AMAZED when I plugged my usb-c headphones into the usb-c port and heard sound come out.
I tend to just travel with a ball mouse because I have really severe hyperhidrosis which renders basically all track-pads, even Apples', completely unusable, and uncomfortable to boot. Moisture + friction is not a great combo.
I admit that I'm a bit of a weirdo and this set-up would be sub-optimal for a lot of people due to support for various adobe products. But I'm happy with the setup.
If I could go back in time I would probably get a Surface laptop and set my home computer up as a server, and automate sending work to it, because I'm a big fan of indie video games and would enjoy being able to play games on my laptop.
I am a full time remote worker, but I have survived the tyranny of an open office in the past. I dislike the open office format.
A lot of the time companies don't "choose" an open office, it chooses them.
If you are working at a small or mid-sized company, building out rented office space you will probably outgrow in a year or two is a crappy investment.
The alternative? Buy the desks, throw them into a room, expect people to be quiet and respectful.
I would be a indie game maker if I could start over, so I guess I would still need the programming skills.
But I would also gain skills in art, music, level design, etc. on top of it.
I would avoid corporate life and carve out a happy little niche in a funky little community like Portland or somewhere similar. Save, live within my means, pay off my student loans. Work as a hard working, humble little dev and pursue my passions on my fiercely guarded free time. Volunteer some of my spare time for environmental conservation and human rights organizations. Have a garden, two cats in the yard... wait that's exactly how I live now, except I'm a sysadmin instead of a game developer.
Overall I have an amazing life and a really bright future so I can't really complain. Choosing to study Computer Science in college is what lead me down my current path. And when I look around at my options, I feel like I made a really great decision. Happiness comes from within. Keep your eyes peeled, always be learning, and don't be nobody's sucker. Don't get left behind.
Really my biggest regret is under-valuing and not believing in myself. It's amazing how great things can go when you just commit to something and make realistic and well-thought out choices while pursing your desired path.
ALTHOUGH, I'm only 29 so I can still do a LOT to change my life and work towards my goals.
It's amazing to me how people still "meh" away testing as a secondary concern, and then regret it later. Over and over again.
WRITING software is easy, anyone can do it. CHANGING software is extremely difficult. THAT is why we have tests. Also, if you are smart about it, you can get documentation out of the deal for relatively little additional cost.
My go to example is on-boarding new developers:
New dev: "OK, i'm here! How do I start?"
with tests: Clone the repo, install dependencies, and run the test suite. As you develop new features, be sure to write additional test.
They are up and going in a matter of minutes.
without tests: Clone the repo, install deps, download testing database, achieve homeostasis with your dev environment, learn the entire system, build up the state you require to write your feature, iterate on it by hand over and over again.
>without tests: Clone the repo, install deps, download testing database, achieve homeostasis with your dev environment, learn the entire system, build up the state you require to write your feature, iterate on it by hand over and over again.
My first job out of college was like that. I had been doing professional-ish (I was paid and employed but I basically worked alone with no other engineers around) work for two years but this still didn't raise any flags.
Pretty nice product, but missing some LAUGHABLE features.
Specifically:
- Ability to start builds based on github pull requests
- Ability to send messages to slack on successful / failed builds
- Ability to update github PRs with build status
- Conditional build steps AT ALL
- Ability to start parameterized builds from GUI ( What if I want to deploy to a specific environment? )
- Any outside integrations AT. ALL.
- No story on how to store secrets
I've been running this product for about a year. I have a Jenkins job that detects github PRs, and then launches these builds. I would LOVE to delete that Jenkins VM, but for some reason a lot of basic functionality has been ignored.
edit:
People have informed me that Github PR building is in alpha! PRAISED BE THE GOOGLE!
https://cloud.google.com/cloud-build/docs/run-builds-on-gith...